Tootfinder

Opt-in global Mastodon full text search. Join the index!

@joshmoore@fediscience.org
2025-05-12 10:02:02

Open repos & AI bots
#FederatedMemory
coar-repositories.org/news-upd
and codeberg.org/forgejo/discussio

@nobodyinperson@fosstodon.org
2025-06-07 09:04:12

Oh wow ​LLMs are just so terrible. 🤦‍♂️
I made a #systemd service watcher¹ ( :nixos: #NixOS module²³) which regularly feeds systemd status outputs into an LLM (mistral here) and sends me an email if it thinks it found real problems. Well, now I always get alarmist emails with bullshit warnings, suc…

An email: Subject: ⚠ yann-desktop-nixos forgejo: "Urgent: Forgejo Service Overrun - Possible Resource Issue" Diagnose ======== PROBLEM Forgejo service has been running for over 4 hours without restarting or signaling an error, which is unusual. This may indicate a problem with the application or a resource consumption issue. It's recommended to investigate further and possibly restart the service.

Yann Büchau / ollama-watchdog · GitLab
GitLab.com

@simon_brooke@mastodon.scot
2025-06-04 21:43:28

@… I have a new #git repository on my laptop of a project I started today. What's the procedure for pushing it up to my #forgejo instance?

@bmariusz@techhub.social
2025-06-16 15:37:52

Day 9
TL;DR: Forgejo
Installed Forgejo and configured its native runner from scratch on Debian. Started with Woodpecker, but it turned out unnecessary. Everything now works locally with Docker integration and a working CI workflow.
Edit: added a GitHub backup workflow — every push to main now syncs code and tags to a private mirror repo.

Day#9 — Installing Forgejo and native Forgejo Runner
Today I installed Forgejo and configured its native runner from scratch. Initially I also installed Woodpecker CI, but it turned out unne...

@castarco@hachyderm.io
2025-04-18 21:50:16

Happy :neocat_bongo_down: , today I deployed a #Forgejo instance to manage my private code projects. I won't be using #Github anymore for my stuff, only to contribute to 3rd party projects.
I still have some pending work to configure the CI workers, but I'll leave that for next week.
Along the way I've learnt some stuff about #OpenTofu and networking. Enough to know that I still prefer to be on the dev side of the "devops" :neocat_googly_shocked: .

@simon_brooke@mastodon.scot
2025-06-03 07:30:19

H'mmm... My @forgejo instance has been hit very hard last night by AI crawlers, including from
* openai.com/gptbot (125,467 hits in 24 hours)
*

Graph of network traffic on my server over the past 24 hours, showing a very concentrated spike around 18:00, almost all public out.
@x_cli@infosec.exchange
2025-05-20 09:56:04

Ladies and gentlemen and others, this is why I recommend hosting your own forge, like forgejo: mastodon.social/@mcc/114536667
Also, as I recently discovered: Github git implementation is pretty dumb and reports unsolvable conflicts that are automatically solved by…

mcc (@mcc@mastodon.social)
Discovery: The "copilot" bot user that Microsoft will soon be flooding your github repos with garbage content from is implemented in some sort of special way that exempts it from the "block" feature you would normally be able to block other users/bots with https://github.com/orgs/community/discussions/159749