Technical Discussion

Thanks @nutomic@lemmy.ml! I was wondering about that, so good to know it's possible.

I wouldn't recommend posting this as factual because of some of its errors and its extreme bias toward some kind of odd libertarian bend to it. A clear example of this bias is that it is referring to national fiat currency such as USD, EUR, etc "fake money". It seems to suggest the only real money is possibly some kind of crypto or precious metals maybe? Its hard to decode some of the author's euphemisms.

@trwnh@mastodon.social that sounds like a them problem not a my problem cc @mayel@bonfire.cafe

@trwnh@mastodon.social oooh that's interesting. I actually commented on the former. But I am realizing now that NodeBB actually explicitly addresses quite a few people because we try to keep everybody in the loop. Responding to a topic with hundreds of posts could mean a Note object with hundreds of individual users addressed in cc. Perhaps it's wiser to not assume "addressed? generate notification.", and instead have configurable notifications based on thread/context participation.

@julian (I replied to this from Hubzilla, but it doesn't seem to have showed up, so reposting from Mastodon... sorry for the duplicate)Yes, it does.I think FEP-171b is the relevant spec; Mike Macgirvin's description of Conversation Containers might be relevant too.It's running Hubzilla, which is already listed as an implementer of FEP-f228. @fentiger@zotum.net @silverpill

@julian not sure why you'd want to put your public AP stuff behind something like Anubis - a thing in general that I think is pretty anti-web to begin withyou're losing out on all sorts of cool integrations that you don't even know about

@julian so, let's start from the beginning: this is already in ActivityPub, always has been, and removing it from ActivityPub would be a grossly backwards-incompatible change. So, I would fight very hard against even considering removing this valuable feature. Second, a already covered some of the main use cases, and I won't reiterate them. One they didn't mention was making followers-only conversations actually useful. If I create a Note like this: { "@context": "https://www.w3.org/ns/activitystreams", "type": "Note", "id": "https://social.example/note/1", "attributedTo": "https://social.example/user/100", "to": { "id": "https://social.example/user/100/followers", "type": "Collection", "name": "Evan's followers' }, "content": "Hello, followers!", "context": "https://social.example/note/1/thread" } A reply by one of my followers should address everyone who the original post was visible to: { "@context": "https://www.w3.org/ns/activitystreams", "type": "Note", "id": "https://other.example/note/2", "attributedTo": "https://other.example/user/200", "inReplyTo": "https://social.example/note/1", "to": "https://social.example/user/100", "cc": "https://social.example/user/100/followers", "content": "Hello, back!", "context": "https://social.example/note/1/thread" } Another application is private groups. If the members of a group are represented as a Collection, then sending an activity to that collection is a private, members-only message. There's some discussion of this in in the Groups TF explainer: https://swicg.github.io/groups/ Features in the ActivityPub spec were designed to be really flexible and useful beyond narrow applications, allowing interesting extensions and new kinds of interactions. "Mastodon doesn't do that" is a bad reason to not support a feature.

@julian @pfefferle ActivityPub spec says IDs are URIs, I think that means non-ascii characters should always be encoded.Mitra rejects IDs that are not URIs, most of the time this doesn't cause any issues (WordPress was the only notable exception).

@evan thanks! I would attend but unfortunately a winter storm hit and I'm at home watching three kids today

Hm, it appears that none of my objections have been addressed.Once again, why there are two activities Move and Remove, and not a simple Update or a new activity type?