Sublinks, crafted using Java Spring Boot, stands as a state-of-the-art link aggregation and microblogging platform , reminiscent yet advanced compared to Lemmy & Kbin.
But the author of PieFed, written in even more popular language than Java (Python) said:
The thing with the more twitter-style ActivityPub projects is they send activities to individual users inboxes a lot, whereas with the threadverse it's all shared inboxes. So there's a fundamental difference in the way they use the protocol which makes scaling those projects much more difficult. My gut feel is that adding full microblog support would increase the size and complexity of the codebase by at least 50% and triple the server load. Maybe much more. It just doesn't seem worth it.
A feature creep?
(maybe they see a bus factor = 1 as the only issue of /kbin, though)
I think the developer of PieFed is mistaken because the microblogging projects also use shared inbox a lot. My understanding is that for certain classes of posts, they actually just use it over a user's individual inbox and the remote server is responsible for delivering it from the shared inbox to the user's timeline.
There’s no reason to not block threads. If someone wants to use it, they can go there and use it. There’s absolutely 0 need for the fediverse to have Meta anywhere near it.
Say Meta does get federated. How long until they begin making contributions to ActivityPub? Before Meta decides it’s a worthwhile purchase?
Oh yeah that’s my mistake, it was a plugin for WordPress, not ownership. It looks like it was co-authored by someone as part of W3C to be an internet standard, but I don’t know if that changes much.
It’s mostly that if something somewhere can be bought, Meta will try to. I don’t see any reason to extend any open arms. Just because something is open source doesn’t mean that ownership won’t change or changes can’t be implemented or influenced.
That aside though I also feel that any integration is just asking for an invitation to reckless abandon. I think I mentioned in the previous comment, what happens as Meta begins making contributions to the open source protocol? As people looking to run their own instances come across a Meta build due to SEO? Maybe Meta money starts getting thrown at W3C and the co-author - who knows man. At that point, are we just going to use whatever forks that get Meta’s stuff stripped out from it?
Why risk 100m Facebook and Instagram users for the “potential growth of Masto-lemmy” when it seems like the very obvious reality is that Threads would just leech users from here after some integration then “oops Threads doesn’t support ActivityPub instances all your communities are with us now sorry!”. Not to mention the imposed tracking, dark patterns and monetization - which from my understanding instances can set fetch authorization, alongside defederating it would mostly prevent the data scraping? However I’m not entirely clear on all that.
Anyway, not trying to claim that I’m extremely well versed in the subject or the specific logistics of how it works, I just don’t see a single reason to trust Meta or why there would be any reason to federate with them.
I also personally have no issue having separate spaces for separate things, so to me the integration just seems a bit much. Some people have told me that’s a positive for them, and that’s cool. If I could functionally have one and actually interact in full I’d probably just use one account too. I occasionally view microblogs on Kbin alongside my subscriptions, I browse through here (Beehaw), both slrpnks lemmy and Mastodon instances, all different accounts. If I were interested in the content I’d have made a threads account (but the posts I get shown from Instagram don’t really pull any interest).
If someone is interested in using Threads, why not just use it there? I don’t entirely understand the reason we would need Threads to be seen in the same space as Twitter posts and Reddit threads all alongside our microblogs and posts (if say, Reddit and Twitter were also to federate). It just seems so much more centralized compared to the nature of the decentralized instances, I could see Meta’s interest here being to make their version of WeChat. A space where you have Microblogs, Forums, Marketplace, and games all in one spot no need to ever use anything else.
I dunno, I just feel like the desire to consolidate everything into a single bitty package is asking for a disaster. And to an extent, I genuinely can see this being the start of that path.
Anyway, sorry to get so long winded. Maybe I can take advantage of this idea and develop an app to centralize your Fediverse, Reddit, Twitter, Discord, GameFAQs and any account you can think of all in one spot. Then you can just interact from all of them as a single master user posting from each individual account as you come across the content. Support for all that will probably get pricey so I’ll just charge for extended account integration, maybe I can make my own subscription based off this to cover the cost (/s but feel free to use it!)
I think I mentioned in the previous comment, what happens as Meta begins making contributions to the open source protocol?
Then you don't use their version.
As people looking to run their own instances come across a Meta build due to SEO? Maybe Meta money starts getting thrown at W3C and the co-author - who knows man. At that point, are we just going to use whatever forks that get Meta’s stuff stripped out from it?
Yes? We're already using not-their-version, without the 100M users. If it's okay now, it'll be okay when we decide they took it too far and can go fuck themselves.
Anyway, I don't have a horse in this race. I have a Mastodon and Kbin account, and I don't know if either of them plan on federating with Threads or not. It just seems like a lot of alarm over nothing. Saying that people aren't going to want to defederate from Threads once they're federated is the same argument people would use to say I wouldn't leave Twitter or Reddit, and I easily left both of those.
Right, we left there over much smaller reasons than Meta. If Meta is heavily involved in ActivityPub, where to next?
Yes? We’re already using not-their-version,
Right, but for how long would we be able to do this? If Threads does federate and get popular, even worse, the communities here get heavily integrated with Threads, wouldn’t it only be a matter of time until Meta makes a push to keep users on their platform over this one?
Then you don’t use their version.
We come full circle here, if you’re not using Meta’s federated ActivityPub, it’s a ghost town because the goal is for Threads to replace us. What are you doing here on Kbin when all of the communities it is part of is now over on Meta’s instance?
I don’t know if it’s as simple as “don’t use it”. This is Meta we are talking about. You literally can’t not use Facebook to get away from it’s tracking, they track you regardless.
I also don’t really have a horse in the race. I’m with you in that yeah, I’d probably find somewhere else too. But I’m thinking long term with our space here, regardless of whether 41% of instances are defederated, Meta’s involvement is a bad thing due to their immense wealth and, in my opinion, high likelihood they will implement changes that we can’t get away from. I’m not so sure it will be as simple as not using their version. I also don’t think it’s wrong for people to be aware and vocal about this, even if it may not immediately affect us in the moment. Again, we left Reddit over basically the complete inverse of this situation. Reddit closing 3rd party apps to get users into their app vs. Threads adoption of these 3rd party apps to get data from these users.
Why would we be okay making it so that developers and users have to work around finding Meta-stripped builds when we can just… Mitigate how much Meta is able to do it in the first place?
When I said I don't have a horse in this race, I meant I don't much care whether my instances federate with it or not. You're not the first doomsayer over Threads, but I have yet to see anything that would stop this decentralized thing from allowing us to just de-federate or otherwise ignore any changes Threads makes to ActivityPub after the fact. We literally CAN not use Facebook. You may as well say Microsoft is trying to extinguish Linux, but I don't think they could if they tried. Yes, I'm familiar with EEE, but the things these technologies are used for appear to make them inextinguishable.
That’s not what I was saying, or meant to say. I was saying they are tracking you regardless of whether you do or not. Why allow that to extend further by embracing them into the fediverse? I also don’t think they are inextinguishable, I think there a wide, wide range of ways to fracture then consolidate.
Alas, time will tell and we can only hope it amounts to nothing and all us worrywarts are proven wrong as Meta does nothing but integrate then occasionally serve ads (with of course, all the background tracking).
Out of curiosity and completely unrelated, do you have an Android phone? Not Google? If so, it may be worth checking your active processes running under dev services, there may be a Meta Services and Meta Services Manager running in the background. It’s worth disabling these from the apps list, they literally don’t do anything but serve up ads and track you.
On by default through many phones and carriers, gotta love it.
I’m a fan of static site generators, but unless I’m missing something, this won’t replace the most important part of Bandcamp: a platform for selling music.
@ono Yeah, fair point. It's more geared towards patron support and donation prompts, but it does support things like redeemable codes, which could be paired with some kind of recurring donation system.
It does make me wonder what it would take to build in a checkout system, and whether that goes way beyond what a static site can handle.
“Firefish is a hot new microblogging platform”: it’s not that “new” at all, #Calckey, which has been around since 2021, has only recently changed its name to Firefish
the antennas / news picker had apparently not yet been fully understood by the author: they do not fill retroactively and it is a full-text search that also finds parts of words. Therefore, if it doesn’t fit, search words can be excluded - it works very well for me! If you use it for a little longer instead of just taking a quick look, you can use it to structure your content very well.
“Lack of an official app is kind of disappointing”: “official” apps are perhaps important as a “brand” for some, the so-called “Mastodon” app is also the worst app ever for Mastodon (fortunately with many better alternatives). The PWA for Firefish works great on all devices, if you don’t want to miss out on any features and want the best look, you don’t need an app.
The biggest hindrance at the moment right now is the flagship instance at firefish.social:" The instance has clearly communicated that it primarily serves as a test instance, i.e. it does not strive for or want to guarantee stability. In contrast to mastodon.social, Firefish itself also makes clearer reference to the selection and there are now really many Firefish instances.
For me, the biggest disadvantage of Firefish at the moment is that it doesn’t yet federate properly with Lemmy.
Now, I am on the can we ban Threads train, I wasn't at first because they hadn't gotten involved in actually joining the rest of us, now they are and they've admitted they want all our information too, I just don't want any part of that.
Things collected from fediverse participants that interact with Meta users...
- Username
- Profile Picture
- IP Address
- Name of Third Party Service
- Posts from profile
- Post interactions (Follow, Like, Reshare, Mentions)
They've never met a piece of data they didn't want to mine, have they?
I think the implication is that threads/meta is going to use it for different purposes than your average fediverse application/server owner would.
However, it is kind of a silly argument to bring up in the context of fediverse since everything you share publicly online is, well... public info from that point onwards - even more so in the fediverse that by design sends and stores it to countless other, privately owned and maintained, servers beyond your control. This comment is public and any other individual or company can get it whether they do it through activity pub or by just scraping it off any of existing (or their privately owned) instance.
The real risk threads poses is competition and taking away content creators from mastodon, indirectly pushing everyone else under the facebook's corporate umbrella again. I want FOSS to take over but if there's nobody actually using it and everyone is still creating content elsewhere then there's few reasons to stay.
I don't understand the point of this article at all. How would an instance federate without processing these information? (And I think the IP cannot be collected; not sure why the author indicates so without source.)
Not sure if the author understood anything about the fediverse, either. Feels like an AI-generated article, honestly...
The point of the article is to appeal to people's hatred of Meta (which is well-earned, admittedly), not to actually say anything meaningful.
Having observed conversations about Threads here and on Lemmy, it's a pretty dependable tactic. I completely understand not wanting to associate with Meta and not trusting their intentions, but there are plenty of things to criticize them for without trying to whip up a fury over what's objectively not problematic. But this is the internet and people like being in a fury, so whip one up they will.
@BraveSirZaphod Hey, I'm the guy that wrote this. While I absolutely hold negative bias towards Meta, the point of the article was not to produce a piece of propaganda, but instead illustrate that their policies have updated to acknowledge the existence of third-party accounts on other servers, that they will be collecting data, and that this is likely a sign that federation may be happening sooner than expected.
Not everybody is happy about that, and some developers are working on hardening their applications to protect against unauthorized access for edge cases related to this.
wedistribute.org
Hot