something cool to add to #activitypub woulöd be a global shoutbox
General Discussion
2
Posts
2
Posters
17
Views
-
something cool to add to #activitypub woulöd be a global shoutbox
-
something cool to add to #activitypub woulöd be a global shoutbox
I mean... technically, any public post is kind of a global shoutbox?
Gli ultimi otto messaggi ricevuti dalla Federazione
-
If you investigate NodeBB's actors, all of their outboxes return an empty OrderedCollection because I simply haven't gotten around to it yet, and I don't know many implementations that read it.
I read from outboxes all the time. But I can't do that with NodeBB 😢
-
I mean reciving votes.
It is “here is a dm with the content being the same as one of the options on the poll”
-
@gabboman@gabboman.xyz for polls? The post sends an update every time someone votes I think.
-
Im scared of implementing polls because I would have to check the get post recursively function on wafrn and oh no
-
@Edent PHP 8.5 might be diffcult on some classic webhosters, but that might change during the spring or autumn.
-
@edent@mastodon.social is it fair to play ActivityPub code golf when nobody else can come close to competing? :stuck_out_tongue_closed_eyes:
-
RE: https://example.viii.fi/posts/69b029a4-2ee5-0f49-b23b-333d1e8ee38b.json
OK! Editing posts now works.
A fully complete #ActivityPub server in under 80KB of code.
https://gitlab.com/edent/activity-bot/
I think supporting polls will be too hard, so I'm declaring this feature complete (although not bug free) for now.
If you have any suggestions for how to improve it - let me know 🙂
#ActivityBot
-
> from my understanding Person vs. Group actor are mutually exclusive, so I can't have both on the same handle right?
Correct, while you can have webfinger resolve both a group actor and person actor from a single handle, that gets messy quickly because how the receiving end handles this is not specified. Mastodon for example only takes the first entry, which crucially means if a community and user have the same handle, then one of the actors is inaccessible to Mastodon.
I don't think you need to introduce breaking changes (I hope!), the threadiverse component can be bolted on to existing functionality. In fact, I'd recommend maintaining the existing Person actor so that microblog compatibility is not impacted. It's not an either-or approach, NodeBB does handle both types effectively.
Here are some quick answers to the open questions:
Should the Person actor have its own inbox?
Yes, the Person actor and the Group actor are two separate identities (as far as anybody outside of your instance is concerned.)Outbox representation — Should the Group's outbox contain the Announce
activities, the inner Create activities, or both?This is optional (at least for NodeBB). If you investigate NodeBB's actors, all of their outboxes return an empty OrderedCollection because I simply haven't gotten around to it yet, and I don't know many implementations that read it. Federation works fine without it, but it would make sense to follow Lemmy or Piefed's lead here.
Backwards compatibility — Should Madblog support a "hybrid" mode that sends both Create (for Mastodon) and Announce (for threadiverse)?
Mastodon will correctly de-duplicate the object so sending both Create(Note/Article) and Announce(Create(Note/Article)) is fine. The former serves non-threadiverse followers, and the latter ensures threadiverse syncronization capability.
NodeBB actually sends three :see_no_evil:: Create(Note/Article), Announce(Create(Note/Article)), and Announce(Note/Article). That last one is not needed.
Separate keypair for the Person actor? If the Person actor eventually needs to sign requests (e.g. for inbox delivery), it would need its own keypair.
I believe so. It was trivial for me to just generate keypairs for everybody, so I don't know off-hand whether things break if your Person actor doesn't have one. It might not resolve in some implementations?
