My problem with Apple is that everything’s designed to interoperate with other Apple stuff, and nothing else. It feels like a walled garden that doesn’t just keep users in, but also keeps those of us out who might want to try a single Apple device without spending many thousands replacing our entire ecosystem.
Absolutely, Apple is being resistant to RCS not because they think iMessage is superior but because they know it weakens their lock in power. I know I’m stating the obvious, but it just annoys me so much.
That’s my belief. They don’t derive revenue from their users data, they get it through hardware sales and service subscriptions. Google has proven that they will monetize their users data in not so pleasant ways. I like Google products a lot but don’t use them because of their business practices overall
Contrary to Apply making products harder to repair, efficiently locking in to their ecosystem with no way out? Apple ducks consumers every day. I doubt they’d gather all your data for the purpose of utilizing storage space.
I’m from Thailand. We have a term called เกมหมา (dog game) which means a shitty game that gets you raging. The list varies from person to person but every list so far includes Dota 2 and League of Legends (which I have personally played). Other honorable mentions include:
I am not sure anyone would care tho, for example see Threads! That’s just twitter Why not move to Mastodon? Why be a Corporate Sucker? But people do it. I still see a lot of people active on reddit, The change is simple and efficient yet… The yieldings low…
I feel like Threads is a special case. If you’re using FB or Insta you’re going to use other Meta services. If you got yourself off FB then its easier to not want to get back in bed with Meta. When people jumped ship from twitter we saw a huge percentage come over to Mastodon. There was no Bird company services that they were being pulled back to so the move to Mastodon was easier.
There is a group that will leave Twitter to go to Thread because a bunch of celebrities and influencers switch over. Those people dont care about anything related to the Fediverse.
Like grow some empathy. Hormone treatment isn’t for transitioning. It’s for reducing morbidity in patients and is prescribed on that basis. Fear mongering side effects is the same as poo pooing chemo because it makes your hair fall out.
If you are sad that your bigot opinions get you called a nazi, maybe it’s on you not to share these opinions. I don’t go chewing my clients ear off about startrek, it’s the same principal they aren’t a welcoming audience.
Maybe if you are still going to talk about these things, contrast the things with middling results to the things with the best results, not some boogeyman unknowns.
First they will add loads of new users and become the dominant instances. Then, they will add their own proprietary features that other instances cannot support. Finally, their extensions become the new de-facto standard, marginalizing the original implementations.
Since Meta has proven itself to be an evil company that does not act in good faith, it is better to not federate with them from the start.
Exactly this. In a federated network, the instance with the majority of users could dictate the protocol, forcing the smaller issues to continually adapt or die. See this post for a very real example of this.
But why do the current lemmy instances have to die if facebook decides to make ActivityPub+goldextra? We’ll just stay on our branch, maybe lose a few users who should know better. Facebook isn’t even making use of ActivityPub’s federation anyway, which is why we are here.
I’m actually afraid that they won’t defederate at some point but find some way to track the activities of the federated servers.
Becsuse you don’t move to the next phase until you reach a milestone. The embrace is the first step, to convert a small percentage of users of the original platform. Once you have those, you extend your features to have those users recruit more users to that specific instance or implementation, since they are more feature-rich or stable or whatever. Then once you have a critical point of users on your instance, you defederate from all others and develop your walled garden which now has all the users and the content.
That’s actually the topic of the talk! Around 1995-96, HTTP was picking up all kinds of use outside the academic community, and people were tacking extensions on left and right; one of the biggest was file upload support, which was done by throwing HTTP and email into a room and having them fight it out. Which is how we ended up with the monstrosity that is “sending emails over HTTP”, also known as “posting a form”.
The author of HTCPCP decided to codify some of his concerns with these, partly as a joke; I noticed long afterward that his joke was only standardized for coffee, which Personally Offended me as a citizen of a tea-drinking nation.
The number one question I would ask about HTTP would be: Why was the “Referer” header initially added and why wasn’t it removed from standard to this day. In my opinion the server, I’m going to, should never know where I came from.
I’ve just done some quick browsing to see if there’s a written-down motivation for Referer existing, and there’s this on the Wikipedia: “Many blogs publish referrer information in order to link back to people who are linking to them, and hence broaden the conversation.”
Which I guess makes sense, in the context of the original use of HTTP as an academic publishing protocol, but it’s gained cruft and nefariousness since wider adoption came about.
There are good arguments for stripping Referer from the standard, and yours is one of the most cogent; if Referer is still a thing in another 30 years, I’d be surprised.
There are far more robust methods of fingerprinting to spy on users anyway (adding up all the details of screen size, available fonts, language, os, etc, etc), so I don’t think removing the user agent would have much impact in reducing fingerprinting alone. It’s also useful as a quick and simple way to check the type of device, os, or browser the user is on and serve the correct content (download link for one’s OS) or block troublesome clients (broken bots)
Someone explained it really, really well on Reddit some years ago:
Hexbear.net started out as chapo.chat - a replacement for the defunct r/ChapoTrapHouse community after it was banned from Reddit. It launched one year ago today, based on a modified version of the Lemmy source code. At the time, Lemmy itself was only around a year old, and in an alpha state. Since r/ChapoTrapHouse had accumulated a long list of enemies in its time, a dozen or so members of the community did about a month-long sprint hardening Lemmy and adding features that reflected the needs of the community.
The developers of Lemmy maintained a pretty low-profile community, while the Chapo refugees were the exact opposite of low-profile, so the communities had divergent priorities. It wouldn’t be fair to demand the Lemmy developers drop everything they were doing to satisfy the Chapo refugee’s needs, but the needs of the Chapo community still had to be met for the project to be successful.
The process was very chaotic, and as a result, the fork of Lemmy used for Hexbear.net will likely never be capable of federating with the wider network of Lemmy instances. A handful of changes were contributed upstream, but many of them likely will never be accepted. None the less, it still abides by the AGPL license and the code is publicly available on git.chapo.chat.
The relationship between Hexbear.net and Lemmy is basically that the Chapo refugees decided Lemmy was the most viable platform to work with, and the Lemmy developers were completely blindsided. The Chapo git repository recorded about 2000 changes within the span of a month and not all of the changes were ideal or appropriate to adopt upstream. Within a week or two of launching, chapo.chat had more users than the flagship Lemmy instance. This was also before federation was officially supported upstream, even though that was always the goal of the project. Had the timing worked out differently, Hexbear might have been federated before adding additional features for their instance, but that’s not how things turned out.
undefined> The process was very chaotic, and as a result, the fork of Lemmy used for Hexbear.net will likely never be capable of federating with the wider network of Lemmy instances
actually hexbear is currently on Lemmy v0.17.0, when they update to version 0.18.0 they will be able to federate
This is crazy to me. All this time there’s been a 20k user instance out there just chilling by itself, and we may all start talking to each other one day.
GDPR Art 4.(1) ‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;
Posts in the Lemmy instances contain information relating to an identifiable natural person (by their user handle), as they contain the person’s ideas and opinions. Therefore the Lemmy instances are handling personal data and must comply with the GDPR.
To add another angle not mentioned: Something I’m not sure of but interested in finding out is if multiple communities allow for better curation than one single large one.
For example, imagine a huge sub like /r/pics. When browsing “new” on that sub, the content goes away and is refreshed with even newer content in practically the blink of an eye. Because sooo many people are posting all at once.
As a result, a lot of good content gets missed in the flood of everything, and you have to rely on time of day and luck to get your post recognized.
OTOH with duplicate communities, the content gets divided and conquered a little bit better. One userbase can browse new on one community, while another userbase can browse and curate content on a similar one. In the end, both communities content don’t get drowned out by the massive volume.
Once a multireddit like feature comes out, users like you and me can identify and group these duplicate communities and be none the wiser browsing all of them at once.
No central authority means people do what they want. Maybe the mods there decide to suck at some point, or the instance admins suck, or the instance goes offline, or someone just felt like having their own.
asklemmy
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.