To the extent that I evangelize for any company, I generally give positive reviews of Opalstack (internet hosting). They're no-nonsense, you get what you pay for plus a little more, and you don't pay too much. Their TOS has a few worrying phrases in it, however. Sort of like zip bombs in a conceptual/legal sense.

I'm in violation of Opalstack's TOS if I advertise (I assume just mentioning it positively counts) or link to any "software, program, product, or service" designed to violate Opalstack's policies or the acceptable use policy of any other ISP?*** ***Fucking WHAT?

So before I mention any service, software, etc. that I think is useful, say on a blog or something, I have to research the policies of literally every other ISP in the world? My failure to do this means I can be canned by OpalStack?

How common is language like this? Their TOS binds me to the policies of every other similar company on earth?

Only slightly less worrying: I'm apparently responsible for the behavior of any of my "customers" (I don't have any, but I wonder if a commenter on a blog post would count, or a participant in a self-hosted survey).

Once again: I like OpalStack. I've been with them over a decade. They're a great host. I don't like policies that subject me to an unknown and unknowable set of rules.

#legal #isp #opalstack #tos #wtf

Easy to deal with mailing list server side software? One that comes with #OpalStack ?

This was on my to do list for today, but I failed.

Hey, my favorite* host has an instance! opalstack.social apparently exists. I'm here on c.im, but if I wasn't, I'd give Opalstack's instance a shot.

* as in, that's where my stuff is. For a decade it was on webfaction, and when that got a case of #enshittification I, like many others, followed the devs to opalstack. I don't have a broad knowledge of these things; opalstack works, isn't evil like godaddy, and has responsive, helpful tech folks when you have a probem.

#webhost #opalstack #instance #mastodon

I'm getting very tired of losing dozens of hours of my life getting #nextcloud to work about 3 times a year. More or less with every major upgrade.

This time I'm getting failed checks to sync my desktop app ("CSRF check failed"), along with sudden errors in the online web page that were resolved in past versions.

Wrinkle (always): shared hosting (#opalstack FTW) b/c I want my data stored offsite.

Returning errors:

1. Trusted_proxy incorrect. These were fine until the upgrade. Now I can't get anything to work (so far). It's not a warning, it's an error, in angry red.

2. memory limit not at least 512 MB. Except it is. It's set in the app's .user.ini file, which has no effect (this time, since upgrade).

3. set strict-transport-security... yes, that is set in .htaccess. No effect this time (worked fine before this upgrade)

About 4 more warnings that have lower priority. Basically, #sync stopped working, and that's a 100% bottleneck. Without sync of files, there's no point in having Nextcloud.

Ugh. I do not want to pay for Dropbox or whatever, but I might end up doing that; I seriously lose at least 30 hours a year on this, and there are many, many other things I'd rather do with that time.

I'll try to learn more, but if I have to basically take sysadmin classes to make Nextcloud work... no. I'll just pay for a commercial service.

*EDIT*: Thanks for the words, @pa

Note:
"Made Easy" - fuck, no

"On premises or cloud" - good luck on shared hosting, sucker

"Regain control over your data" - If "control" means "it stays on my laptop and never syncs to my Nextcloud instance," then I guess this is accurate.

#techhell #upgrade #fml

Dynamic DNS on #Opalstack with Python

https://community.opalstack.com/d/1319-dynamic-dns-script