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

help-circle







  • brettvitaz@programming.devtoPiracy@lemmy.mlBoxing sources
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    11 months ago

    There are several risks. The two most obvious ones are

    • you run the risk of forgetting to use https and everything you are doing is visible to your isp
    • the site admin doesn’t know enough to turn off http so they are probably not securing your data in any meaningful way

    To me it’s an indication that the admin doesn’t know what they’re doing and will likely suffer a data breach eventually













  • When I look at the many communities with the same names, I completely stops me from interacting with them. Most of the time I know they’re going to be copies of each other with a bunch of duplicate content reposted to infinity.

    I think your example is interesting but i disagree with your assertion that it some how facilitates finding niche content.

    For example it would be difficult to have to explicitly know that obscure-instance.xyz/c/games hosts content about 90’s graphic adventure games from the Netherlands and programming.dev/c/games is actually about game design and not games generally. A better way, IMO, is to just name your community what it is. Names likeadventure_games_nl and game_design offer a significantly better user experience. If we want to make the fediverse feel accessible to people, it has to be easy to find what you’re looking for.

    This whole thing feels like crypto where everyone has their own coin and they only kind of work together if you have some kind of exchange and some people accept Bitcoin and not Doge. It’s just too complicated for non technical people.