I had no issues when my domain was registered with GoDaddy. It was shortly after switching to porkbun that the issues started. Porkbun blamed nominet and nominet blamed porkbun. Not sure what actually happened, but it does seem related to nominet’s policy about who can hold a .uk domain
Nominet manages the .UK domain, and they’re a bit funny about proof of residence. Not sure I had to give Porkbun any photo ID, but the did temporarily suspend my domain. Took forever to clear up.
IMO the moral if the story is avoid ccTLDs (though now I have it I’m sticking with it for as long as I can).
I’d say don’t risk it if you’re not based in the UK.
I have a .uk domain and had to provide proof of residence or something to nominet. I can’t remember the exact process now, but they did temporarily suspend my domain (without warning) until I contacted them.
The change would be using Gitmail as the plumbing, and normalising the creation of user-friendly porcelain on top.
E.g. suppose there is a repo foo/bar hosted by a forgejo instance at myinstance.org/foo/bar. Sending an email to foo.bar@myinstance.org (or similar) could automatically create a PR and, conversely, opening a PR could send a patch series to the foo/bar mailing list.
To be honest, I’m starting to drink the Sourcehut coolaid here. We have a distributed method of interacting with repositories: Email.
Don’t get me wrong, the current user experience of email-based patches and discussion isn’t great because it’s too easy to send a badly formatted patch. But if we invested time in making email patches easier to use (e.g. sending them through a web ui for people who prefer github style PRs) then we could skip all the architectural pains of solutions like forgefed.
Be aware there are basically two different things called Owncloud. There’s still the original php version, which is similar to nextcloud but worse (not open source, smaller plugin ecosystem I think)
On the other hand is owncloud “infinite scale” (or ocis). This is the thing entirely written in go. But as others have pointed out, it’s little more than a file server at this point.
IMO the self-hosting community is really missing a self-contained “all the DAVs” server (files, calendar, contacts). Baikal etc seem like a great start, but it would be great to have somewhere to get those parts pre-assembled. Until then, nextcloud works for me.
I can’t imagine that’s any more free than bitwarden?
I dont get why they didn’t just call that update 11.0? Or use that for this update?
I guess if you’re changing the semantics of your version numbers its also a good idea to introduce a deliberate discontinuity to mark the change?