@triskelion Forgejo is preparing for that as we speak. You already can use a mastodon instance as oauth provider, according to the docs (Haven’t tried it yet)
#softwareConcept TwoTags: an #ActivityPub enabled bookmarking service where the first two tags you give a bookmark are hashtags, and also the combination of the two.
What I find strange in #ActivityPub and #Fediverse that there is no way to put a note to follow request. Like "I want more posts in language_name in my feed and I liked the cat videos you repost".
It gives cases when someone concerned that they did not understood why someone follows them.
@J12t Yes, that's certainly one use-case for the outbox... to "catch up" on things you missed, on a per-user basis.
But as far as I am concerned they're separate APIs that pull from a common data source.
For example, reading the ActivityPub spec, one could draw the conclusion that the outbox is an ordered list of activities, likely read as-is from the database.. but that's not strictly defined, so it's possible to dynamically create outbox items on-demand based on user history stored elsewhere.
That would mean less duplication of content (and the syncing that is required), fewer bugs, etc... but the cost is the collection then has to be dynamically constructed.
@julian It's mostly append-only, easy to cache ...
For FediTest, we have come to the conclusion that simple pass/fail isn't going to cut it. We need a more gradual rating, and the current state is 1) fail -- against the spec and likely go cause interop problems 2) soft fail -- against the spec but probably harmless from an interop perspective 3) degrade -- e.g. everything turns into a Note and 4) pass. Not sure this is an exhaustive list ... your empty outbox would get a pass, I think.
More Excellent developments on the good work being performed on #NodeBB and interoperability with #WordPress instances endowed with the #ActivityPub plugin:
@molly0xfff is a leading cryptocurrency critic, but get to know her and you’ll see she’s anything but cynical about the future of the web. Hear why this researcher, writer and software engineer thinks so in this fascinating conversation with @mike: