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

help-circle

  • Like Hawke said it seems like the graphics card or driver crashing. Very hard to troubleshoot, especially when it’s random. Bazzite probably already has very recent drivers, there’s this post on the bad website listing some things to try. This stuff can lead to superstitious thinking, with people changing something, rebooting to have it work fine for a while then they post that change as if it fixed it.

    God speed.



  • This is why I find this stuff so bewildering, even Wikipedia says no one died in the square. It was hectic around Mudixi, with buses of soldiers being torched and the burnted bodies being strung up. People there were absolutely shot at and killed.

    It was an insane week with a lot happening, many different groups with their own motives, and so many details unclear. It’s weird that anti China rhetoric insists on something that didn’t happen, pushing a false narrative that’s so easy to dispell and distracts from the real violence and politics of the time.


  • Your motherboard wouldn’t happen to be an AsRock? There’s been reports of ASRock mobos in particular causing problems with 9000 series AMD chips, especially the X3D. Mate of mine running windows has been having it crash especially when idle at desktop.

    I’m not familiar with a green Linux equivalent to the BSOD. Is it completely green? In that case it may be a graphics problem…


  • My understanding is that it’s technically against their TOS but loosely enforced. They don’t specify precise limits since they probably change over time and region. Once you get noticed, they’ll block your traffic until you pay. Hence you can find people online that have been using it for years no problem, while other folks have been less lucky.

    Basically their business strategy is to offer too-good-to-be-true free services that people start using and relying on, then charging once the bandwidth gets bigger.

    It used to be worse, and all of cloudflare’s services were technically limited to HTML files, but selectively enforced. They’ve since changed and clarified their policy a bit. As far as I’ve ever heard, they don’t give a toss about the legality of your content, unless you’re a neo Nazi.


  • I’m guessing the cloudflared daemon isn’t connecting to jellyfin. You want to use http://. Also is jellyfin the hostname of the VM? Using localhost or 127.0.0.1 might be better ways to specify the same VM without relying on DNS for anything.

    Personal opinion, but I wouldn’t bother with fail2ban, it’s a bit of effort to get it to work with cloudflare tunnel and easy to lock yourself out. Cloudflare’s own zero trust feature would be more secure and only need fiddling around cloudflare’s dashboard.


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


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