• 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle






  • How it works in the fediverse in general is that you log into your home instance and navigate to the other instances from your home instance. You won’t be able to log in with your Lemmy.world credentials on lemmy.ml. You can, however, view lemmy.ml content and interact with it (same for kbin.social) in the same way that I’m talking to you from a Lemmy instance.

    kbin and Lemmy are two different ActivityPub softwares with similar goals and so you can use them interchangeably. If you prefer being on kbin.social and you prefer the things kbin as a backend provides to you more than lemmy, then you can use kbin entirely and still interact with everyone else. That’s the magic of the fediverse. Think Gmail vs Outlook. It’s still emails. Just flavoured differently.


  • 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.




  • Apologies and thank you for the clarification, I was reading an earlier draft of GDPR that had information on companies with fewer than 250 employees. Not sure how Lemmy instances fall under this though, do you know?

    Businesses that are not engaged in processing of the personal data listed in Article 9 or Article 10 do not need to appoint a data protection officer (DPO or DPO as a Service) unless they are engaged in regular and systematic monitoring of data subjects on a “large scale”.

    I would also assume that deleting your information would only apply to the information located on the server and anything that’s already been propagated is up for grabs unless you request it from someone. Not sure how Lemmy as a software is responsible for being GDPR compliant. Again, I don’t know anything about GDPR teehee


  • Someone correct me if I’m wrong but GDPR doesn’t apply fully to small organizations (less than 250 employees) and mostly only applies if you offer goods and services which is not the case if you’re running a Lemmy instance. If you’re an instance owner with no employees because you’re not a registered business of any sort, you’re not on the hook for anything.

    Then again, I am neither European or knowledgeable in GDPR so someone please correct me if I’m wrong.