Hah, they’re TrueNAS BSD jails, but yes, now I need to figure out how to rename the “Jails” tab in my UI to overlords.

Also, all the extra work my self-hosting endeavors generate is “creep”.

I use zerg units.

• NAS is named Nydus
• Homelab with a GPU is Hydralisk
• Jail instance that I can use for random cron jobs is Drone

Afaik the cookie policy on your site is not GDPR compliant, at least how it is currently worded. If all cookies are “technically necessary” for function of the site, then I think all you need to do is say that. (I think for a wiki it’s acceptable to require clients to allow caching of image data, so your server doesn’t have to pay for more bandwidth).

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.

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

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

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.

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

Ooo I just found out element added support for drop-in/drop-out voice and video rooms. That’s the real killer feature they’ve been lacking I think. Will have to try it out.

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.

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

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.

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.

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.

Thanks, good to know!

I think their question is, what do you mean by “secure”? Because as the saying goes for internet services: usually, if you’re not paying, you’re not the customer, you’re the product.

Agreed. Anyone who thinks it’s ok to just expose ssh on 22 to the internet has never looked at their logs. The port will be found in minutes, and be hammered by thousands of login attempts by multiple bots 24/7. Sure you can block repeat failed logins, but that list will just always be growing.

Normal for who? I wouldn’t expose SSH on 22 to the internet unless you have someone whose full time job is monitoring it for security and keeping it up to date. There are a whole lotta downsides and virtually no upsides given that more secure alternatives have almost zero overhead.

As someone who majored in CS and is now in a software engineering position, the people in tech who come from a completely different field are always my favorite. On top of just proving people wrong about the “right” way to get into the field, they’ve been around, they know how to think about problems from other perspectives, and they’re usually better at working with other people.

Honestly, I think more people should minor in CS, or if they did their undergrad in CS, they should have to do their grad work in something else. The ability to compute things is only useful if you’re well versed in a problem worth computing an answer to, most of which lie outside of CS.

I see several Amcrest options that look like they have integrated AI object detection. Frigate on the other hand says you should get a “Google Coral Accelerator”. Do you know if Frigate (or RTSP, I guess) has a way to leverage the built in detection capabilities of a camera (assuming they are built in, and not being offloaded to the cloud)? Or am I better of looking at the “dumb” Amcrest cameras, and just assuming all processing for all cameras will happen on my Frigate hardware?