@[email protected] thanks for the kind words! Obvious I also think NodeBB's implementation is superior
What circular loops are you referring to?
Those who prefer GNU/Linux over any other OS.
@[email protected] thanks for the kind words! Obvious I also think NodeBB's implementation is superior
What circular loops are you referring to?
@[email protected] I recently thought about something similar.
On a create we send the activity to all followers (and mentions' inboxes).
On an Update, however, we'd need to also notify every user who boosted, as well as their followers.
I imagine it'd be the same for Deletes.
@crazycells it may, it may not, nobody knows exactly how search engines rank sites
@[email protected] said in Article vs. Note vs. Page:
For Mastodon, it's keepin' it real and sticking to purist microblogging. For Hubzilla, it's a way to spite them and their silly text formatting and image embedding antics. Hubzilla still holds a grudge against Mastodon for this.
Thanks for sharing this history. I'm certain Eugen would have a different view of how things went down, but nonetheless we have ended up at this impasse where a Note can have more than 500 characters, and some rich formatting, but not a full set (e.g. no block/inline images, horizontal rules, etc.)
@[email protected] said in Article vs. Note vs. Page:
And I'm not even sure if a vast alliance of Fediverse devs could change it.
Certainly that is one pessimistic way of looking at it. I am new to the fediverse developer scene and perhaps am still naive enough into thinking we can make a difference (<-- Mastodon users can't see it, but I put a smirking emoji there)
@[email protected] said in Article vs. Note vs. Page:
The conclusion I came to: Mastodon is probably more-or-less doing the right thing by refusing to render articles, but perhaps it would be nice to have a pop-out view for reading them.
Not every software needs to handle Article/Note differently. From a forum perspective, or at least in NodeBB, Articles and Notes are both just added to topics and the posts that make up topics can be of any length.
But additional handling could be introduced, like an optional "reader mode" for longer form content. Who knows.
@[email protected] said in Article vs. Note vs. Page:
I don't think that's the case, but maybe you meant something more specific than what you wrote? Several implementations support content-related AS2 content types (both base types and extensions) that do not fallback to as:Note or as:Question. For example, Funkwhale has "Libraries", "Tracks", "Audio" (etc.), PeerTube has "PlayLists" and "Video", PixelFed has "Story", Mobilizon has "Event", and so on.
You're right, and that's why I worded it like I did, because I personally don't know about the other softwares around and how they handle this particular use case. That's the main question I wanted answered, and you've helped me out there!
So lots of other federating software send out AS2 content types, that at least does reinforce the need for some sort of "generic" handler for unknown types.
At least from a the WG perspective we'd be concerned with Notes and higher order collections of Notes, but there's no telling where this may go!
@[email protected] said in Article vs. Note vs. Page:
on an ecosystem level, you get buy-in from implementers of those standards โ of which there should at least be NodeBB, Discourse, and Flarum, right? the process of standards alignment can be slow and painful, but it should be done nonetheless. the landscape right now looks like what it looks like because there hasnโt been any real protocol stewardship, and Mastodon emerged as a de facto steward of its own protocol. how we change that is by developing actual standards via FEP, WG, etc. โ and then advocating other implementers use those standards for better interoperability.
Part of the reason I started this topic was to confirm my suspicion as to why WordPress sends out Notes. Mastodon being a micro-blogging application means they have rationale for resisting attempts to add support for rich-text Articles and such (as @[email protected] implied), but it should never have gotten to the point where an implementor like @[email protected] would choose to use as:Note
over as:Article
.
Alignment from other implementors would apply some additional pressure for Mastodon to re-consider its handling of as:Article
.
@[email protected] that's fair. For me I kept getting sick of being logged out of my signal account on desktop, so now I stick to using my phone.
@[email protected] moved when my Framework laptop only recommended Fedora, haven't looked back!
Pop_OS! is great too, used it as my daily driver for many years.
There have been some scattered discussions I've seen over the past year that mention that @[email protected]'s WordPress ActivityPub plugin federates their blog posts out as an as:Note
, and that the only reason this is done is because Mastodon only treats as:Note
(and as:Question
) as a first-class object and relegates anything else to a fallback handler that takes a short snippet of the content, and shows a link back to the original source, thus losing any in-app benefits (boosts, replies, etc.)
Whether this is actually true or not, I do not know. So that's why I'd like to ask Mattias โ or anybody else with some context โ here.
For reference:
as:Article
: Represents any kind of multi-paragraph written work.as:Note
: Represents a short written work typically less than a single paragraph in length.as:Page
: Represents a Web Page.I have also noticed that Lemmy, perhaps out of principle, sends out an as:Page
for new generated content, and only the replies federate out as as:Note
. It has unfortunately led to some assertions that Lemmy's federation is "broken", even though it is arguably not the case.
@[email protected], care to weigh in?
I don't even blame Mattias for opting to send everything out as as:Note
.
End of the day right now it doesn't matter how Mattias or Nutomic represent their higher-level collection of data, because Mastodon is the largest implementor and neither they โ nor anyone else I know of, for that matter โ treat anything that's not as:Note
or as:Question
specially.
But that ought to change. The question is how, but this WG is not at the point where we start throwing around decrees and making up standards.
What's important to me right now is what the landscape looks like right now, and why that is the case.
N.B. The discussion here will eventually make its way to online real-time discussion at one of the future WG meetings.
Hey @[email protected] โ yes! You're around at a really great time for forums and the fediverse!
Three of the biggest names in modern forum software (NodeBB, Discourse, and Flarum) have signed on to work on ActivityPub, and we're starting to see the fruits of their (our?) labour now. NodeBB users can be followed, and Discourse and NodeBB categories can be followed.
ActivityPub and the fediverse has really enabled us to go in an exciting new direction, and we're stoked to see where it will take us.
Follow me or @[email protected] for updates
@crazycells said in Pre-Alpha ActivityPub-related bug reports:
edited federated posts are not updated on other sites?
We're sending the appropriate activity out (an Update
activity) whenever a post edit takes place.
I believe @oplik0 worked on this a bit, so if there are issues perhaps he may be able to speak to that.
However there is no guarantee that updates are properly handled across the fediverse. Best effort, I guess
@crazycells said:
originally- I just made a comment in a topic, but there it looks like I opened a new topic
That one's because SocialHub (more specifically, Discourse's implementation of ActivityPub) does not automatically traverse up the reply-chain to discover the original post. The original topic pre-dates @[email protected] and I syncing the categories together, so SocialHub does not know about the other posts in this topic. In that scenario, it will create a new topic like you saw.