I am a Meat-Popsicle

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

help-circle



  • I ran gnome for about a decade. I really didn’t like how a lot of bits and pieces of it worked so I went and found all of the plugins and religiously installed and updated them. Updates what happened, crab would break, I’d just have to deal.

    At some point I tried KDE. And it literally did everything that I was doing to gnome through plugins out of the box.

    I’m all about configurability but I’m also a pretty big fan of not having to fuck with it because it already does what I want out of the box.


  • It’s a bit of math, split into two pieces.

    You hand out one piece, that’s the public key. It’s tiny and simple.

    You keep the other piece, that’s the private key. It’s long and complex.

    The public key can scramble data that only the large piece can unscramble.

    The private key can create a piece of data that only the public key can verify.

    In practice, these keys can be kept in a database or a file, and they can be held in a hardware security key (yubi/fido). They can be stored on your phone, in Bitwarden, and just about anywhere that keeps passwords, they’re really just a few thousand bytes of data.

    In many cases, You can store them in your phone’s private password storage, then when you log into a website, it will trigger a popup on your phone to authorize your login, so you don’t even have to keep them on the computer you’re using to access the secured site. Most of the implementations require you to have a biometric component. You need to face scan, fingerprint scan, or, worst case, use a password to unlock/verify the passkey on the device.

    The upside here is that the keys are unique to every site. The public key is completely safe to hand out to everyone, it can’t be reverse engineered. This means that websites can’t leak your login credentials in any meaningful way. edit: Also since you’re using math to change a piece of data, it’s impervious to a replay attack and the communication even unencrypted would be reasonably safe even if someone was actively reading it.

    As far as storing for loss, I’d consider regenerating them. I prefer using a password manager that stores them, that way my phone/computers all have access to the same keys.


  • Back when reddit* was just starting to fall to shit, I had already been dipping my toes in the mastodon water, and while I really liked the instance I was on it did not have enough people on it to properly surface good collections of off node traffic.

    Knowing that Mastodon had the problem, I didn’t dick around with smaller nodes. To be honest it’s still a fight if you’re on a node with only a handful of people, you have to do something to mitigate the lack of community traffic in the face of lacking discoverability.




  • So many f****** ads I gave my cell phone cancer.

    TMA:DR

    When taking the geometric mean of 73 benchmarks run for this comparison, upgrading from the Ryzen 9 7950X to 9950X on Ubuntu 24.04 LTS yielded a 14% generational improvement with this set of cross-platform applications/benchmarks while under Windows 11 was a 10% generational improvement. The raw performance of Ubuntu Linux on the AMD Ryzen processors also was greater overall to the extent of the Ryzen 9 7950X to Ubuntu 24.04 LTS nearly matching the Ryzen 9 9950X on Microsoft Windows 11.


  • You could make automatic breaking without a full blown computer, but it’s so much cheaper to put a full-blown computer than it is to do it all in hardware. Everything uses turing complete equipment now, it’s actually less expensive at this point.

    There’s absolutely no reason not to put multiple computers in the car I think the real win is not surfacing it to the end user.



  • I have a slightly different suggestion.

    Inflation is crap and the first thing to go are subscriptions that raise their prices when people are already hurting. If you want retention, keep your prices locked when users are having bad times and you’re raking in record profits.

    I think curation is great too, but I also think age plays a lot into individual views. A bunch of the younger guys at work were saying how they didn’t want playlists and they didn’t want to listen to an album, they just wanted to hit a button that knew their tastes musically and would give them a mix of familiar likes and new discoveries. The proceeded to describe a radio station to me, sans commercials. They were hot on all the music streaming and though I was crazy for wanting to spend time sorting through music.

    Looking at a Spotify by age graph, the boomers dig it (because it’s easy?), Gen-Z and the Younger Millennials dig it, Gen X has less than half the uptake of the other groups.

    We were mixing our own tapes in our tweens and teens. We wired ourselves to find music, copy it and play it in the specific order we want.

    or at least that’s my story and I’m sticking to it.


  • The first worry are vectors around the Synology, It’s firmware, and network stack. Those devices are very closely scrutinized. Historically there have been many different vulnerabilities found and patched. Something like the log4j vulnerabilities back in the day where something just has to hit the logging system too hit you might open a hole in any of the other standard software packages there. And because the platform is so well known, once one vulnerability is found they already know what else exists by default and have plans for ways to attack it.

    Vulnerabilities that COULD affect you in this case for few and far between but few and far between are how things happen.

    The next concern you’re going to have are going to be someone slipping you a mickey in a container image. By and large it’s a bunch of good people maintaining the container images. They’re including packages from other good people. But this also means that there is a hell of a lot of cooks in the kitchen, and distribution, and upstream.

    To be perfectly honest, with everything on auto update, cloud flares built-in protections for DDOS and attacks, and the nature of what you’re trying to host, you’re probably safe enough. There’s no three letter government agency or elite hacker group specifically after you. You’re far more likely to accidentally trip upon a zero day email image filter /pdf vulnerability and get bot netted as you are someone successfully attacking your Argo tunnel.

    That said, it’s always better to host in someone else’s backyard than your own. If I were really, really stuck on hosting in my house on my network, I probably stand up a dedicated box, maybe something as small as a pi 0. I’d make sure that I had a really decent router / firewall and slip that hosting device into an isolated network that’s not allowed to reach out to anything else on my network.

    Assume at all times that the box is toxic waste and that is an entry point into your network. Leave it isolated. No port forwards, you already have tunnels for that, don’t use it for DNS don’t use it for DHCP, Don’t allow You’re network users or devices to see ARP traffic from it.

    Firewall drops everything between your home network and that box except SSH in, or maybe VNC in depending on your level of comfort.





  • I’m not sure the list is really that big of a deal for a home gamer. They’re probably more in danger from their choice of home audio appliances and that microwave that has been sitting on their network for 10 years which no longer gets updates. Or that 2019 Plex server they have put forwarded straight outside.

    It’s actually one of my beefs with containers, You can’t keep track of The versions for everything and you’re at the mercy of the maintainers to keep individual packages updated.