starshipwinepineapple

Wait, if they suspended your domain, can you even transfer it away? if not, that's really fucking scary.

Njalla takes ownership of every domain purchased on their platform. They do let you transfer domains to another registrar where you could be the owner if your account is in good standing but seems like that may not be the case here (since account suspended)

That may be great for some domain use cases but for most stuff it would be better to have your name on the domain registration

Gitea, took control away from community and gave it to a for profit organization. Forgejo was born

Python 3.13 is adding support for removing GIL, via PEP 703

I really like that it is a static website being updated and built on a schedule from github actions.

Open source is generally understood as libre, and an OSI approved license.

I think you're thinking of source-available.

Additional reading: https://news.itsfoss.com/open-source-source-available/

Anyway, thanks for the list!

In fairness websites from 2000-2004 werent all that better

Were there better ways to make a site? Absolutely, but it is much less wild than if you told me that this happened last week. Plus i would hope they were just churning out websites for cheap since a lot places didn't have a website, or they used geocities/similar

Who hurt you!?

It would be much more customer and developer friendly to allow linking a service portal instead of providing a phone number. I would go insane if a user called me directly every time one of my projects had a bug or some perceived (non)issue. No, that's not how this works.

And if you want a private repo, you can also use gitlab and point to custom domain with gitlab pages or cloudflare pages.

Yes, oracle will reclaim your server if it falls under certain thresholds for the resources you've signed up for. So it might be better to request less resources then you need but this will somewhat complicate things if you want more resources in the future since iirc you can't simply resize.

One way to get around all of this though is convert to pay as you go (PAYG). PAYG gets the same always free allocations and you only pay for use above that, and oracle won't reclaim PAYG (at least not my server for ~4 years). Just set up a budget of a $1 and then alerts to email you if you reach 1% of your budget. If you somehow go over your free resources it'll tell you.

Lastly in some cases oracle just straight up loses your data or disables your account. As always practice 3-2-1 backups (don't rely on the free rotating backups on their servers as your only backup).

It's some hoops to jump through but i was paying $5/ month for a digital ocean droplet and the oracle server has been running for 4 years now, and i also have scaled up one project and started a few others that wouldn't have all fit on my droplet. Other than the threat of reclaiming my resources before i switched to PAYG I've been pretty happy with it.

Thanks! I'll add that to my list to check out

If you only ever keep your repository private AND it is not a fork of a public repo, then you are fine. Full stop.

If you ever fork the repo and make a "INTERNAL" private fork but move the main project public then anything you commit to the private fork will be discoverable through the public project.

Basically you should assume if you make a repo public then the repo and all of its forks will be public-- even if the forks are "private" the commit data can be found through the main repo.