if i search for a user in #activitypub .academy the first time, #mastodon is doing - a webfinger request - read outbox-collection request - read following-collection request - read followers-collection request not bad. what do they expect wenn reading the outbox? the objects that was adressed to as_public?
1/3 The Internet of the future belongs to 'Linked Open Data'
In my opinion, the Internet of the future is based on machine-readable / interpretable data. This is not HTML. HTML is machine-readable, but only interpretable in the context of the structure and formatting of texts and other data. By interpretable I mean more the technical context, i.e. event, POI, article, short message, recipe, organization, person, etc...
The Fediverse, a networked ecosystem of social platforms, is based on JSON-LD according to the specification. JSON-LD is a way of representing RDF data.
For me, “social platforms” are not just microblogging systems or platforms for videos & images. We need to think further! Supply chains are a key example of Linked Data (and in my view always Linked OPEN Data).
@evan uuuuuhhhhh i can't remember the last time i spoke in front of many people. and certainly not in english. but you should follow the ideas you're afraid of ;-) let's see
@weekinfediverse elk (A nimble Mastodon web client) I would be really happy if the category “Clients” would get subcategories. Elk is a Mastodon client and therefore does not speak fediverse protocol. Or am I wrong with my opinion ?
@pfefferle@darnell I use uuids for the ObjectIds (actor id). I had also toyed with the idea of using the Oauth2 UserId, but decided against it. I might want to allow the actor to log in with 2 different Oauth2 providers at some point.
However, this makes debugging and troubleshooting hell ;-)
@sl007@pfefferle@evan if tools don't work without webfinger, it doesn't help much not to support webfinger. it doesn't matter whether webfinger is part of Activitypub or not.
In his presentation for berlin, @evan talked about activities regarding HTTP signature and webfinger. Are there any documents on this that I don't know about?
@pfefferle@evan@julian Client developers are very welcome. that's not my focus at all. and it would be very good to have a client developer who has a different perspective. I would start with “Notes” anyway, as this is the easiest to test with other servers. next steps, however, are stabilization, webfinger feditests, following..., http signature.