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

help-circle
  • Another aspect is the social graph. It’s targeted for normies to easily switch to.

    Very few people want to install a communication app, open the compose screen for the first time, and be met by an empty list of who they can communicate with.

    https://signal.org/blog/private-contact-discovery/

    By using phone numbers, you can message your friends without needing to have them all register usernames and tell them to you. It also means Signal doesn’t need to keep a copy of your contact list on their servers, everyone has their local contact list.

    This means private messages for loads of people, their goal.

    Hey, we know this account sent this message and you have to give us everything you have about this account

    It’s a bit backwards, since your account is your phone number, the agency would be asking “give us everything you have from this number”. They’ve already IDed you at that point.




  • To me I’d consider Linux not standardized since anything outside the kernel can be swapped out. Want a GUI? There are competing standards, X vs Wayland, with multiple implementations with different feature sets. Want audio? There’s ALSA or OSS, then on top of those there is pulse audio, or jack, or pipewire. Multiple desktop environments, which don’t just change the look and feel but also how apps need to be written. Heck there are even multiple C/POSIX libraries that can be used.

    It certainly can be a strength for flexibility, and distros attempt to create a stable and reliable setup of one set of systems.


  • ZFS doesn’t have fsck because it already does the equivalent during import, reads and scrubs. Since it’s CoW and transaction based, it can rollback to a good state after power loss. So not only does it automatically check and fix things, it’s less likely to have a problem from power loss in the first place. I’ve used it on a home NAS for 10 years, survived many power outages without a UPS. Of course things can go terribly wrong and you end up with an unrecoverable dataset, and a UPS isn’t a bad idea for any computer if you want reliability.

    Totally agree about mainline kernel inclusion, just makes everything easier and ZFS will always be a weird add-on in Linux.




  • My partner worked for a local council. They reset your password every 90 days which prevented you from logging in via the VPN remotely. To fix it you’d call IT and they’ll demand you tell them your current password and new password so they can change it themselves on your behalf.

    Even worse, requesting a work iphone meant filling out an IT support ticket. So that IT could set up your phone for you, the ticket demanded your work domain username and password, along with your personal apple account username and password.


  • It was meant in jest, I should have contrasted plain text / cipher text to be more clear. Though it’s a similar kind of extenstion to email technology that they are advocating against.

    These folks want to read their emails in their terminal email client, and for you to cater to their limitations. If you use tuta and send them an email, tuta just emails them a link to view the message on tuta’s webapp. I’d say this anti-HTML group aren’t fans of that.

    Not to argue semantics, but I would consider encryption in general is a change in message formatting. The client needs to change how the bytes are interpreted. It adds complexity, and clients may not support it, their exact arguments against HTML.





  • IPv6 isn’t just larger addresses, it was meant to totally remove the need for layer 2 / MAC addresses, bus networks, DHCP, and broadcasts. Since the plan was to get rid of the 12 byte ethernet header, the 24 byte increase in IP addresses would only be a 12 byte increase in header at the end of the day. WiFi wouldn’t need three MAC addresses in every packet. IPv6 only achieves it’s true potential with a complete switch over.

    I personally don’t think that can ever happen. The opportunity to switch everyone over is absolutely long gone. IPv6 isn’t an extension of v4 or a compatible replacement, like ASCII to UTF-8. It’s more like X to Wayland. The protocol authors went “This is a mess we gotta rethink this from scratch”. But there’s so much already relying on the old protocol, and replacing it with something that doesn’t perfectly match features is difficult for little reward for users.

    The increase in IPv6 nodes has mostly been due to mobile networks. The tragedy is they actually still mostly use layer 2 and bridge networking. IPv4 nor v6 can handle maintaining connections while addresses change. So they set it up so that you keep the same IP address as you travel and move between different towers. This is done with massive virtual layer 2 LANs across towers, with the IP routing happening at a central datacentre. IPv6 is simply used for the larger addresses, and none of the network/protocol simplifications it promised can be used.