lemmyvore @ lemmyvore @feddit.nl

Posts

15

Comments

2,750

Joined

2 yr. ago

If only there was a fully-featured alternative OS we could use on ARM!

If he really had balls he'd restrict access to the site and improve the built-in search engine.

If reddit's own search worked well nobody would care. Engines like DDG even have bang codes that send you to a site's own engine. So instead of having to add "site:reddit.com" to the search on DDG I'd just add "r!" and it would end up being the same thing. IF the internal search didn't suck.

They're not claiming copyright. They have a perpetual, non-revokable license to the content, granted by the people who use their site when they post the content.

It lets you change reverse proxy or run a website with TLS completely independently of the certbot. The certbot deals with obtaining certs and leaves them in a dir, and the proxies or webservers just take them from that dir. If the proxy container breaks the certbot still does its thing etc.

It also makes it easier to do stuff like run different proxies in paralel for different things, chain proxies (for instance if you need to use a VPS because you can't forward ports) and so on.

But it's all for advanced setups, for basic stuff I'd still go with NPM.

You don't run your own DNS, they are services hosted by someone else, just like Afraid. The difference, on top of the interface, is that they support modern record types, they have redundant servers all over the world, there's a team working on them instead of just one guy, they have APIs that can let you manage your many domains easier, they have zone backup and restore etc.

I've used Afraid too, back when I was starting out and didn't know any better, but once I've seen some of the other services out there I've never looked back. You'll never know what extra features you could want if your current service doesn't offer you any.

You can protect important data with backups, which you should do anyway, and in practice I feel like the added complexity of BTRFS and ZFS is not worth the COW.

BTRFS is cool but they tried to cram way too much too fast into it and it added a ton of complexity and it's still not 100% done after all these years. A COW mode for ext4 would have been adopted much faster.

They're all "standards", yet no two TVs will work the same (if at all) — even when they're the same make as the phone.

IMHO 99% of the time btrfs features are used as a band-aid for things that would be much better done otherwise. Generally by using a stable distro and a decent backup solution (like Debian + Borg). And you get to use a truly stable, proven, boring fs ike ext4 or xfs.

I'm currently in the process of separating the certificate renewal service from the reverse proxy completely.

But if you're just starting out Nginx Proxy Manager makes it so easy.

Your only option for what, exactly?

I've been using the Xtra app on Android exclusively ever since this string of updates started. The new Twitch app is completely unusable.

FWIW when you can't connect to a website Firefox shows you the "hm we're having trouble finding that site" error.

I was assuming that you don't own a domain. If you do why would you use Afraid? There are lots of reliable DNS services to choose from and you can have interface and features that aren't frozen in 1995.

Afraid.org gives you subdomains on other people's domains, who can decide to stop letting you use them at any moment.

Get your own domain, find a free DNS service that provides an API, and it becomes a simple matter of updating a DNS A record whenever your IP changes.

Here's a starting point: https://community.letsencrypt.org/t/dns-providers-who-easily-integrate-with-lets-encrypt-dns-validation/86438

Don't use a DynamicDNS service, they're usually crap and they make you depend on a domain you don't own.

The BubbleUPnP app can cast to Chromecast (and DLNA) and has built-in support for Jellyfin as a media source (you can browse your Jellyfin content from the Bubble app). It's basically the "remote" you want.

Bubble can also act as a media player so if you launch a video file from a file manager and tell it to play on Bubble while it's connected to a Chromecast, it will cast it.

Bubble can also directly access local files on the phone, Samba shares, and various types of cloud storage accounts.

Its only shortcoming is no SSH support but there's a workaround for that: the Solid Explorer file manager has a built-in relay that will pipe a video file over SSH to a local video player... pick Bubble as that player and you can play to Chromecast from SSH.

Miracast is not the same thing as WiDi and anyway it's just another bunch of competing proprietary protocols except for screen casting instead of streaming.

We'd love to but there are almost zero Android apps that suport DLNA. You can use DLNA for your Jellyfin but if you want to cast from the app of any large streaming service it wants Chromecast (or Apple TV, which is another quagmire).

You're getting a bad TLS certificate. If you press the Advanced button you should be able to see a reason why the certificate is not accepted by the browser.

It can be any reason, for example I got this error when one of my certificates expired (because I messed around with the DNS API token's permissions and didn't test it afterwards).

In your case it's probably not an expired certificate because then you'd see that error everywhere not just on the hospital WiFi.

I suspect that whoever controls that WiFi is trying to hijack your connection, but it won't work because once a browser has seen a HSTS flag it will refuse to connect to that site in any way except TLS (with the correct certificate ofc).

Kudos for enabling HSTS btw, excellent move.

I'll be very curious to see what the browser says the reason is.

And yes the HSTS error is completely unhelpful in this scenario. The fact HSTS blocks the connection is secondary, the much more important detail is why TLS could not be established.

It's like if your house key didn't work and you were told "you know, doors require a key to be unlocked". You'd be like "dude, I know, I have the key right here, why isn't it working?"

A redirect would work. This is not a redirect, it's TLS hijacking. Someone's injecting a bad certificate into OP's connections.