I don't think people are realising the danger the Fediverse is in.
The only thing stopping corporations and VCs taking over this place is that the Fediverse is spread out on many different servers, which makes it very difficult to purchase.
If most of the Fediverse ends up on mastodon.social, which is now a strong possibility, there will be nothing to stop most of it being sold to Musk or Zuckerberg or whoever.
The bigger mastodon.social becomes, the more likely a buyout is to happen.
On top of that, #Mastodon deliberately breaks #ActivityPub specs, and refuses to fix that. It can already be observed that, instead of forcing Mastodon to be interoperable, other projects start breaking their implementations to please Mastodon instead due to its market power.
I'm thinking that Task Management is a typical candidate for a standard #ActivityPub vocabulary extension to be created for it. One would even expect a well-known ontology to be available for the purpose.
In any case then it could become a #FEP and until that time you might add an issue to the new fediverse-ideas repo to track this.
All these talk about #BlueSky and complaints about #Mastodon this, #ActivityPub that, #Fediverse this, and #Decentralisation that, are mostly questionable(?) since many haven't seriously looked around the fediverse. It's like saying burgers are bad because you've tasted McDonald's yet there are better burgers from #Jollibee.
The problem stems from the fediverse ending up unofficially represented by a very limited-feature software and most are not willing to do their due diligence (one would think they'll check out the forks at least). Before championing about the new kid on the block, before claiming that the fediverse is this and that, look around first.
What you've known as the fediverse, so far, is only based on what happens to be the software with the least feature set. Mainline Mastodon will get better, but it is what it is currently, as far as comparison with similar fediverse projects.
No one is saying you are not allowed to complain, just look around first before you make claims about the fediverse.
Also, no one is saying #ATP shouldn't exist. By all means develop it! Innovation and improvements come from seeing ideas come to fruition instead of staying as theories. Having different branches of development is better than getting stuck in one particular way of doing things, or line of thinking. It's all good and I think anyone will agree it is much welcomed.
Here's a #challenge: Since you have time to research a non-fediverse network, why don't you explore what the fediverse really has to offer, with the same effort and enthusiasm? Mastodon is not the fediverse, so you can not judge the fediverse based on it. That's like saying China is Asia, and you judge Asians because of mainland China.
Take the challenge, then publish the results of your journey. Good evening, and Shalom!
@pfefferle Does anyone know a good example of a #WordPress site using the #ActivityPub plugin yet? I'm curious how it looks when viewed from my instance.
It still feels a bit beta imo, but it’s easy to see why the design is more likely to have mass appeal – especially once it becomes a bit more stable.
I’m not yet motivated to move anywhere yet, mostly because @ivory has greatly improved the #Mastodon UX for me.
But overall it’s great to experiment in the #fediverse. You get to see the magic of #ActivityPub in action: the simple idea that the apps we choose should not bar us from talking to each other.
Can anyone point me at a diagram of typical #ActivityPub protocol interactions? More detail than the extremely basic pictures in the ActivityPub spec, and less detail than actual JSON-LD blobs, if that makes sense? Asking for, um, tomorrow's class :-/
What am I reading for some nice light late night reading? Why, it is the #ActivityPub spec! And #ActivityStream! And #ActivityVocabulary! I want an ActivityPub project to work on. Starting here:
The one thing I do think the AT Protocol is better at than #ActivityPub is data portability. Being built-in at the protocol layer so that you don’t have to do the migration shit (which doesn’t bring your posts) is better. It just is. I think ActivityPub has more potential overall for the social web beyond just Twitter clones, but that part of #ARProtocol is better.
It's good for everyone in the decentralized social space to learn off of each other. Not just be reflexively in tribal camps.
And #ActivityPub folks need to move faster on their own nomadic identity systems, rather than diss others. But most I see that are serious on the AP side are seeing that as better way: learn and move faster.
I feel like I've largely rebuilt the community I had on Twitter over here on #Mastodon and am just not interested in #BlueSky right now. I'm honestly disappointed that they deliberately chose not to have #ActivityPub compatibility. Also, I don't really trust Jack, either. He very intentionally pushed for Elon taking over Twitter. Going to BlueSky seems sort of like falling for your ex again because they changed their name from Brianna to Bri and started wearing a leather jacket.
There seems to be a growing amount of uninformed, negative posts on #Mastodon about #Bluesky.
It’s unfortunate that a platform which believes is populated by open minded people do not gather information themselves to form a balanced opinion, but rather jump on the “echo chamber” bandwagon instead.
Kind of reminds me of behavioral patterns on #Twitter. Remember it’s not the platform, but what you bring with you that matters.
@codesmith for me it’s account portability. The way #Mastodon (and others) are currently designed leaves too much in the hands of instance admins. We’ve seen instances disappear, and potential misuse lures around the corner as well. Account portability gives more control and freedom over your social media data.
I too hope the new interest, and competition, wakes up people and causes long awaited wishes to be realized both for Mastodon and #ActivityPub.
@alastor8472 Reasonable account portability is #1 on my wish list of next steps that I feel should have been implemented long ago. It also seems like something that the Mastodon devs in particular are not interested in implementing any time soon.
@evan Rather than an obligation, I see it as strategically beneficial.
By making at least a minimal effort to publicly chart a path towards interoperability between the #activitypub powered #fediverse and other open (but not outwardly cooperative) protocols, we can effectively reveal their true motives.
Extend a genuine invitation of cooperation, then we’ll see whether they act in accordance with the ethos of the convivial open web or the winner-takes-all mindset.
I'm a bit embarrassed to say that It's been a long time since I caught up with how the @Flipboard is evolving. It's just so well done, and chock full of features and ideas I once criticized it for not having. And now that it's partly integrated with Fediverse, I am seeing all kinds of new possibilities for it. I'm allocating a lot of time next week to studying it more closely, and seeing if it can become the foundation of a really cool curation idea I've been noodling for years.
@shoq@Flipboard Unfortunately we never got around to implementing an API though we certainly thought about it. As we look to #ActivityPub that may finally change. Let me know what you'd like to see from an API if you have ideas here.