I simply don’t get why domain squatting is legal. On my ccTLD it is absolutely illegal meaning you have to forfeit the domain if you don’t use it anymore.
I simply don’t get why domain squatting is legal. On my ccTLD it is absolutely illegal meaning you have to forfeit the domain if you don’t use it anymore.
Nextcloud won’t be able to recognise new files if you do it that way. A full scan will be needed before they’ll show up in the web app.
Only lunatics buy drives over 10 TB.
Hey! No need to call us out like that.
I got one shipped to Denmark after brexit and IIRC they handled all the customs and everything.
Ninja edit: It looks like you’ll pay taxes and customs fees on top of it if you order directly, so it might be a good idea to hunt for a reseller: https://discourse.osmc.tv/t/european-orders/96161/2 - apparently I was lucky and happened to order when they were trialling IOSS
The closest I can think of is a Vero from osmc.tv but that’s breaking the 100 mark.
I’ve got the old Vero 4K model and it works like a dream in conjunction with my Jellyfin server (it’s essentially a Kodi box so you can save media on it locally too).
dba.dk is a pretty popular site for buying used stuff in Denmark, but for electronics I usually go on eBay and sort by EU only (IIRC they removed that option so now the results are tainted with lots of UK gear that’ll be hit with import taxes).
Setup a reverse proxy and configure it to redirect yourdomain.org/nextcloud (or nextcloud.yourdomain.org) to a custom port that you’re now running Nextcloud on. Then configure some-random-service which you want at yourdomain.org/some-random-service to redirect to port 1234 and so on.
This means all incoming connections on port 80 and 443 now will be handled by your reverse proxy and depending on the requested URL, the reverse proxy will fetch the desired website contents from the origin web server. I personally use nginx but there exists other good reverse proxies you can use.
I tell my friends that my SLA for my media server is Shit’s Likely Available just so they understand that I give it out of generosity and don’t want anything in return. The bonus is that keeping brutally honest upfront likely means less risk of me ruining someone’s Friday movie night.
You know, I would have looked it up and checked if there were holes on my knowledge but you being a dick about it makes me not want to.
Next time, don’t assume the worst in people and you might actually succeed in convincing them.
No, that’s a placeholder a set. It’s a class C range which is limited to 254 hosts.
No it’s not. 192.168.x.x is a reserved class C range which per specification is limited to 255.255.255.0
The 192.168.x.x IP range doesn’t allow for subnet masks greater than 255.255.255.0. How that’s enforced I can’t remember, but I’m 99% sure he isn’t using larger subnets.
There is though reasons to stray from certain consumer products for server equipment.
Enterprise distributuions can hot-swap kernels, making it unnecessary to reboot in order to make system updates.
If anyone asks you’re just hosting home videos ;) No one can bust you for that.
Any reason those $5/yr in difference are worth the risk?
For personal use I’d say go with whatever and make sure your Jellyfin server has been locked down. Maybe block anything but your own country IPs as that will lower any risk of scanning. But this is pretty much not necessary for a personal instance.
If you want to share your Jellyfin it depends on how many and how much you trust those you share with. The bigger the risk, the more likely I’d be to order through Njalla and routing through a VPN or the like.
I myself just use my lastname.tld as it’s for personal use along with sharing with a few trusted friends. I do though use a ccTLD that is assigned to my country as I feel like I have a better chance at keeping my stuff secure and private.
If you want to host “Linux ISOs” I’ve heard from a friend that Njalla is the best option. You don’t own the domain meaning your personaldetails aren’t published and Njalla has a good track record when it comes to protecting their customers.
If I’m not mistaken this is only applicable for USA.
Neither do .dk domains, but in order to determine use the courts will have to be involved. I haven’t heard about a lot of those cases, but I’d guess you can prove use against the person who wants to take the domain. If I have a domain called firstnamelastname.dk it’d be pretty easy to show that I got a mail address at contact@firstnamelastname.dk that’s in use.