Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)T

teawrecks

@ teawrecks @sopuli.xyz

Posts
1
Comments
167
Joined
3 yr. ago

  • Server upgrade/replacement help

    Jump

  • My recommendation would be, have two machines: new hw for all your services, and use the old hw for your NAS. Each could be whatever OS you're comfortable with using. Most everything on the services machine could be in docker configs, including network mount points to the NAS. You might be able to get away with using the 1080TI in the services box depending on what all you want to do (AI stuff, or newer stream transcoding requirements may require newer hw).

    Moving the data from the old NAS to a new one without new disks will be a challenge, yes.

    I have a TrueNAS box and used jails for services. I recently set up a debian box separately, and am switching from jails on truenas to docker on debian. Wish I had done this from the start.

  • Linus responds to Hellwig - "the pull request you objected to DID NOT TOUCH THE DMA LAYER AT ALL... if you as a maintainer feel that you control who or what can use your code, YOU ARE WRONG."

    Jump

  • To be fair, it's entirely possible someone else made a post about this topic with an non-sensationalized title, but no one engaged with that one. Including us.

  • Linus responds to Hellwig - "the pull request you objected to DID NOT TOUCH THE DMA LAYER AT ALL... if you as a maintainer feel that you control who or what can use your code, YOU ARE WRONG."

    Jump

  • Come on and slam

  • Linux 6.14 With Rust: "We Are Almost At The 'Write A Real Driver In Rust' Stage Now"

    Jump

  • A Linux user time traveling from the 90s/00s would be elated to know that one day someone could possibly have this opinion.

  • Anyone else here self-hosting on absolutely shit hardware?

    Jump

  • All of that was introduced in 2004. When you said "25 years ago" I assumed you meant the original P4 from 2000.

  • Anyone else here self-hosting on absolutely shit hardware?

    Jump

  • Negative, Pentium 4 was x86 and thus could only address 32 bits.

    64bit CPUs started hitting the mainstream in 2003, but 64bit Windows didn't take off until Win7 in 2009. (XP had it, but no one bothered switching from 32b XP to 64b XP just to use more memory and have early adoption issues. Vista had it, but no one had Vista).

  • Save your computer from Microsoft's Windows 10 end-of-life planned obsolescence

    Jump

  • I'm sure that it's just the marketing dept changing hands over time. Marketing teams are like a Scott's Tots situation: they are just trying to say whatever makes the product numbers look good in the near term. Fulfilling on any promises is a future marketing team's job.

    "Of all the empty promises I have made, this one is by far the most generous"

    Michael Scott/Microsoft's marketing team

  • Security blindspots for selfhosted website

    Jump

  • Let's Encrypt is good practice, but IMO if you're just serving the same static webpage to all users, it doesn't really matter.

    Given that it's a tiny raspi, I'd recommend reducing the overhead that WordPress brings and just statically serve a directory with your site. Whether that means using wp static site options, or moving away from wp entirely is up to you.

    The worst case scenario would be someone finding a vulnerability in the services that are publicly exposed (Apache), getting persistence on the device, and using that to pivot to other devices on your network. If possible, you may consider putting it in a routing DMZ. Make sure that the pi can only see the internet and whatever device you plan to maintain it with. That way even if someone somehow owns it completely, they won't be able to find any other devices to hack.

  • KDE Will Nicely Notify You When Apps Are Being Killed Due To Out-Of-Memory

    Jump

  • Or your OS* is doing something wrong 😆

  • KDE Will Nicely Notify You When Apps Are Being Killed Due To Out-Of-Memory

    Jump

  • But if you're filling up all RAM and swap, either you needed to upgrade a while ago, or you're doing something wrong.

  • Using refurbished HDDs in my livingroom NAS

    Jump

  • Btw it looks like you accidentally quoted the same sentence twice.

  • Linus Torvalds Growing Frustrated By Buggy Hardware & Theoretical CPU Attacks

    Jump

  • In the last 10 years there has been a seemingly noteworthy uptick in hardware bugs in both intel and amd CPUs. Security researchers find and figure out potential attack vectors that rely on these bugs (ex. Specter/Meltdown). Then operating systems have to put workarounds in their kernel code to ensure that these hypothetical attack vectors are accounted for, at the cost of performance and more complicated code.

    Linus is saying how annoyed he is with all this extra work they have to do, resulting in worse performance, all to plug vulnerabilities that we've never actually seen any real attackers use. He's saying instead we should just write the code how it should be, and if the hardware is insecure, let it be the hardware company's problem when customers don't use the hardware.

    The problem is, customers will continue to use the hardware and companies who need a secure OS (all of them) will opt to not use Linux if it doesn't plug these holes.

  • Why self host a password manager?

    Jump

  • Agreed with using keepass. If you're one person accessing your passwords, there's no reason you need a service running all the time to access your password db. It's just an encrypted file that needs to be synced across devices.

    However, if you make frequent use of secure password sharing features of lastpass/bitwarden/etc, then that's another story. Trying to orchestrate that using separate files would be a headache. Use a service (even if self-hosted).

  • SpacebarChat - a selfhosted, Discord-compatible communication platform

    Jump

  • SpacebarChat - a selfhosted, Discord-compatible communication platform

    Jump

  • Yeah, I saw that element is using jitsi under the hood for its screensharing. If that makes for a seamless user experience, that's great. It's been like 10 years since I last tried Jitsi, but it was not smooth.

  • SpacebarChat - a selfhosted, Discord-compatible communication platform

    Jump

  • TBH both disc and slack have their downsides, disc more so, so I'm fine if they just take the best of all worlds.

    But yeah, screensharing is the deciding factor for me. As much as all my friends hate discord, we use screensharing all the time (it's just a bit jankier getting it working on Linux).

  • SpacebarChat - a selfhosted, Discord-compatible communication platform

    Jump

  • This one is clearly made to look like slack, which is great I need to try this out. Just wish someone would make one that looks like disc. And then matrix needs screensharing support.

  • SpacebarChat - a selfhosted, Discord-compatible communication platform

    Jump

  • Does it work now? I tried it around a year ago and couldn't get voice to work at all. It even had a message saying they were in the process of rewriting their voice streaming backend, and the legacy path may just be broken.

  • SpacebarChat - a selfhosted, Discord-compatible communication platform

    Jump

  • Discord compatible bots run on whatever server you run them on, they're not owned or run by Discord.

    It says the client is compatible with both space-bar and discord.com, so yeah, if you use it with discord, expect all the downsides of discord.