AtomHeartFather

I’m just an old guy with a lot of opinions. I am a sysadmin by trade. I like Linux, cool gadgets, Sci-Fi, DC comics, bass guitar, prog rock/metal, and annoying my kids with dumb dad jokes.

  • 9 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle








  • Community discovery that spans all federated instances should be one of the top things that development should be working on. And it should be integrated into Lemmy, not as a separate website people have to go to and search.

    Peoples are lazy. They don’t want to have to go to some separate website and then search for something. And lets not even get started on the difficulties of adding a remote community if your instance doesn’t know it exists, its wonky at best.

    If a user cant type “Stephen King community” in the search bar on their instance and then get results, they are either going to assume it doesn’t exist and give up OR they are going to be hitting that “Create Community” button.


  • Of the themed instances that exist now, I’d be willing to bet that in addition to their local communities they host that they also subscribe to other communities that aren’t strictly related to whatever theme they are going with.

    For example, I’m sure the Star Trek instance also subscribes to the lemmy@lemmy.ml community so the admin can stay abreast of Lemmy news. And probably also follows other technology related communities as well.

    I think most people would just want to gravitate to whatever they want to be identified with. There’s nothing stopping you from joining a music themed instance and then adding some non-music subscriptions to your list. It doesn’t force those subs on anyone else on the instance.

    And if you don’t want to be identified with any specific topic or community, you can always join a general Lemmy instance like Beehaw or Lemmy.world and subscribe to whatever you like piecemeal.



  • Honestly, I hope not.

    For example, if all the “programming” communities ended up on a single instance, that is still a single point of failure. I think it would be better if they were spread out a bit. That way if the programming themed instance went down unexpectedly it wouldn’t take ALL the programming communities out with it, only the ones it hosts.

    There’s nothing stopping anyone from creating a programming themed instance and then subscribing to various programming communities on other instances and then creating their own local communities to fill in the gaps. And ideally, I think that’s what should happen.




  • Hot take. I think the instances that are trying to be Reddit are the ones that give their users carte blanche to create new communities without any thought of looking to see if the same community exists elsewhere. I’d prefer that community creation be limited to the admins of each instance, that way they could - hopefully - at least do a cursory search to see if the community exists already and then just add it to THEIR instances subscriptions. There’s a reason why every community shouldn’t be on a single instance. It’s a single point of failure.




  • I guess at the end of the day that I don’t have many concerns for privacy. I am not searching for things that might get me on a watch list. Searching from my private instance is no more/less secure in terms of privacy than it would be if I did a Google search. The search endpoints (Google, Bing, DDG, etc) all know the IP that the search is coming from even if its passing through SearXNG first. So if I was doing something shady, I could easily be tracked down that way.

    The main reason I run my own SearXNG is so I can strip ads and search multiple search providers from a single search.




  • I tried doing that with a previously unsearched/unsubscribed community as a test on my own instance, and I got a 404: couldnt_find_community error when clicking the link. As you stated, it seems like in most cases that special link will not work unless someone has previously manually searched for the same community in your instance.

    I think I’d rather link directly to the instance for the community than get a 404 error. For most people, getting the 404 will just deter them from proceeding further.

    Perhaps it would be best to include both links in a post?


  • Making specialized instances does not in any way make hopping around necessary. If you join a specialized instance that doesn’t already sub to the communities you want, you just add them.

    Example: I join a Star Trek themed instance that has a bunch of locally created star trek communities. I want to sub to all those, but i ALSO want to sub to the homelab community on beehaw. I just subscribe to !homelab@beehaw.org FROM the star trek instance I am a member of. That star trek instance will then start syncing the homelab content from beehaw and you can read and reply from the star trek instance.

    Conversely, if someone has an account on beehaw.org and they want to read a star trek community based on that star trek instance, they just need to sub to it FROM beehaw.org.