#codeberg

Did you know that Wide Angle Analytics:

1. Supported #Mastodon for many months (highest donor tier)

2. Donates to numerous open-source projects like #codeberg and #vue

Our product is not #FOSS. But we give back to the community that allows us to build great products.

Our customers (indirectly) support open-source projects.

Just saying :)

While backing up all my GitHub data and downloading everything I need before deleting my account, my website is now live on Codeberg Pages.

- https://midtsveen.codeberg.page/
- https://codeberg.org/midtsveen

I spent the weekend reviewing my GitHub account and am spending this week making sure all important data is backed up before deletion.

#GitHub #Migration #Codeberg

The Week in Review, Edition 89 (2025-17)

Topics:

Ebay: an iMac for 6.51 Euros

Village works. Sometimes.

Bikerouter – The Handbook (Work in Progress)

Codeberg vs. GitHub for Open Source Hosting

Rediscovered: FastRawViewer for quick photo sorting

CLI Tool of the Week: Taskfile

Listened to this week: Marlene del Mar, Tim Kollberg

#Weekly #iMac #Ebay #Village #Bikerouter #Handbook #Documentation #Codeberg #GitHub #FastRawViewer #Photography #Mac #CLI #Task #Taskfile #Techno

https://www.marcusjaschen.de/en/blog/2025/2025-17/

Wochenrückblick, Ausgabe 89 (2025-17)

Themen:

Ebay: ein iMac für 6,51 Euro

Dorf funktioniert. Manchmal.

Bikerouter – das Handbuch (Work in Progress)

Codeberg vs. GitHub für Open Source Hosting

Wieder entdeckt: FastRawViewer zum schnellen Vorsortieren von Fotos

Das CLI-Tool der Woche: Taskfile

In dieser Woche gehört: Marlene del Mar, Tim Kollberg

#Wochenrückblick #iMac #Ebay #Dorf #Bikerouter #Handbuch #Dokumentation #Codeberg #GitHub #FastRawViewer #Fotografie #Mac #CLI #Task #Taskfile #Techno

https://www.marcusjaschen.de/blog/2025/2025-17/

Love to see #GoToSocial on #Codeberg https://codeberg.org/superseriousbusiness/gotosocial @Codeberg #Fediverse

@Codeberg you are likely aware, but with the #Anubis protection in place https://archive.org cannot archive URL's from #Codeberg anymore. Possibly a necessary trade-off. So just FYI.

I'd like to move the Git repo for my R protopackage ("Inferno") from GitHub to Codeberg. I was wondering if Codeberg offers (even paying of course) something similar to GitHub pages, by which I mean something like this: https://pglpm.github.io/inferno

From what I understand, the Codeberg pages <https://docs.codeberg.org/codeberg-pages> should be something equivalent – but I'm not fully sure. Is that correct? And does anyone have examples of Codeberg pages of R packages, just to see their functionality? I didn't manage to find any examples.

Cheers!

#rstats #codeberg #git #bayesian

gptel-org-tools update.

1. Cloned to https://codeberg.org/bajsicki/gptel-org-tools, and all future work will be happening on Codeberg.
2. Added gptel-org-tools-result-limit and a helper function for it. This sets a hard limit on the number of characters a tool can return. If it's over that, the LLM is prompted to be more specific in its query. Not applied to all tools, just the ones that are likely to blow up the context window.
3. Added docstrings for the functions called by the tools, so LLMs can look up their definitions.
4. Improved the precision of some tool descriptions so instructions are easier to follow.
5. Some minor improvements w/r/t function names and calls, logic, etc. Basic QA.

Now, as a user:
1. I'm finding it increasingly frustrating that Gemma 3 refuses to follow instructions. So here's a PSA: Gemma 3 doesn't respect the system prompt. It treats it just the same as any other user input.
2. Mistral 24B is a mixed bag. I'm not sure if it's my settings or something else, but it fairly consistently ends up looping; it'll call the same tool over and over again with the exact same arguments. This happens with other models as well, but not nearly as frequently.
3. Qwen 2.5 14B: pretty dang good, I'd say. The Cogito fine-tune is also surprisingly usable.
4. Prompting: I have found that a good, detailed system prompt tends to /somewhat/ improve results, especially if it contains clear directions on where to look for things related to specific topics. I'm still in the middle of writing one that's accurate to my Emacs set-up, but when I do finish it, it'll be in the repository as an example.
5. One issue that I still struggle with is that the LLMs don't take any time to process the user request. Often they'll find some relevant information in one file, and then decide that's enough and just refuse to look any further. Often devolving into traversing directories /as if/ they're looking for something... and they get stuck doing that without end.

It all boils down to the fact that LLMs aren't intelligent, so while I have a reasonable foundation for the data collection, the major focus is on creating guardrails, processes and inescapable sequences. These will (ideally) railroad LLMs into doing actual research and processing before they deliver a summary/ report based on the org-mode notes I have.

Tags:
#Emacs #gptel #codeberg #forgejo #orgmode #orgql #llm #informationmanagement #gptelorgtools

PS. Links should work now, apparently profile visibility affects repo visibility on Codeberg. I would not have expected that.

PPS. Deleted and reposted because of strong anti-bridge sentiment on my part. Screw Bluesky and bots that repost to it. Defederated: newsmast.*

I am pleased to announce I've gotten off #github and have moved to #codeberg Seems very nice! Very nice indeed!

Añado a mi lista de pruebas pendientes este proyecto en lenguaje #c que he encontrado en #codeberg para montar una instancia de #activitybup . A ver si consigo que funcione en la #raspberrypi .

https://codeberg.org/grunfink/snac2

@rtsisyk @forgejo @organicmaps @zloidemon z Somehow this article managed to include #Codeberg under hosted services and not include #Forgejo https://forgejo.org/ under self hosting.

@farooqkz I've successfully modified the README.md to now point to your GitHub account as well as the #Codeberg repository.

It might be good to think about the possibility of letting previous contributors on GitHub have the ability to contribute without forcing the creation of a Codeberg account. A mirror or something might be good. (But since you're the maintainer now, feel free to do it the way you want.)

I hereby grant you the permission to take the branding.

If you would mention me and the prior work in the README, that would be really neat.

Adding RTL support is awesome. Glad to see work being done to make the theme usable for more languages.

@farooqkz Hey Farooq, no worries for the ping. I'm glad that you're thinking about being the future maintainer of the theme and bringing it to my attention.

If I can figure out how to mention your fork even on an archived repository I'll change it asap.

I'm not away from #github, I've just decided to make #codeberg the home for all future projects. Since I want to bring more attention to this great alternative of GitHub.

I'm on mastodon also for communication about this type of topics.

#codeberg

Thanks a lot to @Codeberg not only for mitigating/solving a spam attack but also for removing all the spam issues opened by bots on my #floss projects!

This is great service, I expected to spend some time to clean this mess up, but you already did it for me.

@jerger

Valid question! One I've really had to think about in the past.

First of all, I love the #codeberg mission and am a member of the association. We're on the same side.

However, I don't think #federated instances are the best solution to hosting the world's #OpenSource.

I think individuals (rather than organizations) should have the power to seed repos they care about and keep them online.

That is: I think the solution should be of a #peerToPeer nature, not of a #federated one.

@screwtape @Codeberg

I agree. I like #codeberg a lot. I donate.

They have limited resources and the pages server is overwhelmed.

As I started to put pages in to use the doc was slightly discouraging. But one of the main arguments is to turn it off, or at least state its unreliablity up front. I am ready to turn it on. But I'm not going to now.

I'm going to try #statichost and use codeberg for my repos. It doesn't hurt me.

For big projects in need of a site, this seems to be problematic. GitHub and gitlab have spoiled people and raised expectations.

@screwtape @Codeberg

Yea. I just moved my repos and #jekyll site from #gitlab after moving from #github a year ago. I do like #codeberg and #forejo. Much better than gitlab.

I just set up my woodpecker CI to build my site, but now realise I should just use statichost.eu instead.

@screwtape @Codeberg

There's an issue under heavy discussion at this moment as to whether #codeberg should continue with the pages service or not.
The server is apparently terribly broken and pages are unreliable.

https://codeberg.org/Codeberg-e.V./Discussion/issues/124#issuecomment-3923084

The only real eu option is to use statichost.eu instead.
https://www.statichost.eu/

It's a shame. It's one of the reasons that I recently moved to codeberg. I checked the doc, it said it worked, but then to use CI you need to get approved for the purpose as resources are limited.

But really, you probably shouldn't use codeberg pages, even for your #jekyll site.

@mattblaze Projects across #codeberg were hit with a wave of issue spam in the past 24 hours, that also veered into a racist language. Possibly related.

@bob The Fuzzel project got several, too. I did not recognize the first ones as spam. Many of our users are non-native speakers, so the quirky language did not throw me at first.

Indeed, the feature suggestions and bug reports were realistic and I started to respond as such.

It was receiving 7 in a similar style all with fresh accounts within 15 minutes that clearly showed the pattern.

Had the abuser been slightly smarter and patient, this could have been a real time-waster.

#codeberg