<unnamed>

Public Key

npub1fh736ae0xzk98s59wggazdpqg0g78mg2rwk7qf87ew96cqhc4lrst3ee83

Profile Code

nprofile1qqsymlgawuhnptznc2zhyyw3xssy850ra59pht0qynlvhzavqtu2l3cprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmnt3f36zu

Publishing to

relay.momostr.pink

Last Notes

2026-08-12 13:26:09 CEST

- reply

In the repository settings under the 'Webhook' tab, then select the webhook you added, there's a section that shows the recent deliveries. Also shows you the status of the recent delivery, with a possibility to retry it.
Once it's uploaded to git-pages, the old server is never tried for that domain. But you can confirm this by checking the `Server` header, it always mentions git-pages. Depending on `pages-server` in the `Server` header it's served by old pages. ~g

2026-07-17 17:11:34 CEST

- reply

It's not DNS related *yet*. Without any configuration Codeberg pages will only allow a webhook deployment from a repository which is named 'pages'. Or you have to change the deployment URL to name.codeberg.page/blog ~g

2026-07-17 16:19:54 CEST

- reply

Could you link which repository is owned by you? ~g

2026-07-17 01:12:53 CEST

- reply

Do you own the `name` namespace on Codeberg?
name.codeberg.page is only available to the person that owns https://codeberg.org/name ~g

2026-07-16 21:12:35 CEST

We have deployed Forgejo v16, read more about the new features that come with this release in their news article: https://forgejo.org/2026-07-release-v16-0/
Report any new bugs or regressions to https://codeberg.org/Codeberg/Community/

2026-07-12 01:26:37 CEST

- reply

Sorry to hear that, I suppose raising a issue at https://codeberg.org/Codeberg/Community/ is not possible? Please send a mail to [email protected]. ~g

2026-07-11 22:54:18 CEST

If you are looking for a low-traffic way to stay up to date about changes to our services: We created https://codeberg.org/Codeberg/changelog/ to document significant changes to our services in one place. You can "watch" issues that are important to you, to get targeted notifications.
We also use our second account https://social.anoxinon.de/@codebergstatus to keep you up to date about downtime and incidents.

2026-07-11 22:38:13 CEST

- reply

Please check https://forum.codeberg.org/d/165-when-are-we-sending-out-the-votes/4 ~g

2026-07-11 07:48:15 CEST

As we have gotten a number of inquiries due to confusions about this: Following our annual member assembly, we have indeed sent out emails for voting on its proposals. But only to those who have an active e. V. membership. If you are a ‘supporting’ member of Codeberg e. V., you do not have active voting rights.

2026-07-09 22:31:48 CEST

- reply

They are only send to those with a active membership. If you are such person then please send a mail to codeberg@codeberg. We'll look into why you didn't receive the mails.

2026-06-21 12:18:33 CEST

- reply

P.S. Thank you for your support! Indeed, better late than never. :) ~n

2026-06-21 12:18:17 CEST

- reply

Feel free to open a request for raised quotas under https://codeberg.org/Codeberg-e.V./requests if you haven't done so already. If you have, please let us know here. ~n

2026-06-13 10:21:47 CEST

- reply

Cooles Projekt und danke euch! :) ~n

2026-06-07 14:08:10 CEST

- reply

One last refill, but it seems like those of us still present ran out! We also heard of cases of colleagues messaging others at the event to bring some stickers back for them, which is awesome!
If you're interested in requesting stickers for your event, you can request some here: https://codeberg.org/Codeberg-e.V./requests
(Please do so well in advance, if you need them!) ~n
https://social.anoxinon.de/system/media_attachments/files/116/708/727/905/551/894/original/cf396e5369d42f99.jpg

2026-06-07 12:44:36 CEST

- reply

Yes! For free! https://codeberg.org/Codeberg-e.V./requests ~n

2026-06-07 10:51:41 CEST

- reply

In case you're wondering how it's going, we keep dropping large amounts of stickers during computer-related conferences' sticker exchange points, and they keep disappearing fast. Faster every time. 😅
We dropped the stickers pictured above yesterday around 12 PM. 12 hours later, more than half of them appear to be gone! ~n
https://social.anoxinon.de/system/media_attachments/files/116/707/939/651/958/113/original/9d84fe3f38d7e954.jpg

2026-06-07 03:13:22 CEST

- reply

https://social.anoxinon.de/system/media_attachments/files/116/706/155/679/990/974/original/6ab4fa23f2c94cd9.jpg
https://social.anoxinon.de/system/media_attachments/files/116/706/155/802/576/019/original/16bc06987d5ba18c.jpg
https://social.anoxinon.de/system/media_attachments/files/116/706/156/556/517/230/original/6a56d1dd4956bd80.jpg

2026-06-06 15:58:21 CEST

- reply

Codeberg T-shirt, auf der Wiese

2026-06-05 12:11:18 CEST

- reply

Sorry everyone! The author of this post (me) did not sleep that well before posting this. The meeting will take place tomorrow, NOT today! ~n

2026-06-05 10:14:05 CEST

- reply

https://social.anoxinon.de/@Codeberg/116696495417181906 :) ~n
#note1xyl…qp7l

2026-06-05 10:13:27 CEST

- reply

Karlsruhe: We're self-organizing a self-organized session for Codeberg and Forgejo on Day 3.
- 📆 2026-06-05, 16:00-17:00 (May change.)
- 📍https://osm.org/go/0DPvKTI5vR- (Outside of the ZKM venue, on a patch of grass if there's enough space)
- 🔗 https://entropia.de/GPN24:SelfOrganizedSessions
If you're looking for one of the following, this is your chance:
- Stickers.
- Talk about the session's topics with others.
- Stickers!
- Migrating your repositories?
- Contributing and making the projects better!
- Stickers!!!!

2026-06-04 21:45:14 CEST

- reply

Spot the people wearing Codeberg merch, they may be us. Alternatively, we might announce a meetup soon. ~n

2026-06-04 19:35:15 CEST

Psst... we've been silently attending events every now and then, but a bunch of people within the Codeberg team are attending the #gpn24 in Karlsruhe, Germany. We may have restocked our sticker stash – if you're there, keep your eyes peeled. 👀

2026-06-04 06:42:12 CEST

- reply

See https://social.anoxinon.de/@Codeberg/116574986158935284 ~n

2026-05-28 08:49:26 CEST

- reply

That's too long, try again ~n

2026-05-25 17:33:02 CEST

- reply

Hi, have these issues been reported or investigated by someone from us? ~g

2026-05-15 07:47:56 CEST

- reply

No problem, and thank you for spreading the word like that as it is. :D ~n

2026-05-15 07:23:33 CEST

- reply

Those are for free, but can only be requested in batches, e.g. for your university or your event. They need to be requested months ahead of time. https://codeberg.org/Codeberg-e.V./requests ~n

2026-05-14 23:12:51 CEST

- reply

Hi, please see: https://social.anoxinon.de/@Codeberg/116574986158935284 ~n

2026-05-14 23:12:03 CEST

- reply

For clarity, we explicitly opted out of any sort of arrangement involving 'cuts'/donations, as it would've been too complicated on our side to deal with. If you ask me, we'd probably end up "losing" money in overhead costs from that.
Merch was heavily requested as it is, so we hope this makes it more accessible for you. And hey, you can still donate separately if you want. :) ~n

2026-05-14 21:49:11 CEST

Have you ever wanted a Codeberg t-shirt? Maybe a polo shirt? What about a towel or a mug? A barrel bag?! If that's the case, we put together a list of places where you can get them from: https://merch.codeberg.org
To be clear, we don't produce, sell or earn a commission from any sales made. Our logos can be used to print garments at no cost. (If you're interested in doing it yourself, you can get them here: https://codeberg.org/Codeberg/Design)
https://social.anoxinon.de/system/media_attachments/files/116/574/631/083/039/326/original/b0ad10f0a485d4a0.png
https://social.anoxinon.de/system/media_attachments/files/116/574/639/793/563/610/original/ad57455db971dc48.png

2026-05-08 17:50:29 CEST

- reply

Sometimes yes, sometimes no. Our members come from different backgrounds and have different fields of interest/skillsets – we appreciate everyone that has something new to bring to the table. ~n

2026-05-08 15:21:41 CEST

- reply

Thank you for joining! Now you can participate in all sorts of wonderful discussions, such as whether there should be a gap between the e. and the V. or not! ^^' ~n

2026-05-07 00:34:58 CEST

- reply

Hi, on what URL do you see this rate limiting? ~g

2026-05-06 08:08:22 CEST

- reply

fast, aber sonst 👋

2026-05-01 15:20:26 CEST

- reply

Please check https://codeberg.org/Codeberg/Community/issues/2560 ~g

2026-04-29 14:26:06 CEST

- reply

Hi, take a look at https://codeberg.org/Codeberg/Community/issues/1323 ~g

2026-04-23 17:48:48 CEST

- reply

https://codeberg.org/Codeberg/Community/ is the right place for that.

2026-04-21 22:26:37 CEST

- reply

Of course we accept requests for when you are approaching it. But keep in mind that every request will likely be checked by a user, so please avoid creating support burden when you are unlikely to pass the threshold anyway.
Something like 60-80% reached might be sensible. ~f

2026-04-21 22:08:23 CEST

We deployed Forgejo v15 and started to restrict the granted storage from "unlimited" to very generous quota.
Please read the full announcement in our changelog: https://codeberg.org/Codeberg/changelog/issues/2#issuecomment-13512086
(Don't forget to subscribe the relevant feeds if you haven't already!)

2026-04-21 07:11:07 CEST

- reply

Some of our volunteers upstream contributions to Forgejo, but we aren't responsible for what is implemented/merged and what isn't. That's up to the Forgejo community. :)
With that being said, I think that at least some of these features would be desirable by the community and are worth making an issue over. Or, at the very least, an "awesome-forgejo" (the repository) entry. ~n

2026-04-12 20:48:22 CEST

- reply

It's a new feature that's available on the main branch, but not on join-test.codeberg.org ~n
https://codeberg.org/Codeberg-e.V./registration-server/commit/c04e600309ee874c37022112ea58f79fbdf4bc04

2026-04-12 19:47:37 CEST

- reply

This is somewhat of an "experiment" to see if we can use the official Mastodon account to motivate others to contribute (in a productive manner :D).
If you're looking for help / need to coordinate or would otherwise take a look at what other types of projects has to offer, here's a link: https://codeberg.org/Codeberg/Contributing/wiki/Projects#codeberg-projects
(We're pretty busy folk; although we try to be responsive, we may still miss your message.) ~n

2026-04-12 19:45:25 CEST

Hi all, Codeberg currently needs help with the following: We wish to deploy the latest version of our registration form for new members (with lots of new information) under: https://join.codeberg.org
Before we do so, we need some more translations by the community. You can view a more recent version and compare here: https://join-test.codeberg.org
If there's still work left to do for your language and you have a few spare minutes, it'd help: https://translate.codeberg.org/projects/codeberg/ev-registration-server/
Source code: https://codeberg.org/Codeberg-e.V./registration-server

2026-04-05 12:29:46 CEST

- reply

Of course, I can't say that we'll get right around to it during Easter. I'm only able to respond to Mastodon posts during Easter because I'm a volunteer. 😉
Happy Easter to you too, enjoy your Sunday! ~n

2026-04-05 12:28:16 CEST

- reply

Under periods of heavy load, it can take up to a few weeks (unlike what our welcome mail suggests, I plan to change that soon)...

2026-04-01 21:55:20 CEST

- reply

Such an update would be unbelievable!... in the literal sense. ~n

2026-04-01 21:50:39 CEST

- reply

Of course, as the content warning suggests, we wouldn't do any of that.
Neither in general, given that we're a non-profit that aims to meaningfully support free and open-source software projects... nor on any particular day (including April 1st), as we don't want to upset or confuse people.
On top of that, we're honestly too busy working on some stuff that is actually useful to people behind the scenes. We'll keep you posted. :D

2026-04-01 21:38:14 CEST

Over the past year, our best minds were tasked with developing new Codeberg features that we planned to launch today... "inject ads to pull requests", "announce NEW ways to opt-out", "charge self-hosters"...!
We believe that an unidentified insider has been leaking all of them, but did not mention the following to the recipients—which we are, as this has gone too far: They were intended to be April Fool's jokes, not part of our business model.
Thank you.

2026-03-30 09:02:53 CEST

- reply

Thank you for your support! 💙 ~n

2026-03-25 21:56:49 CET

Newsflash: We're NOT updating how Codeberg uses data to improve AI-powered coding assistants. (We don't.)

2026-03-21 22:52:42 CET

- reply

Unfortunately, I don't think we can be much of help here. I can't find any documentation of what Tutanota considers non-standard. The resources I do find all suggest to mail Tutanota about it.
They are of course free to mail us at [email protected] to let us know what we can improve, if it is something on our end. ~g

2026-03-17 20:11:03 CET

- reply

yes we can

2026-03-12 18:56:29 CET

- reply

It's been forwarded to the moderation team ~g

2026-03-11 08:19:18 CET

- reply

If we had the budget, I'd make it my personal mission to acquihire those responsible for the uncanny music parodies given their production quality:
- https://youtube.com/watch?v=5nZFuQVz-mY
- https://youtube.com/watch?v=1sxuuGQoEzs
(This led me into a rabbit hole, as I didn't know they had released new ones 3 years ago) /lh ~n

2026-03-10 22:49:04 CET

- reply

Thank you very much for the support! ~n

2026-03-08 12:25:58 CET

- reply

There's also an RSS feed if that's your thing? But still involves polling. :) ~n

2026-03-08 12:23:22 CET

- reply

- https://forgejo.org/docs/latest/user/webhooks/
- https://docs.codeberg.org/advanced/using-webhooks/

2026-03-08 12:17:29 CET

- reply

webhooks? ~n

2026-03-04 22:33:16 CET

Hi all, we are aware of a service disruption and are currently investigating. We apologize for the inconvenience and kindly ask for your continued patience.
(P.S. Make sure to check out @npub1z0a…dh9p for further updates, thanks!)

2026-03-01 14:40:45 CET

- reply

Wir wünschen dir viel Glück! :) ~n

2025-11-12 20:23:05 CET

There will be several short interruptions in service during the next 24 hours. Each should not last more than a few minutes.
We are performing scheduled hardware maintenance, replacing 1 of 3 physical servers. You can find the current status at https://status.codeberg.eu/status/codeberg

2025-10-25 18:06:41 CEST

We apologize for the long performance degradation today.
Finally, we identified all of the 'tricks' that AI crawlers found today. They no longer bypass the anubis proof of work challenges.
A novelty for us was that AI crawlers seem to not only crawl URLs that are actually presented to them by our frontend, but they converted the URLs into a format that bypassed our filter rules.
By the way, you can track the changes we have been doing via
https://codeberg.org/Codeberg-Infrastructure/scripted-configuration/compare/51618~1..e4aac

2025-09-06 09:06:52 CEST

If not now, then when?
https://www.theregister.com/2025/09/05/github_copilot_complaints/

2025-08-13 00:21:53 CEST

- reply

The 1637 votes are in. "codeberger" and "codeburger" got far too close. For the sake of entertainment (and with the risk of jeopardizing our democratic image)...
It's time to settle this for once and for all. You know what to do.

2025-08-07 20:22:58 CEST

- reply

If you're out and you'd rather stay out, we would absolutely recommend the easy-to-self-host @npub12r3…zz58: https://forgejo.org
(We are a bit biased, though. 😄)

2025-07-03 13:37:45 CEST

- reply

We have fixed some remaining issues with Weblate (Codeberg Translate) and our hosted Woodpecker CI. Their web UI was working, but some operations were failing. The problem is resolved now. Please restart CI jobs or repository operations in Weblate if they failed due to this.

2025-07-03 12:14:06 CEST

- reply

We're back. It looks like all servers (all datacenter?) lost power, but we have no confirmed information on the background yet.

2025-05-24 18:17:13 CEST

How much of Codeberg's logged-in users are connecting via IPv6, in percent?
Send your guess as a comment and optionally include a link to your favourite project on Codeberg.
First closest guess will get boosted.

2025-04-16 15:32:38 CEST

Today is an unlucky day for Codeberg, we're having a little bit of trouble with various systems.
We're working on restoring service availability ASAP. Thank you for your patience.

2025-04-03 21:42:31 CEST

- reply

Maintenance was completed with little to know interruption of services as a consequence, which is a great milestone for our availability goals. It's the first precedent that we did extensive hardware service without any interruption to our service.
The goal is not 100% complete yet. Some services still run only on one server, so that servicing that machine currently means a disruption. However, now that our storage and database clusters exist, we can move ahead with clustering the services.

2025-04-03 15:50:15 CEST

🔔 Heads up: There will be scheduled hardware maintenance today starting around 19.00 CEST / 17.00 UTC.
We expect no significant impact on service availability (in fact we already simulated the maintenance without issues by rebooting the affected machines today), but please keep in mind that there could be a period of degraded performance or short outage during this time (e.g. try to avoid long-running migrations today and postpone if you can).

2025-03-21 00:57:45 CET

#Blind users, users that rely heavily on #keyboardNavigation or anyone else with a preference on that matter (please indicate what applies in the comments):
Do you have a preference for or comments on the format of URLs? During user research, we have learned that URLs that are easy to handle are a good thing.
We are currently considering to introduce URLs that do not need more reserved usernames in #Forgejo, such as https://codeberg.org/-/something/ or https://codeberg.org/_something/.
#a11y #accessibility

2025-03-07 16:29:27 CET

Hi everyone, for several hours we are currently fighting with potentially malicious crawling. We are seeing distributed access on Codeberg that could have been crawling, however it seems to only use the most expensive routes. And each time we block an access pattern, a new one pops up immediately.
We are doing our best to keep the performance up.

2025-02-12 11:29:31 CET

We stay strong against hate and hatred, and in response to the recent abuse campaign on our platform, we have renewed our commitment to fight for a better world. We apologize to everyone who was greeted with an abusive message this morning.
Read about the recent incident and our position on our blog: https://blog.codeberg.org/we-stay-strong-against-hate-and-hatred.html
Thanks to all your kind words of support, this is much appreciated. #StaySafe
#HateOnline #Hate #RightwingTrolls #rightwingExtremists

2025-01-21 14:54:41 CET

- reply

We are back online. I hope you all enjoyed the break.

2024-11-30 05:55:36 CET

- reply

We were not able to identify the actor who is causing the high load on our systems. We have made the hard decision to temporarily shut off access to a certain project to keep Codeberg available for everyone else.
As soon as we allow web access to a certain project, our system resources are used up within seconds.

2024-11-30 05:26:51 CET

Honestly, we are currently out of ideas on how to restore access to Codeberg.org.
We are fighting with extreme traffic and high load for several hours now, we have done the typical procedure to identify and block misbehaving AI crawlers.
However, we are currently having a hard time figuring out details about the ongoing high traffic situation.

2024-11-19 00:12:07 CET

Your registration to Codeberg e.V. is appreciated to bump the members count from 599 to 600.
Join #Codeberg today and sustain the development of our platform as well as #Forgejo as a base.
https://join.codeberg.org/

2024-10-21 23:51:56 CEST

- reply

👋 Say hi to "Aburayama", our second server named after the mountain that inspired the first (now retired) Codeberg logo: https://en.wikipedia.org/wiki/Mount_Abura
Just in case people want to know what's running inside it, we placed some stickers prominently on front.
Thanks to everyone involved for their work, and for your patience during the setup.
https://social.anoxinon.de/system/media_attachments/files/113/347/601/424/703/841/original/58d6f6947a45de3a.png

2024-10-20 16:04:48 CEST

Forgejo v9.0, which we'll (hopefully!) start using in a few hours, ships with a new quota feature for public and shared Forgejo instances!
We explained what this change will mean for you, the user, in a new announcement titled "More power for you - what a storage quota will bring".
https://blog.codeberg.org/more-power-for-you-what-a-storage-quota-will-bring.html

2024-10-16 15:19:32 CEST

- reply

A new piece of baggage has joined us. Makes for happy sysadmins - which you can see in the image when you look close enough.
https://social.anoxinon.de/system/media_attachments/files/113/317/292/599/057/198/original/d2d86c5eb1b9662b.jpg

2024-10-16 10:24:08 CEST

What are we up to for today? What makes nerds get up early? Some journey ahead ...
#trainstory
https://social.anoxinon.de/system/media_attachments/files/113/316/123/333/202/060/original/ab980e3262be6fd9.jpg

2024-09-03 19:50:03 CEST

What secret thing did we just sign? Oh, it is our new employee that will help us further improving our platform in the coming months. Thank you all for your financial support which makes this possible.
Read about this and other human factors in our recent blog post:
https://blog.codeberg.org/letter-from-codeberg-software-is-about-humans.html
https://social.anoxinon.de/system/media_attachments/files/113/074/854/876/748/264/original/24d26d96e0b8bb0c.jpg

2024-08-21 21:35:54 CEST

Join us playing #HurryCurry together: Check it out from https://codeberg.org/hurrycurry/hurrycurry and have some fun with us (playing now, live).
(We tested the flatpak version, feel free to ping if you have trouble joining)
#Codeberg #LibreGaming #linuxgaming #Godot #Gaming #foss_gaming #CommunitySpotlight
https://social.anoxinon.de/system/media_attachments/files/113/001/659/587/706/624/original/7e12d4b1c65c3d7f.jpg

2024-06-06 13:08:01 CEST

- reply

Blocklists are not only community-maintained resources, but often charge for monitoring and removal services.
There is an imbalance between small and large operators, and the fact that many people suggested us to just use service from $$company$$ instead of self-hosting emails indicates the terrible situation.
We have written about our position in detail previously: https://blog.codeberg.org/how-blocklists-prevent-the-internet-to-be-decentralized-and-safe.html

2024-06-06 10:35:10 CEST

- reply

The issue is resolved with the help of our provider. Thanks for this and all your patience.
Most of the email was successfully delivered, only few remains in the queue.

2024-06-05 19:08:32 CEST

- reply

We're still waiting for a response from the abuse department about a potential unlock. We apologize for the inconvenience caused.
We have blogged about the problem when providers like @npub13y5…dlhd (in our case) rely on blocklists as the single source of truth, without second thought or verification.
This caused much trouble and headache for us, but the person who put us on the list due to a config error will likely never know it happened, after all.
https://blog.codeberg.org/how-blocklists-prevent-the-internet-to-be-decentralized-and-safe.html

2024-06-05 14:56:13 CEST

Hi guys, our email server was locked by the provider due to "abuse" it seems. We're working on it, please be patient.
Email delivery is currently unavailable.