evan

@fedicon@techhub.social This is great news!

@hongminhee@hollo.social I wonder if you've had this problem and how you worked around it.

Another possibility is that when someone asks to have their content shared, that will result in a few Follow requests, which does result in their future content being distributed to other servers (and public content goes to Fediverse and hashtag feeds). So, it seems like the sharing is what got the distribution going, even though it is indirect (sharing causes following causes appearing in the Fediverse feed).

Here's another: https://fedi.lunya.pet/notes/a814wossvh

Of course, you can just bang on the API until you get 429 restricted, too.

Oh, and if you're using an AS2 type, you don't have to worry about the extra context URL, obvs: { "@context": "https://www.w3.org/ns/activitystreams", "type": "Person" }

@elle@weathered-steel.social thread here!

There's a new draft of the basic profile for Social API Servers from the ActivityPub API Task Force:

https://swicg.github.io/activitypub-api/basicprofile

It covers some very basic features for getting an interoperable set of clients and servers working together to provide simple social networking functionality.

@julian yes, I agree. This is a different idea -- that somehow interaction between actors on different servers will make their servers connect and share data. It's incorrect, but it's interesting.

@julian here's an example I found with a search: https://f.bumblebee.systems/@bumblebee/113834766747645985

I'd add in projects like Emissary, Bonfire, or https://github.com/evanp/activitypub-bot . They can all be used to build Fediverse servers from building blocks. I think other parts might be more piecemeal. I thing HTTP Signature libraries are awesome. https://github.com/social-web-foundation/activitystrea.ms is an AS2 library that I've used a lot, even though it's weird. https://github.com/social-web-foundation/ap-components is a Web Components library for ActivityPub objects. Also kind of cool! I think a lot of of building a Fediverse server -- or client! -- is implementing behaviour, which an engine like Fedify can do, but most libraries aren't going to do for you.

@reiver@mastodon.social That's not true. Most of those are not correct AS2. Only '"type": "Banana"' is correct. Activity Streams says, The serialized JSON form of an Activity Streams 2.0 document MUST be consistent with what would be produced by the standard JSON-LD 1.0 Processing Algorithms and API [JSON-LD-API] Compaction Algorithm using, at least, the normative JSON-LD @context definition provided here. So, assuming that you've defined some Banana extension, your full code might look like this: { "@context": [ "https://www.w3.org/ns/activitystreams", { "ext": "https://banana.example/", "Banana": { "@type": "@id", "@id": "ext:Banana" } } ], "type": "Banana" } If you park all that context data at a context URL, you can have a much slimmer payload: { "@context": [ "https://www.w3.org/ns/activitystreams", "https://banana.example/" ], "type": "Banana" } If you don't define the extra context stuff, you have to use the full URL for the type: { "@context": "https://www.w3.org/ns/activitystreams", "type": "https://banana.example/Banana" } I prefer the slim one with the context URL. If you use a JSON-LD library for parsing your input, all the funky variants you're sharing get canonicalized into one easy-to-use one. And if you use it for formatting your output, you'll always produce nice, clean AS2.

@Profpatsch@mastodon.xyz https://tags.pub/

@Profpatsch@mastodon.xyz A firehose of gay and furry porn is part of a real social space. Homophobia isn't.

@silverpill@mitra.social really? How does it work?