Dima

No idea, didn't do anything wrong and they were fine with it all until they suddenly closed my account. I too would like to know what I did wrong.

They disabled my account without any notice, I tried to login to see why my VM wasn't responding and found they'd deactivated Oracle cloud services. It's also difficult to get in touch with support as there's multiple different portals and with the cloud services disabled I struggled to find a way to raise a relevant ticket. When they eventually responded they gave some generic BS about their ToS.

My suggestion for anyone using Oracle free tier is stay on it if you want, but be prepared for the eventuality that they shut everything down without notice or access to your data.

Make sure you have backups, they randomly shut mine down after a couple of years

I would go for a distro that has relatively recent/up to date packages, especially for Linux kernel and power-profiles-daemon, as these will work better with the CPU than packages from 6-12 months ago

Yeah, it's not FOSS, but sleep as android is great. You can set various "captchas" that need to be completed to turn the alarm off, you can connect it to smart home stuff to turn on/off lights or open curtains and the general customisability for the alarm settings is extensive.

Why even bother having swap at that point?

@[email protected] posted this previously:

In 61 a migration is borked, this caused some appsettings to be switched around. So previsously if you had custom tabs enabled, this would enable the prevent screenshots setting.
Now I fixed this, so this means those who changed them will see them swap again. And those who haven't upgrade yet won't notice anything. There should be release tomorrow which address all the bugs introduced in this update. Sorry for the inconvenience!

Link to comment

Snuggling or smuggling?

Until they randomly ban you and shut down your free services

I thought running rm -rf /dev/* was a good idea, I was sure worst case scenario […]

Worst case scenario:

They have installation instructions on the Github

You should be able to update the config file for SearXNG to add the port to the URL. Then just restart SearXNG; removing and re-adding the search engine to Firefox should make sure it's updated to use the correct port. In the settings.yml file, under the server: section is the setting you want to change:
base_url: http://192.168.1.65:8887/
Leave port: unchanged