Loops is a new platform for sharing short videos, and it's open source + federated using #ActivityPub
We're really excited to share this sneak peek that showcases the new onboarding flow and discovery features (Connect Mastodon) and look forward to the upcoming beta release!
Serious question for those that this is relevant to: if you don't understand how ActivityPub works, even a little bit, why do you feel the need to have opinions on how it should work?
Isn't this backwards as hell? Shouldn't you try to understand how something works, then ask why it is that way and if it's intentional?
Too many people here have this strange opinion that they have some sort of privacy, even if their profile/posts are set to "public".
This is just simply not true. We're on the internet. There's over 20,000 Fedi instances and there's just no way to manually parse them to make sure there's no "bad actors" using your "public" posts for whatever the hell they want.
We already see this happening with things like NewsMast which is aiming to be a "news" app where their users don't have to login or register to a Fediverse server, yet they will see posts by Fediverse users from bigger instances based on "categories".
Maybe do some research about how the protocol works and how it's VERY opt-out to the core, before you have opinions on it. Just saying....
Who can see my posts? I am super curious as to how far this #activitypub can travel? Learning the #fediverse is interesting but a tad confusing for the laypeople like me. If anyone has an analogy do share. Visualizations help. #mastodon#server#instances
OK, I've got a question for #ActivityPub developers. I'm working on an extended example for the O'Reilly Media book I'm writing, focusing on the federation protocol. I'm going to cover using HTTP Signature, handling and sending the important set of Activity types defined in the AP spec (Follow, Create, Add, ...).
Great to see the ActivtyPub Plugin continue on a fast development timeline:
The WordPress ActivityPub plugin has been updated to version 2.0. The major feature of the release is better comment federation. Comments are now properly threaded, which makes it much easier to follow and understand threads where people are replying to each other. Comments are now also bidirectionally federated. Creator @pfefferleexplains:
“When you respond to comments from the fediverse on your blog, they will now be federated. This allows you to finally engage in (threaded) communication back and forth directly from the comment section of your blog!”
"ActivityPub and ATProto break #siloing in different ways. #ActivityPub is built around URLs and can "socialise" more or less anything on the Web, which is great, but they don't touch the underlying substrate—either you run your own server or you…are at the mercy of an admin. #ATProto, on its side, provides a good initial foundation for an extensible #PDS designed around user agency and credible exit.
…you can be guaranteed to be able to take your content elsewhere." https://berjon.com/ap-at/
One of my favorite parts of this interview with @tchambers is when he wraps up with his 2024 predictions for the #Fediverse and #ActivityPub including the things he's looking for as this crucial election year plays out. He gives a sweeping and insightful summary of the most important efforts now underway which will bear fruit this year.
@tchambers, author of the Twitter Migration report and admin of indieweb.social, is an internet steward everyone should know. In this podcast with @mike, Tim expounds on social media’s thorniest issues and explains how the Fediverse offers a better social home than anything we've had before.
What I personally want more than a good test suite in #ActivityPub, and possibly a lower bar, is a good reference implementation.
Specifically, I'd want something that:
Implements all nontrivial requirements of the spec.
Implements a significant percentage of the data vocabulary
Can handle a nontrivial amount of traffic. It doesn't need to be optimized for it, but it can't fall over in a stiff breeze—analysis should be comparable to analysis of a prod system, just at smaller scale
So, how is #ActivityPub implementation in #GitLab going? Steadily, if a bit slowly!
In the last four months, we've been working on implementing the first ActivityPub actor, the one allowing to subscribe to projects releases. The ActivityPub part is already written, but there will still be a couple month before it's fully merged. Turns out that the most time consuming part is code review : there is no dedicated team to this (but there is a dedicated developer assisting me, thanks Patrick!), so people reviewing code discover ActivityPub at the time they have to review it (and, by the way, it's incredible how they get out of their way to help a contributor on such a complex subject, they rock). For that reason, we have to make smaller than usual merge requests, splitting the feature as much as possible, and then some again, to make it as easy to understand as possible. And even then it usually takes about a month to get one chunk merged.
I'm interested in hearing from #ActivityPub developers who've successfully mapped #OpenGraph properties from <meta> tags in Web pages onto the Page type and its properties in AS2.