calamityjanitor

My understanding is that it's technically against their TOS but loosely enforced. They don't specify precise limits since they probably change over time and region. Once you get noticed, they'll block your traffic until you pay. Hence you can find people online that have been using it for years no problem, while other folks have been less lucky.

Basically their business strategy is to offer too-good-to-be-true free services that people start using and relying on, then charging once the bandwidth gets bigger.

It used to be worse, and all of cloudflare's services were technically limited to HTML files, but selectively enforced. They've since changed and clarified their policy a bit. As far as I've ever heard, they don't give a toss about the legality of your content, unless you're a neo Nazi.

I'm guessing the cloudflared daemon isn't connecting to jellyfin. You want to use http://. Also is jellyfin the hostname of the VM? Using localhost or 127.0.0.1 might be better ways to specify the same VM without relying on DNS for anything.

Personal opinion, but I wouldn't bother with fail2ban, it's a bit of effort to get it to work with cloudflare tunnel and easy to lock yourself out. Cloudflare's own zero trust feature would be more secure and only need fiddling around cloudflare's dashboard.

There's stuff like ripple control to tell appliances to lower consumption. Pretty archaic and rare these days. There's nothing I know of that communicates to the utility.

I have no idea what John is talking about or why he brought this concept up.

It runs basically the same PebbleOS, so they'll work with any app that works with the original Pebbles. They plan to keep using the community app hosting at https://apps.rebble.io/. There's also GadgetBridge that's compatible. Eric mentioned on HN the intention for an official open source library that can be used to make other companion apps too.

Yeah the mobile app is open source too https://github.com/pebble-dev/mobile-app

I was so bewildered reading the novel. I had heard he wrote it as a pro military propaganda piece, but I couldn't help but see it as satire.

They are kitted out in mech suits, making them seem more machine than man, put into drop pods that are fired onto the planet like bullets out a gun. In the pod they are isolated from their comrades, isolated from their humanity, literally turned into pieces of a weapon.

Then they land on the alien planet to perform a terrorist attack on a civilian city. And this book is meant to be pro war?

NumdaQA already pointed out you're utterly wrong, but some additional context might help:

• The opposition says the government should have grovelled more to avoid the tariff, they wouldn't ever retaliate with their own.
• The Australian Steel industry does not give a shit.

So while I get it makes sense in Canada, and we are similar countries in a lot of ways, but on this issue we're just at different political places.

I had a 5 II too, used lineageOS for years, worked great. Doesn't totally solve the battery or fingerprint reader. My screen got the dreaded green lightsaber too. Nail in the coffin was Australia turning off 3G so it can't make calls anymore. (Wasn't officially sold here so they didn't bother loading it with VoLTE profiles)

Some googling suggests this is what Dropbox does when it doesn't like the owner or permissions of any files in the Dropbox folder. It is very weird though. I assume you have dropbox installed? It is syncing correctly? Running find /home/dullbananas/Dropbox/ ! -user 'dullbananas' will list any files in that folder that aren't owned by you.

Assuming your userid is 1000 (likely but not guaranteed), running the script should be harmless and stop the password prompt from appearing until there is another file permission issue. Check your user id with id -u 'dullbananas'.

I don't have a Fedora box to check for sure, but have a look in /var/log/secure, it might have details of the request and what program called it.

Surely the space is part of the command. It's running sh with the file in /tmp as the parameter (run this file).

Seems weird to have a separate app read sent and received messages? Is it poking holes in the Messages app sandbox?