tenna

A critter on the internet

Avatar by Sol


A techie critter and casual streamer in their mid-twenties with interests in webhosting. Known for running web servers on things that shouldn't run web servers, turning others into similar looking blue raccoons, and being a little bit bigger than average.


Disclaimer: All content posted here are my own, and don’t necessarily represent my employer’s positions, strategies, or options.


I post non-lewd kink, but make best efforts to tag it 18+. This might not always happen, however (especially if it's only adjacent to it.) Please only follow if you are 18+.

Additionally, please put something in your profile before following me. I probably won’t block over it or anything, but I get a little anxious when I’m followed by an empty account.



outer fediverse, public
@tenna@blimps.xyz
atproto (bluesky)
@tenna.zip
website league
@tenna@pleasetf.me

jkap
@jkap

there were concerns that we were meaningfully contributing to cloudflare's revenue, which is reasonable! it's not ideal to have your cohost plus subscription money indirectly going to a company whose values you very specifically do not like.

i alluded to this in the vaguest possible tones, for reasons that will soon become obvious, but we were not meaningfully contributing to their revenue. if anything, we were costing them money!

three-ish years ago, i complained on twitter about how cloudflare locked wildcard subdomain support behind their enterprise plan and we were looking for alternatives. a VP at cloudflare running their Startup Outreach program DM'd me offering to set us up with a free enterprise contract. this was supposed to last a year.

they completely forgot they did this and never followed up. we have paid cloudflare a grand total of $50 since then. i never said anything because it was a ticking time bomb; if they noticed and came calling, we'd be kind of boned. but they didn't, and now we're off them completely, so it doesn't fuckin matter! rest easy knowing your posting cost cloudflare money.

but also it doesn't fuckin matter anymore b/c we're off them. the migration means we actually have a CDN bill now, which is kind of a bummer, but it's fine because i'm genuinely happier with fastly.

thanks for using cohost!


You must log in to comment.

in reply to @jkap's post:

this is hilarious

did y’all move the DNS zones to a new provider as well? the registry still shows dom/grace.ns.cloudflare.com but i know that can take a while to get updated by registrars

A comment has been hidden by the page which made this post.

given the IPs currently on the apex domain cohost.org match n.sni... and dualstack.n.sni..., you should be safe to set the apex IPv6 addresses to the ones on dualstack.n.sni

in fact you can test it and it works: $ curl --resolve 'cohost.org:443:[2a04:4e42::347]' https://cohost.org/rc/welcome --head