@achim @evan The fragment ID could be different but it needs to be embedded in your actor document. Here's a JSON schema:https://codeberg.org/ap-next/ap-next/src/branch/main/schemas/actor.schema.json

@3rdi@mastodon.social @stevejb@beige.party I don't think it is a social network, Dan just made a landing page showcasing (his) Canadian alternatives.

@carstenraddatz it was rather last minute but I will do more events like this here.

@julian good!

@raphael both servers I built using GoActivityPub have support for Dynamic OAuth2 client creation (RFC7591 and RFC8414) and by using the Client ID Metadata Document draft if you plan to support one and/or the other.

@trwnh@mastodon.social Yes—Fedify is database-agnostic, so tracking which IDs are already in use is the application's responsibility. Fedify handles the federation layer, but the data model and storage are entirely up to the application built on top of it.

nextgraph@fosstodon.org I see, much clearer now

phoenix you can always test with ActivityPub.academy, live Mastodon servers can sometimes be delayed.

@feralthoughts Yeah I don't know what the practical effect of this on nodeinfo will be.

@liaizon@social.wake.st The contract with STF prohibits subcontracting. Therefore, the milestones listed above will be carried out by @hongminhee@hollo.social, currently the sole maintainer. However, we hope to bring in more maintainers by the next funding round!

@iftas @mainec @haubles FIRES can already share data on entire domains and individual actors, though access to a dataset like this likely needs to be authorized, which is something I need implementer feedback on.

Yep. Just one of the places software engineering which doesn't recognize social contracts fails everyone.@trwnh @feralthoughts @jdp23 @aj @julian @scottjenson @alexisbushnell @mekkaokereke

@silverpill Thank you - I wasn't aware of Mitra supporting conversation containers and nomadic identity, happy to learn.I have some questions about Mitra, I will ask them in a separate thread. @osma

@julian no, mastodon doesn't use salmon anymore, not since a long time ago. they switched to websub then activitypub direct delivery.on the indieweb side, salmention is an extension to webmention, where upon receiving a webmention where someone replied to you, you add that reply to your html then send a webmention up the reply chain to whoever you replied to, and they will fetch your html and find the new downstream reply, add it to *their* html, send a webmention upstream, and so on.

silverpill@mitra.social I have been reflecting on the use of Remove/Move vs Update and I am thinking that Update isn't explicit enough. If I am removing a topic from a category, I'd be sending an Update with the group actor removed from the audience property. However recipients wouldn't know which audience was removed, merely the new state of that context's audience.

@silverpill @julian @helge #ActivityPub today is where HTML was in the early 2000s - nobody agreed on what it should look like, and consumers had to go to heroic lengths to interoperate with all the different ways that producers interpreted the spec. (I was paid to work on one at the time. It was ... an experience.)HTML has come a long way since then - but it took rather more than five years!

I have yet to try SC on my AMD build. Hopefully vulkan treats you well!

@ainmosni Yes, the language detection seems to be a bit buggy, sorry about that!https://github.com/jointhefediverse-net/jointhefediverse.net/issues/99Will try to re-prioritize this over the next few days.@usefulchickadee

@morph @evan but not available for new account

@julian@activitypub.space @julian@fietkau.social well, in theory, you can have private likes and public likes. misskey and pleroma do public likes. mastodon does private likes, but then shows them publicly if anyone asks the origin site. because addressing is just a suggestion, apparently