Threadiverse Working Group
-
@shoq In my mind, articles are more appropriate for blog posts. But on the backend, we can literally use any of them, as long as we can pass on the required parameters indicating whether it is a top level post or a comment to a thread.
I just find it odd that ActivityPub has nothing called "posts" and "comments." It is almost as if they are assuming all posts are top level posts, which is how Mastodon operates. -
Scott M. Stolzreplied to shoq on last edited by [email protected]@shoq Another thing to consider is that although we may agree to use one type, other platforms might not, and we would have to be able to parse what they give us. So if one platform uses article (or whatever) and another uses note, we have to be able to accept their posts anyway.
-
@[email protected] @[email protected] yes, unfortunately we can't make any implementor do anything but I think a published set of best practices would go a long way toward eventual consistency and interop between instances.
-
@shoq said in Threadiverse Working Group:
Have you considered rules for tuples? Like should the main entry be the the left or right of a descriptor or qualifier?
Since categories are standalone, we don't enforce hierarchies on the handles. You can name them whatever you want.
-
@julian I get that, but a lot of really bad habits will likely be impossible to rectify later. Not suggesting anyone be forced to implement anything, but it's another case were "best practices" would avoid a lot of unforced errors. Whether they see categories as random topics, or controlled vocabularies for any particular mission, some skilled librarians might be invited to describe some of those and provide working examples. This won't matter for stand-alone communities, but it might matter a lot for federated communities looking to optimize their knowledge sharing and distribution as things evolve.
-
@shoq NodeBB is designed to be flexible enough to allow you to construct a hierarchy that makes sense for your particular community.
One's interpretation may not match others', and that is ok. We've found that being overly opinionated in implementation forces you into a corner and leads to feature requests asking for exceptions.
-
J julian referenced this topic on
-
@[email protected] said in Threadiverse Working Group:
I have been thinking about SMPT integration and older web standards like NNTP as well. I used to love UseNet in the 1990's / early 2000's, was on alt.os.development, comp.compilers, and comp.lang.misc, tried as I could to get at alt.lang.development group but got the cold shoulder from the non technologist alt group powers that were at the time.
Also GitHub issues intergrate with email well and this can be useful at times more for quick alterts or quick replies. Thinking about this it might be nice to integrate GitLab with ActivityPub/Streams, wether this would be good in practice or not is another matter.
Interoperability needs to be our buzzword for user friendliness.
Dunno you have probably came across this but it made me laugh
Yes Plan 9 was one of the earliest sound multi process OS's IIRC.
-
@julian @[email protected]
Peeps, if we could further fill in the terminology spreadsheet and maybe use this as a start to deeper map between the platforms/protocols :- https://docs.google.com/spreadsheets/d/1tPZXywqFZe3xXx_fV9icNHLOkSrXx3_rHhPeRmMBZR4/edit#gid=0 -
I am interested in this topic. Please add me to relevant groups/calls. My mastodon ID is: @[email protected]
How do I catch up on the current state of things? All I know is that Mastodon and some other software allows subscribing to hashtags: https://fedi.tips/how-do-i-follow-hashtags-on-mastodon-and-the-fediverse/
But this is neither universal nor sufficient. Each community might use different hashtags for different "topics".
