![](https://bookwormstory.social/pictrs/image/f8d584ce-cb7d-490c-83f1-c03e89780fef.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
I’ll be that guy: Use forgejo instead, its main contributor is a Non-Profit compared to Gitea’s For-Profit owners
Just some IT guy
I’ll be that guy: Use forgejo instead, its main contributor is a Non-Profit compared to Gitea’s For-Profit owners
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.
I only suggest Linux if they complain about Windows. The only thing gushing about Linux unprompted and unwanted does is sour the waters.
And also double check whether their use case actually works on Linux, all the improvements in recent years are nice but there are still enough edge cases that checking beforehand is a good idea
Because the lemmy.ml admins have a very particular moderating style they want to extend to all of the communities on their site I guess.
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’
It’s usually the cache after the dns making you think it was the cache all along when it’s just still hanging onto messed up dns data
Same line of thinking, if someone in the FOSS space would take up a similar project I would absolutely financially support that. For how good that keyboard feels right now probably even a relatively large sum monthly.
I’m trying it out and it feels oddly comfortable. Obviously muscle memory from the regular layout is getting in the way but I can feel that the devs are onto something.
It’s probably a combination of this and technical difficulties stemming from there being seemingly 20.000 Desktop Environments/Window Managers
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.
The developer working on federation plans to merge the changes into forgejo first and then from there into gitea but I’m not sure in how far the recent changes to gitea’s CLA have affected those plans.
Forgejo is a drop in replacement (they are committed to keeping it that way for as long as possible) so, as far as I know, simply changing the gitea image to the forgejo image is all you would need to do.
They did start a cloud service for hosting Gitea which introduces a direct incentive for them to make Gitea less hosting friendly by, for example, making newly added configuration options less comfortable to set up. And more recently some changes to code contributions that are not exactly community friendly (as a result forgejo will be unable to upstream some of their changes)
What lead to Forgejo, as far as I am aware, was less a problem that is already there and more the set of problems that have a very high chance of eventually manifesting, at which point forking the project would be too late.
This is absolutely awesome, I love it already. Substreamer had some real annoying quirks but it was the least worst option I found so far, this is better in almost every way for my use case
they likely blanket banned/filtered the .zip tld due to the rather large security problems it brings. I had the same problem with my instance initially before I explicitly whitelisted lemmy.zip
Gitea is managed by a for profit which is now offering a hosting service. That alone is already a conflict of interest because one of Giteas core features is the easy self hosting.
Then the contribution guidelines have been made stricter, anyone contributing now has to give up their copyright to the gitea management, meaning they could change the opensource license to a stricter one down the line without requiring community consent.
The concern is that as time passes features will be locked behind a premium tier for self-hosters or the self-hosting itself will be made more difficult in an effort to push their cloud service.
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.