So I want to host my own Git instance for my personal projects. I'm experimenting with https://git.edent.tel/

It isn't quite self-hosted; I'm paying PikaPod €2/month to deal with the hassle of hosting and updating the software. I get to point my domain name at it which means I can always change the underlying service if I want. For example, it uses Gitea and I might want to switch to Forgejo later.

So far, it works. But there are a few significant drawbacks.

Network Effects

A large service like GitHub has network effects which are incredible. It feels like 90%+ of all developers have an account there. That means if someone wants to leave a comment or send a PR there is no barrier to entry. That's huge! There are a bunch of popular FOSS projects which make me sign up for yet another service when all I want to do is send a simple bug report which I find deeply annoying.

Luckily, Gitea has built in support for various OAuth providers. So I've set up single-sign-on with Gits Hub and Lab.

I asked people how easy it was to use - most people were able to use it, although a few people wanted a local-only account.

But is is still a bit of a faff. Even a little bit of hassle turns people away.

Forking isn't Federated

Suppose you want to make a Pull Request or just take a copy of the code. At the moment, you have to create a fork on my server. There's no way to easily fork something to your GitHub or personal server.

You can git clone the repo to your local machine, and you can manually move it elsewhere, but there's no way to send a PR from your repo to mine.

There's also no way for users to find other forks. Perhaps the upcoming ForgeFed proposals will fix things - but it doesn't exist yet.

As pointed out in "Let's Make Sure Github Doesn't Become the only Option" - most of the tooling of git hosting platforms isn't adequate for modern needs.

Discoverability

The easiest way to find code at the moment is to search GitHub. Moving my stuff to a different site means it will only be discovered by a general search engine.

I want people to find and use my code. If that's hard, they won't. I can point existing users to the repo - but it still cuts down on discovery.

Admin Hassles

Although PikaPods takes care of all the hosting administration, there's still the faff of setting up all of Gitea's options.

If I get hit by an automated spam attack, it'll be up to me to clean it up.

I'm not sure if I have the time, patience, or expertise to correctly and safely configure everything. Time spent administrating is time not spent coding.

Sponsorship

I get a little bit of money when people sponsor me on GitHub. There's no "sponsor" option on Gitea and, even if there was, the network effects of GitHub are substantial. Getting people to enter their credit card info into a random site isn't as convenient as clicking a button in GitHub.

Now What?

My most popular Github repo has around 140 contributors. I genuinely don't think I could attract that many people to OAuth onto my personal git hosting service.

Gitea seems to have a mixed reputation. But it's the only one offered by PikaPods.

There are interesting discussions about how to replace GitHub but they're only in the early stages.

Although €2/mo isn't a huge amount, I've gotten used to having free services on GitHub / GitLab / CodeBerg.

So this, I think, is my plan:

1. Leave my popular / sponsored repos on GitHub
2. Move my smaller repos to https://git.edent.tel/
3. Create new repos in there as well

I'm also going to look for a hosted Forgejo instance which lets me use my own subdomain - hopefully at a cheaper or comparable price. If you have any recommendations - please let me know!

😱 I Can't Use On This Day 😭

Seriously, What’s Going On?! 🔍
I’ve been trying to use the On This Day feature, but it’s just not working for me! 😩
Every time I input my details, it says I have no posts for today, even though I know I’ve posted stuff! 🧐

Here’s My Setup: ⚙️

• Python 3.x 🐍
• Access token fully generated (I triple-checked!) 🔑
• Attempted on multiple instances but still nothing! 😩😩

Could It Be a Bug? 🤔

I’m really starting to doubt my posting history! 😳
Is it supposed to show only specific types of posts?
I’ve made some pretty epic posts before! 💥💬

Documentation Confusion 📚

The README says to register for an access token but doesn’t clarify if it factors into this feature! 🤔❓
Did I miss something REALLY important?!
Help me figure this out, please!!! 😱

Feature Suggestion 💭

If this is broken, can we at least have a debug mode to log what’s happening! 😬
I need to know if it’s truly my fault or the code’s! 🔍🛠
Thanks for looking into this TRAGIC situation!!! 😭💔

P.S. My friends ARE posting on this day and their instances work!! 😤
I feel so left out!! 😟

Let’s get this sorted ASAP! ⚡

OK, that's a lot of Emoji - too much even for me! But if one of my users needs help, I'm there for them! As the feature works for me, I decided I'd ask for the output of the app. Maybe there'd be a clue in the minimal debugging output it had.

I clicked on the link to the Codeberg repository and was hit be a 404! What? I clicked on the link to the user "simpleseaport2" but that was also broken.

"Seriously, What’s Going On?! 🔍"

It looks like Codeberg has been hit by a wave of spam bug reports. I read through the bug report again, slightly more awake, and saw just how content free it was. Yes, it is superficially well structured, the Emoji are a bit over-the-top but not the worst I've seen, and the emotional manipulation is quite insidious.

A few weeks later, I got a bug report to a different repo. This one was also deleted before I could reply to it, see if you can spot that it is AI generated:

I've been trying to use the Threads tool to visualize some conversations but I'm running into a serious problem, and it's really frustrating!

When I input the URL for a post with a substantial number of replies, the script seems to hang indefinitely. I've waited more than 15 minutes on a couple of occasions, and nothing seems to happen. This is not what I expected, especially since the README mentions large conversations may take a long time, but doesn’t specify any limits or give guidance on what users should do if it doesn’t respond at all!

It's unclear what's actually happening here. Is the script failing silently? Is it the API timing out? Why isn’t there any sort of progress notification built into the tool? It feels like a complete dead end.

Can you please add some kind of error handling or logging feature to the Threads script? It would be helpful if it could at least inform the user when a timeout occurs or if the API response is simply taking too long. Additionally, could you clarify the maximum number of replies that can be handled? It’s really inconvenient to have no idea if the script is still processing or if it’s just broken.

Thanks for addressing this. I hope to see improvements soon.

• The emotional manipulation starts in the first line - telling me how frustrated the user is.
• It turns the blame on me for providing poor guidance.
• Then the criticism of the tool.
• Next, a request that I do work.
• Finally some more emotional baggage for me to carry.

I'm not alone in getting these - other people have also received similar spam

To be fair to Codeberg, they are under attack and are trying to stop these specious complaints reaching maintainers.

Post by @Codeberg@social.anoxinon.de

View on Mastodon

But, still, search the socials and you'll find a stream of frustrated developers.

Woke this morning to my first ever AI generated spam issue on a repo. Got it via email. When I went to check it out at Codeberg, it had already been moderated. Wonder how many others were affected. I immediately knew it was AI spam due to the overuse of emojis…🎉

[image or embed]

— Jeff Sikes (@bsky.box464.social) 24 April 2025 at 15:07

What's Going On⁉️

I can only think of a few possibilities - none of them particularly positive.

• Attacking the viability of CodeBerg - make users abandon it for a different platform.
• Attacking the attention of developers - make them unwilling to give attention where it is actually needed.
• Attacking the integrity of users - make them less likely to receive help because they are mistaken for AI.
• Maybe it is just a bored kid or an unethical researcher. Trying to find the limits of what a maintainer will recognise as spam?

Either way, AI bug reports like this are about as welcome as a haemorrhage in a jacuzzi.