Everyone has a hobby 🙃

And it makes no mention that they were modifying and using GPL code prior to making their code “open source”.

Id argue that this story is not over until the GPL code can be confirmed removed by a third party

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.

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

The difference is that commercialization is inherent with a free (libre) open source license. Whereas going against the intent, but still legally gray area, is imo malicious compliance because it circumvents what the license was intended to solve in the first place.

But that’s all i really care to add to this convo, since my initial comment my intent was just to say that the AGPLv3 license does not stop corporations from getting free stuff and being able to charge for it-- especially documentation. Have a good one

No. I said even if they don’t maliciously comply with the license [by making the open sourced code unusable without the backend code or some other means outside of scope of this conversation] then they can charge for it.

The malicous part is in brackets in the above paragraph. The license is an OSI approved license that allows commercialization, it would be stupid for me to call that malicious.

Nothing. The context of this comment thread is “fuck corporations” and then proposing AGPL to solve that. I am merely pointing out that if their goal is to have a non-commercial license then AGPL doesn’t solve that, which is why i mention they can charge for their services with AGPL.

AGPL is the most restrictive OSI approved license (of the commonly used ones), but it is still a free (libre) open source license. My understanding is just that the AGPL believes in the end-users rights to access to the open source needs to be maintained and therefore places some burden to make the source available if it it’s being run on a server.

In general, companies run away from anything AGPL, however, some companies will get creative with it and make their source available but in a way that is useless without the backend. And even if they don’t maliciously comply with the license, they can still charge for their services.

As far as documentation goes, you could license documentation under AGPL, and people could still charge for it. It would just need to be kept available for end-users which i don’t think is really a barrier to use for documentation.

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.

Kebab or snake for ease of parsing through them.

Either i wasn’t clear or you are replying to the wrong person, but i am in support of foss projects asking for donations in a reasonable manor such as this

There is an option to disable it permanently. Otherwise it is once a year and easily dismissed

It’s once per year, easily dismissed, and can be permanently disabled. Seems entirely reasonable for a piece of free software that someone would use everyday

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.