• 0 Posts
  • 17 Comments
Joined 2 years ago
cake
Cake day: July 30th, 2023

help-circle

  • Yeah fair. I tried setting it up, but honestly probably not worth the effort in home networks. Problem is browsers don’t know that the other end of the unbound DNS server is DoH, so it won’t use ECH. Even once set up, most browsers need to be manually configured to use the local DoH server. Once there’s better OS support and auto config via DDR and/or DNR it’ll be more worth bothering with.





  • I’ve been using pcloud. They do one time upfront payments for ‘lifetime’ cloud storage. Catch a sale and it’s ~$160/TB. For something long term like backups it seems unbeatable. To the point I sort of don’t expect them to actually last forever, but if they last 2-3 years it’s a decent deal still.

    Use rclone to upload my files, honestly not ideal though since it’s meant for file synchronisation not backups. Also they are dog slow. Downloading my 4TBs takes ~10 days.




  • I don’t get the term ‘technical debt’. Most people seem to use it to say “We took shortcuts previously, so now we need to go back and do things properly”.

    FIrst, it’s a bad metaphor. You take on debt to invest in long term things that will provide future benefits. Telling the bean counters that you need to stop working on useful features to ‘pay back technical debt’ is not making things clearer to them.

    Second, you write software, what the heck are you talking about? Compare to civil engineering. If an area gets busier and the existing narrow wood bridge is no longer suitible, engineers don’t say “Wow what idiots built this road with no eye to future growth?” It was built with the needs and resources of the time. To improve it, the bridge needs to be closed, demolished, and rebuilt with planning, labour and materials.

    Instead software is empherial. You don’t need to demolish what’s there. No need to build temporary alternative infrastructure. No need for new materials and disposal of the old. It’s just planning and labour to redo a piece of software. It always seems so whiny when people complain about technical debt, as if switching to a different build system is anywhere close to the difficulty of fixing real life; replacing lead pipes with copper for an entire city, or removing asbestos from buildings.



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