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!
Still in development, but got #ActivityPub replies working! Once it goes live, replies from the fediverse will show up on Remark.as.
Last major issue is to add some basic moderation. Already got instance-level blocking done so I can easily defederate from bad servers, but want to make sure we can handle any potential abuse from individual users too.
The Podcast Index has an ActivityPub implementation, and now I can follow some of my more irreverent non-techie podcasts directly on the fediverse. So cool! Hopefully they'll add a Follow button soon...but in the meantime:
Find your podcast on the site
Grab the numeric value at the end of the url
Search for the podcast with this name {numericValue}@ap.podcastindex.org
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....
Can an instance operator running a derivative of Misskey (Sharkey, firefish, or maybe even Misskey itself) get in touch with me? I can't seem to federate with that entire pie of the fediverse... 401 Unauthorized 😬
Alternateively, if you've run into this type of issue before, any tips? Heh.
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
Now that for-profit tech companies are beginning to implement #ActivityPub, I think it's important to establish what we want with the #fediverse and whether federation with #Threads, #Flipboard, Tumblr, and the like bring us closer to or further from those goals.
With that in mind, I've come up with a few statements (in no particular order) that describe what I think is an "ideal fediverse" — a fediverse that's not necessarily realistic but that we should aim for:
No actor controls a large portion of visible activity.
Users can move between instances without penalty.
Creating and running an instance requires minimal effort.
People on or entering the fediverse understand the variety of available options.
There is no downside to using free and open-source platforms over proprietary ones.
These definitely aren't comprehensive, and if you have anything you'd add, let's discuss that! They're currently helping me reassess my stance on Threads now that Flipboard is also entering the stage, and I hope they're helpful for others as well.
I'll elaborate on these five statements in the comments.
I've been thinking a bit about this post regarding #Mastodon's responsibility to be compatible with the #threadiverse (#ActivityPub thread aggregators like #Lemmy & #Kbin). Right now, a thread from Lemmy or Kbin usually federates to Mastodon with truncated text and a link to the actual thread. However, many want Mastodon to be more compatible with threads so that the people over on Mastodon interact with the threadiverse more.
I was initially in agreement as a Kbin user. But having given it some thought, I think this is an unwise approach that'll only serve to overcomplicate platforms on the #fediverse. Yes, people on Mastodon should promote other parts of the fediverse (and vice versa), but complete interoperability shouldn't be expected of every platform.
As much as many would like it, you can't have long-form video from PeerTube, images from Pixelfed, threads from Kbin, blogs from Writefreely, etc. all neatly fit in a microblog feed. These are different formats made for different platforms, and the people making them are expecting them to be interacted with in completely different ways. When someone makes a thread in a Lemmy community, they're probably expecting that the people who are going to see and interact with the thread are people that want to see threads and are thus on a Lemmy instance (or another thread aggregator). If someone from Mastodon were to interact with it as if it were a microblog post, there'd be a big mismatch. People interact with microblogs differently than they do with threads — that's why they're separate to begin with. You don't see everyone on Twitter also wanting to use to Reddit because people who want microblogs don't necessarily want Reddit-style threads, and vice versa.
The other option, then, is to separate these different formats into different feeds or otherwise make them clearly distinct from one another. Kbin does this by separating threads and microblog posts into two tabs. While you can view both in the "All Content" tab if you'd like, they're styled differently enough that it's very clear when you're looking at a thread and when you're looking at a microblog post. This distinction lets users treat threads like threads and microblog posts like microblog posts, which is really helpful since the two formats serve different purposes and have different audiences. This option — clear distinction — is a great way to solve the conundrum I've been talking about… if your platform is meant for viewing all these different kinds of content to begin with.
And that's what it really comes down to imo. Mastodon is a platform for microblogging. Most people go to Mastodon because they want a Twitter alternative, not a Twitter alternative that's also an Instagram alternative and a Reddit alternative and a YouTube alternative. Even if you put these different content types in separate tabs, it would inevitably make things seem more confusing and thus raise the barrier of entry. Add a Videos tab to Mastodon to view stuff on PeerTube, and people are inevitably going to go, "Wait, what's this? Is this like YouTube? I thought this was just a Twitter alternative! This all seems too complicated," even if you tell them to ignore it.
It's probably best to leave Mastodon as it is: a microblogging platform that has some limited federation with other formats. The way Kbin threads currently display on Mastodon is fine. In fact, when I post a Kbin thread, I'm expecting it to be viewed via a thread aggregator. If people on Mastodon were part of the target audience, I would've made a microblog post.
Now, if you want to make something that lets you view everything on the fediverse via different tabs, feel free. As aforementioned, Kbin supports both threads and microblogs, though it comes with some challenges (e.g., trying to fit magazine-less microblog posts into Kbin's magazine system). However, this doesn't mean every platform on the fediverse needs to seamlessly incorporate everything else. I'd love people on Mastodon to promote and even try out Lemmy & Kbin more, but that doesn't mean Mastodon needs to also become a thread aggregator.
When Twitter changed hands and Mastodon had its 15 minutes of fame, on October 2022, it seemed that we were on the verge of a digital revolution based on Act...
I don’t think pitching #ActivityPub to existing social media makes sense. Adding federation to a non-federated social media service isn’t a net win.
You have to spend the time and money to implement it. Then you have to spend the time and money to maintain it. Most of the time, ActivityPub support is implemented as mastodon compatibility, not true AP support. This means having to constantly make sure you keep up with masto changes and constantly fielding issues with other implementations because you didn’t fully implement AP.
And after implementation, you don’t just gain access to a ton of new users, you have to take on the burden of moderating all of it (which is a persistent ant recurring time and money cost). And since the #fediverse has a ton of opinions on moderation, you’re always pissing somebody off.
And after all that, what you’ve enabled is an easy way for your users to recreate their social graph without your service. The idea of an interconnected social web is cool, and hopefully it’ll be the futrue, but it doesn’t make sense for profit-driven businesses.
Automattic's Tumblr/ActivityPub integration reportedly shelved ( notes.ghed.in )
When Twitter changed hands and Mastodon had its 15 minutes of fame, on October 2022, it seemed that we were on the verge of a digital revolution based on Act...