It’s neat that this exists, but not neat if someone hosts it for a year, a bunch of fed users rely on it and share a bunch of links using it, and then the hoster takes it down for whatever reason, and now there are a bunch of dead links littered all over the place.
Even less neat if some malicious group can then buy the lapsed domain and forward all those dead links to ads and viruses.
Please host responsibly, is all I’m saying.
It’s not sunk cost, dude. We agreed that $120 will get them 5 years of service that meets their needs. Even if they switch to jellyfin after 5 years, they still got their money’s worth.
It’s only sunk cost if they are worse off than if they had switched earlier. I guess if you’re arguing that they would still have $120 if they switch today, I would argue they should still pay that $120 toward jellyfin’s development. And that’s assuming they have time to switch to jellyfin AND it fits 100% of their usecases, either of which could be untrue.
Or Plex currently does everything they need it to, and $120 for 5+ years of keeping that going without any interruption of service is very reasonable. In the meantime, jellyfin will only get better and there might even be other options available by then.
Stop trying to make the issue black and white, one-size-fits-all. There are perfectly legitimate reasons for people to use both Plex and Jellyfin.
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.
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.
It’s normal for it to heat up under load, but it’s not normal for it to be under load 24/7 indefinitely.
Why is that? Does the motherboard effectively just not have enough inputs for all the disks, so that’s why you need dedicated hardware that handles some kind of raid configuration, and in the end the motherboard just sees it all as one drive? I never really understood what SCSI was for. How do the drives connect, SATA/PATA/something else?
Modern Android Do Not Disturb is configurable enough for you to do this. Allow your family contacts through, block the rest.
You’re saying you see a bunch of login attempts on your router, but you don’t think they actually got into it?
I would assume that wouldn’t cause so much contention that the system is unusable, though, right? Unless they’re busy waiting.
Sounds like OP is asking about file storage. Video streaming could be spotted using info leaked regarding traffic behavior. But uploading an encrypted file for storage shouldn’t leak anything except the size.
Wait what? I’m saying what you said is correct. Am I the one who’s confused here?
Edit: oh maybe you meant that’s the excuse people give for being wrong? lol
More specifically, the container is run on bare metal if the host is running on bare metal. You are correct in this thread, not sure why you’re being downvoted. I guess people don’t know what virtualization technology is or when it is used.
If the nextcloud container is slow, it’s for reasons other than virtualization.
A CSV file should work.