Title, description and id are now correctly fetched over ActivityPub. But the library we are using is a mess, and the code is extremely ugly. Also our database and logic needs a good number of changes to deal with federation (like we cant use simple numeric IDs).
Not closer than I was a month ago sadly. I got bogged down in some C2S details.
That being said, my library has pretty much interchangeable C2S - S2S behaviour. Ie, the dev needs not worry about the distinction too much.
Returning to the ID problem. In ActivityPub the ID you expose when federating needs to be a fully qualified IRI, so multiple instances with containing the local numeric ID 1 should not a problem. Otherwise collisions would happen even if using UUIDs or some other non numeric sequence logic.
Good on both you and /u/nutomic (and anyone else) for continuing to work on federation though!
Well, I’m working on federation on another project. :) Thank you, though.
Okay so I’m more thinking of the URLs that are visible to the user, not of ActivityPub. Still need to get more familiar with that.
For user-visible URLs, keep in mind that having plaintext names (so something like
https://lemmy.ml/c/community@communism.lemmy.ml) is good for both human readability and search engine optimization.