Announce and Undo(Announce) in Mastodon
Technical Discussion
3
Posts
2
Posters
16
Views
-
NodeBB federates out the
Announceactivity in two ways.- The "plain object" way, which is an
Announceactivity wrapping an object (either a uri or the full object itself.) - The "1b12" way, which is an
Announceactivity wrapping another activity (e.g.Create)
Up until now I haven't needed to handle the reverse (which in AP-speak is the "undo" of an activity), but since NodeBB sends
Announcewhen moving a topic in to category, it now makes sense toUndo(Announce)when moving a topic out of a category.My first interop test with Mastodon didn't work, and it turns out that Mastodon checks the
idof the embeddedAnnouncefor a match. It doesn't infer it based onactor/objectcombination.Once I matched up the IDs, the
Undowas processed correctly.I also noticed that
Announces sent from Mastodon have apublishedproperty, although this is not relevant inUndoparsing. - The "plain object" way, which is an
-
What does undoing an announce do, in Mastodon? Remove a boost?
-
What does undoing an announce do, in Mastodon? Remove a boost?
Yep, that's basically it. It's not really a concept in threadiverse implementations since group actors do the Announcing for synchronization.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
-
@julian @saskia @evan or do you think that anybody knows , that #stupidhashtag in the system is https://mastodon.social/tags/stupidhashtag and it's type is https://www.w3.org/ns/activitystreams/hashtag
But as far as I know, this type is not specified at all!
-
@julian @saskia @evan A tag, a hashtag, a SKOS concept, all IRI or URL! Users don't see the concept behind it. If we developers do it right!
-
@naturzukunft2026@mastodon.social absolutely not, sorry.
For the simple reason that it requires user education, and ain't nobody going to go around teaching 7bn people how to use SKOS.
The beauty (and admittedly a downside and source of a lot of noise) is the hashtag's ubiquity and simplicity. Anyone can make one, anyone can name it whatever they want.
-
@julian @saskia @evan
The only way to give hashtags uniqueness and Semantik.Bad practice: use just words.
-
There are a couple of parallel development efforts tackling the problem of hashtags. The main drawback is that while you can use them in your posts and search for them to find additional content, the reach and visibility of the hashtag is restricted to that of the instance's own visibility.
In other words, looking up a hashtag on your instance probably would not give you a complete view of the use of that hashtag worldwide.
@newsmast@newsmast.social channels The first I'd heard of it was Newsmast's "channels". How they worked was opaque to me, but after seeing @saskia@backend.newsmast.org's presentation, I now know it is collating use of hashtags into a broader topic (e.g. #Asenal, #AFC, plus many others into "Arsenal") tags.pub @evan@cosocial.ca came up to me after FediMTL and asked whether I'd looked into his FOSDEM presentation about tags.pub, which aims to do something similar, although user-facing. Users can follow individual "tag" actors and they then receive all content tagged as such. I will have to watch the presentation as tags.pub is headless and has no landing page! :laughing: FediBuzz Relay ActivityPub.Space is following this approach, where I set up NodeBB to subscribe to a couple of relevant FediBuzz relays: #activitypub, #fedidev, #fediadmin, #fedimod and #fedimodsIt's interesting to follow the convergent evolution of solutions to solve a single problem. Right now NodeBB gives you the tools to set up the FediBuzz relay connection + auto-categorization rules, but it's not exactly user-friendly for admins.
The ideal flow would be something much more high level for admins. An additional field during category creation where they can specify hashtags they'd like to follow globally. Simple, understandable, hides all the backend complexity away.
It is worth looking into additional solutions (like tags.pub or the Newsmast channels) so as to not be tied to a single provider in the backend.
-
For generating a summary for long-form text, I'd suggest these techniques in rough order:
- Let the user to define a summary manually - either with a marker in the text, or with a separate input element
- Use the whole text if it meets the rough guidelines (~1 paragraph, a few sentences, about 500 chars) in b2b8.
- Use the first paragraph if it meets the rough guidelines (a few sentences, about 500 chars) in b2b8.
- Truncate the first paragraph and include an ellipsis ([...]).
-
Some bloggers follow a similar practice, especially since blogging software often uses the first paragraph as the summary in RSS and Atom feeds.
