Slightly unrelated to all the usual things: I am now trying out #sourcehut with a few projects and opted to become a paying subscriber.

https://sr.ht/ has this nice feeling of being clean, and purely work focused. I have not found any of the usual sales buzzwords on their site yet.

Plus, it all also is fully open, and runs local too if you so desire.

I do love #forgejo but this one is going to be for learning and expanding my horizon a bit.

sourcehut hub

Cannot believe what an absolute sparkly crapfest #github has become since the #microsoft acquisition 💩

#gitlab #gitea #forgejo #codeberg #sourcehut #bitbucket

Any/all of these are better than github đŸĒĻ

Something I genuinely deeply dislike about #email is that there isn't a way for a list's moderator to mark a message as spam once it has already been delivered to subscribers.
Context: Got hit by another GitHub comment notification masquerading as an official GitHub email.
But this is not unique to GitHub, all the mailing lists I've been on that had a spam problem - or worse, had people posting violent or disgusting images - could only resort to telling subscribers: "Hey, don't open that message from yesterday. I hope you didn't already do it." The whole thing is a pretty glaring #moderation hole.

If I want to have an async development workflow, is there a way to eg. set up (a mailng list on / an instance of) #SourceHut such that it's as resistant to targeted harassment as a more centralized forge / messaging platform?

@laedit I just wrote a tool to automate it and queries for other API params as well
https://sr.ht/~carnotweat/srht/
#sourcehut #agplv3 #rust
GenAI risk management: limit #GitHub exposure and switch to #sourcehut where @drewdevault has committed to protecting developers. #Microsoft allegedly trained GitHub #Copilot on #copyleft material code, when we all know #RAG #LLMs cannot cite like humans. Potentially massive IP violation. My PhD is #ccbysa and if the RAG LLMs can't abide by the terms, then the people who are using them are in violation. And yes, I will enforce terms. There's pending case law for this. Lots and lots of it!
#til #git commits messages esp for #sourcehut need always be valid #ascii chars for its #graphql api
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd6 in position 527572
0xd6 is a valid Latin-1 character (Ö) but invalid as a UTF-8 continuation byte. That byte pattern — a single high byte that isn't a valid UTF-8 sequence — is the signature of Latin-1 or Windows-1252 encoded text leaking into what should be a UTF-8 response. Likely a commit author name with a non-ASCII character encoded in Latin-1 by their git client
but why
> GraphQL errors with non-ASCII or Latin characters in JSON usually stem from encoding mismatches or unescaped characters (like
\, ", or control codes
-
) causing jq to fail. To fix this, ensure the GraphQL server returns UTF-8, sanitize data for JSON-style escapes, or use --raw-output (-r) and --raw-input (-R) in jq
#jq #json
finally a case where i need #python as #bash gives up

It has been heartening to see the steady trickle of projects moving away from Microsoft GitHub to #FOSS friendly code forges like #Codeberg and #SourceHut, or self-hosting with tools like #cgit and #Forgejo

#Gentoo has been up and running on Codeberg all week which has made it easier for me to contribute to the O/S I use every day.

I'm now Proxy Maintainer for a handful of packages, including #VinylCache who also moved their bug tracker on Monday, making it possible for me to contribute 😀

Been a little busy with work / family life, but finally got around to pushing out some very minor updates to the wruby project.

Also wrote about building wruby through #sourcehut builds + hosting with pages:

"Automatic Deploys to SourceHut Pages"

https://wruby.site/posts/deploy-sourcehut-pages/

#ruby #blog

Automatic Deploys to SourceHut Pages

With all the people moving from #shithub to #codeberg I really get the feeling of "Lets jump from one Silo into another".

Arguably a much better Silo, but a Silo still.

It really is time for #forgejo to get federation abilities. Because the majority won't go to #sourcehut and (the proper) email based development scheme unfortunately.

Or #radicle to succeeds. But I don't see this happen just yet unfortunately although it is really good already.

Sourcehut coolness: create a new Git repo on-the-fly by pushing to a not-yet existing repository. So nice :-) #sourcehut #srht