@iiogamaIf you manage to import the cryptographic keys of all users and the instance actor, then it shouldn't be an issue either way.

@thisismissem @hongminhee imo the value of a did document is overstated -- did can be a useful framework for how to interact with identities that *can* be operated on and *can* have keys and *can* link out to other services, but none of those things are actually required and a lot depends on the actual did method to fill in that framework. in the case of did:key, the "key" method is just a thin wrapper around a key (for when that key is the identity). this makes the key valid for *any* purpose.

@evan it’s a good one, fb vs twitter style replies.

yes, this should just be a cursor with a pagination direction. However, the Mastodon API is proprietary and specific to their needs so they can do whatever they want and whatever makes sense for their application. I believe ActivityPub API just gives you URLs to follow for prev/next/first/last.

@evan @mariusor @silverpill i think we probably need to revisit the user story of creating multiple objects at once, or more accurately, the user story of minting and binding multiple identifiers at once.

@silverpill previous/next are the properties of a Collection object. And GoActivityPub uses "after" and "before" query parameters for configuring a keyset pagination cursor. Next is a collection IRI where ?after=IRI where IRI is the last object in the current collection.Previous is a collection IRI where ?before=IRI where IRI is the first object in the current collection.

@silverpill yes. Like I said in the sibling comment, a client can do the collection creation manually and then updating the objects with them.@trwnh

@smallcircles@social.coop Thanks for suggestion!

@silverpill @helge Alright, done:https://codeberg.org/fediverse/fep/pulls/771

@trishalynn I hope that answers your question.

RE: https://mastodon.social/@fediversereport/116178002926045553Laurens Hof is at it again highlighting the problems of our lack of an adequate ActivityPub API and the hurdles that are to come in it getting adoption.#fedidev

@bsky.brid.gy Does unfollowing everyone from the bot account not affect function? Or had that become vestigial at this point?I'm sure I've missed specifics over the months - but I love catching these updates, this is one of the most important functions the social web has right now.

@quillmatiq@mastodon.social I'm glad I only commented out that code.. It's restored now!

definitely not a fan of this. tbh, there should just not be a global feed that new accounts see, because they see a lot of stuff they don't understand or know the community norms for, and that leads to bad engagement.

There is the Web Share API, and the future Web Share Targets API, but I think we could also align Web Share with FedCM and be able to say "I want to share to this type of application"

@quaff @hongminhee thats the main issue, "the spec" doesn't have the coverage to have an implementation to cover it all. there are a ton of things that are under defined in it or that you need to point to some other spec that points to some other spec etc. thats sorta at the heart of this whole meta conversation thats been taking place recently

@trwnh @raphael @mariusor No, my goal is to interoperate with many Fediverse servers, not just Mastodon. I agree that a generic server is supposed to support any activity, this is exactly what I was arguing about for the last two days, and this is what my FEP is about.

@jihyeok what about two servers of Oeee Cafe run by different people? Also Wafrn has built in drawing mode in their mobile app so you could let posts come from there too

I think it should be followable by any actor that can receive the accept/reject activity. There's no type check on the actor, except for an inbox or sharedInbox. Yes, it uses the relay interface either as a client (following an existing relay) or as a server (provides a fake relay to your server). The server side is kind of a fakeout; it doesn't send any data to your server by default, unlike most relays. It's just a way to get your server to send it public activities. It works with Mastodon and Pleroma style relay clients. I'd love to talk! If you want to experiment, use https://tags.pub/user/_____relay_____ as the Pleroma relay server. Let me know how that works; I've only tested with the Mastodon style.

@naturzukunft2026 @julian @saskia https://swicg.github.io/miscellany/#Hashtag