I write English / Escribo en Español.

Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.

This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.

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

help-circle

  • If you are using Gnome distros: you can feel exactly what it feels like getting back to working in a restricted, overhyped, overbranded environment like Windows.

    If you are using Ubuntu: you can get advertising during your system’s software upgrades. No, really.

    If you are using Arch: you can post aroudn the internet saying you use Arch btw.

    Depending on the distro, you can use some alternative software stacks, but that’s mostly the backend (eg.: systemd versus openRC, Apache vs Nginx, X vs Wayland); most “desktop app” level is mostly the same for each desktop environment, is kinda the point.









  • Usually the issue of media storage (photos, videos, etc) is brought in as an Issue. For now I’ll skirt the “legal ramifications” including copying media and privacy, as those are an ever changing landscape of legal wanking that wankers can speak of much better than one can (and evil wanking still needs to be fought against).

    One idea I’ve seen floated around is to have some sort of cooperative CDN for instances. Let’s say four or five relatively kindred instances, make a commitment to last and pool their resources to maintain a joint CDN from from which they’ll get their “media federation” from. This would reduce costs and issues a lot, since by the very nature of the fediverse, if everyone builds their own caches most of those caches are going to be hosting most of the same content. Basically: deduplication, but the poor man’s version.

    Another alternative is to just ditch storage of videos and images. Just take links to Elsewhere and let Elsewhere handle it.





  • Security is not a state but a scale, and is gauged against everything else.

    From the perspective of a privacy / security zealot, a smartphone is SOL as soon as they lave the factory, as not only not even OTA updates keep them safe (and you can argue that with some manufacturers such as Samsung, OTA does is the primary risk vector!) but they can eg.: ship with unfixable vulns at the hardware level that would lead to ditch the whole thing anyway.

    So long as there isn’t something like a state-funded program for citizens to renew their phones every ~2 years for fully open ones, I’d not worry much. After all, the other option would be not using a phone because current ones are a PITA and just as vulnerable from the other end.





  • I’m not sure if there’s a solution here, but I’d like to urge people to avoid lemmy.ml hosted communities in favor of communities on more reasonable instances.

    It depends on what exactly do you consider the problem to be, but my understanding is that solutions to the more general problem of “what server a community is in” are already in the works (multicommunities and stuff).

    As for a more local kind of change… Be the change you want to see. Start up, and maintain, those alt communities that would serve as counterweights to the ones that are in .ml. Also, understand why they are in .ml in the first place yet still manage to function.