Neshura

As the other commenter already said it’s an abundance of caution. GItea is already moving in the direction of SaaS and an easily self-hostable solution runs counter to that plan (Gitea is already offering a managed Cloud so this is not a hypothetical). One thing that has already happened is Gitea introducing a Contributor License Agreement, effectively allowing them to change the license of the code at any time.

I’ll be that guy: Use forgejo instead, its main contributor is a Non-Profit compared to Gitea’s For-Profit owners

I think you have the wrong idea about what I was referencing. I’m not talking about Cloudflare Tunnels but their Encrypted Client Hello. While Cloudflare could intercept the inital ClientHello the rest of the HTTP traffic still is encrypted between Client and Server not between Client and Cloudflare. In that sense they have not turned into more of a MitM than they (or any other DNS Nameserver) were already anyway. So unless governments decide to completely dismantle the trust chain the internet works on they won’t be forced to fuck with ECH for anti-piracy either.

But ultimately anything going over a public DNS Server is susceptible to being compromised. We simply trust that the providers don’t.

I’m sure this is definitely going to go how the regulator thinks it will go. What with Cloudflare being one of the driving factors behind e2e encrypting more and more of the HTTP stack, making it ever harder for ISPs and other 3rd parties to see inside the HTTP traffic.

The worst part really is just getting off the damn spam lists. There is almost no documentation anywhere for do’s and dont’s. I ultimately had to setup a sending relay for the mail on my status monitoring VPS because my residential IP triggered most spam filters, but I only found out that that was the problem from forum posts investigating the same problem. I check with stuff like mail-tester, get back perfect scores and yet most of my outgoing emails have a good chance to land in the spam folder anyway (but at least they get delivered so that’s a plus I guess)

As others in other threads have said: Google and Microsoft have killed the ability to self-host email simply by black-boxing their spam filters. As a user you have no real way to fix your mail server such that your emails get delivered into the inbox reliably.

I self-host email, it certainly isn’t something I’d recommend

Imo you probably save more money keeping the server up 24/7 than constantly shutting it down and starting it up again. Especially once you get a good list of services going.

Please tell me they had the decency to filter out the ML garbage… nvm that would’ve been too much work

The lemmy docs are all a mess. Try writing something that uses the lemmy api and you start crying because looking up the endpoints in the code tells you what it does faster than their ‘documentation’

Just my two cents but if you decide to go for the self hosted GitLab approach I think Forgejo might be a better fit. It’s not as resource intensive as GitLab is but has all of the essential features you’d need from a forge.

Tempo is a really good Navidrome Client for Android imo

Navidrome is a subsonic server, feom the cursory research I did before setting it up it is also among the best supported/developed ones available.

It’s what happens when the devs have to spend more time making sure the DRM works than actually improving the UX of the platform. Pirates/Non-DRM users don’t have that problem hence small FOSS projects can outclass big Streaming Services in UX quality.

If Gabe cares he likely already handed leadership over to allow for an interim period where he could step in and Veto any decisions he thinks are crap

For now it should work but it will have an increasing likelihood of breaking with every future Android Update.

Migrating to Mihon now is recommended, one of the devs worked on Tachiyomi and for now the code is almost identical which allows easy migration via a Tachiyomi Backup.

Migrating in the future might be more difficult because incompatibility between Tachiyomi and future versions of Mihon could mean Backups from Tachiyomi cannot be restored by Mihon.

Kakao nuked the official Tachiyomi Extension repo because they “infringe on their copyright”.

The Extension repo does not and never has offered copyrighted material, it merely facilitated access to sites that do within Tachiyomi. Essentially it was a collection of hyper specific Browsers. The repo is gone, the extensions are not (they are now in a different repo provided by a user). Tachiyomi itself allows for 3rd party repos now and everyone is mad at Kakao for making the App less usable.

they smoked their own supply is how. The management team ate the legal departments bs about how they are fighting a righteous cause here.

Nope they are only using API’s from the various hosting sources. That’s what makes this request so blatantly fraudulent. For all intents and purposes Tachiyomi is just a Browser specialized for Manga

Essentially Kakao Entertainment abused DMCA to get all extensions removed despite the Extensions themselves not containing any DMCA material. What allowed this to spiral so out of control (it started out with only Bato.to, Mangadex and Kissmanga being removed) was that the Tachiyomi devs have absolutely 0 spine and 0 will to prevent DMCA abuse. They just folded at the requests immediately without any sort objection or demand to go through GitHub instead (this approach in particular has worked in warding off false DMCA claims because that way the corporations have to somewhat publicly press their illegitimate claim, worked wonders for youtube-dl afaik)

Not surprised in the slightest. Having a doormat DMCA policy and then not even using GitHub as a shield (like youtube-dl for example) is just asking for it. The dev response doesn’t really help so I guess the App is dead. Maybe a fork will pick up the pieces but I have no trust in the main repo devs to do the right thing or work in the users interest.