The Doctor
and 1 other
boosted
pvergain (framapiaf)
boosted
Vouch : un système visant à maintenir la qualité de l'open source face à l'afflux de pulls requests de mauvaise qualité générées par l'IA,
Il permet de gérer la confiance dans les contributeurs à un projet
Vouch : un système visant à maintenir la qualité de l'open source face à l'afflux de pulls requests de mauvaise qualité générées par l'IA,
Il permet de gérer la confiance dans les contributeurs à un projet
Social Media Channel
boosted
I have created a Github repository with an automatically updated CSV-file containing importable Infosec Mastodon people based on the @LukaszOlejnik Google sheet.
https://docs.google.com/spreadsheets/d/1t13k5_cNhP9_TgoUmqDZk2ROkWkF6Bg3O5269vKIqWw
Perhaps you find it useful, feel free to Boost the post and make sure others can benefit from this IMHO very useful list of Infosec people.
https://github.com/cstromblad/infosec_mastodon/
Update: Python-code has been published, and a Dockerfile as well.
Disclaimers et al.
Social Media Channel
boosted
I made a #Linktree Page
so I can list all the links of my #SocialNetworking profiles in one place for everyone to see.
https://linktr.ee/Etard_The_Lifecaster
#SocialMedia #Social #LinkInBio #Twitter #MastodonSocial #Mastodon #GitHub #Lastfm #Spotify #SoundCloud #IMDb #YouTube & more
Social Media Channel
boosted
There's always something more urgent: I've been known for a long time that sooner or later I'd feel prompted to switch from #github to somewhere else (since 2018 at least!), but I've been postponing and only very slowly flirting with the idea... That didn't work too bad for me: if I had rushed into it I would have probably migrated to #gitlab, before knowing about the more objectionable sides to it. In the end, 2025 was the year I finally acted upon the urge to move. I did not do a very thorough analysis of the alternative hosts - what I have been reading about them along the years felt enough, and I easily decided to choose #codeberg. Being hasty like that, alas, was a mistake: I just now found - during this slow and time-consuming process of deciding what and how to migrate - that there is a low repository limit on codeberg: "The owner has already reached the limit of 100 repositories." I'm not complaining, mind you, and those "lucky 100" that are already there will stay - at least as a sort of backup. But this means that codeberg is not for me - and so this time I turn to you, the #mastodon community.
What github alternative, not self-hosted, should I move my >100 projects into?
Social Media Channel
boosted
发现一个小玩具，比较有趣，针对Mastodon用于追踪特定推文的后续回复
https://github.com/hcschuetz/follow-toots
4 media
发现一个小玩具，比较有趣，针对Mastodon用于追踪特定推文的后续回复
https://github.com/hcschuetz/follow-toots
4 media
AI eliminated the natural barrier to entry that let OSS projects trust by default. People told me to do something rather than just complain. So I did. Introducing Vouch: explicit trust management for open source. Trusted people vouch for others. https://github.com/mitchellh/vouch
The idea is simple: Unvouched users can't contribute to your projects. Very bad users can be explicitly "denounced", effectively blocked. Users are vouched or denounced by contributors via GitHub issue or discussion comments or via the CLI.
Integration into GitHub is as simple as adopting the published GitHub actions. Done. Additionally, the system itself is generic to forges and not tied to GitHub in any way.
Who and how someone is vouched or denounced is up to the project. I'm not the value police for the world. Decide for yourself what works for your project and your community.
All of the data is stored in a single flat text file in your own repository that can be easily parsed by standard POSIX tools or mainstream languages with zero dependencies.
My hope is that eventually projects can form a web of trust so that projects with shared values can share their vouch lists with each other (automatically) so vouching or denouncing a person in one project has ripple effects through to other projects.
The idea is based on the already successful system used by @badlogicgames in Pi. Thank you Mario.
Ghostty will be integrating this imminently.
@mitchellh@hachyderm.io
That what forks were for.
Now, since your automation won't prevent forks, it looks either pointless or just divisive.
I mean, forks are good!
But are you sure that automated contributor managenent can solve automated theft and regurgitation by corporations?
If your project spreads, you would be in the position to execute a wide variety of #SupplyChain and #DDoS attacks.
Even if you wouldn't, anybody taking control of your repo could, turning such repo into a high-value target.
You should really take effective #security measure to avoid this outcome.
For example you could force downstream project to fork and adapt your scripts by only ever pushing on your repo slightly broken code.
Eg, you could apply before each push an easy to invert
____
Also, #GitHub?
The reign of #CopyALot?
I guess projects still there face no trust collapse in AI contributions and in contributing to AI.
@driggy@mastodon.gamedev.place
#AI eliminated the natural barrier to entry that let OSS projects trust by default.To me, this reads:
Corporate automation eliminated the natural barrier to entry that let #OSS projects trust by default.I'm not much sure what you meant with "trust by default", but for sure #opensource projects never let unreviewed code in from strangers.
That what forks were for.
Now, since your automation won't prevent forks, it looks either pointless or just divisive.
I mean, forks are good!
But are you sure that automated contributor managenent can solve automated theft and regurgitation by corporations?
Who and how someone is vouched or denounced is up to the project. I'm not the value police for the world.If it's your code that executes the "flat text file" in the repository, you are in control.
If your project spreads, you would be in the position to execute a wide variety of #SupplyChain and #DDoS attacks.
Even if you wouldn't, anybody taking control of your repo could, turning such repo into a high-value target.
You should really take effective #security measure to avoid this outcome.
For example you could force downstream project to fork and adapt your scripts by only ever pushing on your repo slightly broken code.
Eg, you could apply before each push an easy to invert
find vouch/|grep nu|xargs -n 1 sed -i 's/use/!!!BrOkEN!!!/g'This way no one coukd directly use your GitHub actions without reviewing them and nobody would need to #trust you or your security practices.
____
Also, #GitHub?
The reign of #CopyALot?
I guess projects still there face no trust collapse in AI contributions and in contributing to AI.
@driggy@mastodon.gamedev.place
I was a little bit nostalgic over the Atom text editor being sunset when Microsoft bought Github.
But not only did I find Pulsar. I also found out "activate power mode" still exists. https://packages.pulsar-edit.dev/packages/activate-power-mode
Ruud Steltenpool
and 2 others
boosted
Are you using #Codeberg to host your favorite AI-assisted and otherwise vibecoded project because your desire for dopamine has utterly destroyed your willingness to learn new things? Do you neither care about how you're "flooding the room" of the free software ecosystem nor about the greater societal implications, insisting that "it is what it is"?
Check out #GitHub, the world's most popular AI-first platform! Copilot, annoying maintainers with slop, you'll fit just right in!
Are you using #Codeberg to host your favorite AI-assisted and otherwise vibecoded project because your desire for dopamine has utterly destroyed your willingness to learn new things? Do you neither care about how you're "flooding the room" of the free software ecosystem nor about the greater societal implications, insisting that "it is what it is"?
Check out #GitHub, the world's most popular AI-first platform! Copilot, annoying maintainers with slop, you'll fit just right in!
FinchHaven sfba
boosted
Mastodon gGmbH may be getting rid of the Pinned Post carousel -- created because some bright-eyed young Mastodon dev decided unilaterally that a column of pinned posts was obstructive to new user Mastodon on-boarding
Not that @Mastodon dot Social -- currently at some 313,843 Active Users -- needs any help in sucking even more people into its maelstrom
Here, on #Github: https://github.com/mastodon/mastodon/pull/37761#issuecomment-3861069974
Mastodon gGmbH may be getting rid of the Pinned Post carousel -- created because some bright-eyed young Mastodon dev decided unilaterally that a column of pinned posts was obstructive to new user Mastodon on-boarding
Not that @Mastodon dot Social -- currently at some 313,843 Active Users -- needs any help in sucking even more people into its maelstrom
Here, on #Github: https://github.com/mastodon/mastodon/pull/37761#issuecomment-3861069974
Neil Brown
boosted
I just noticed #GitHub have started charging a 6% transaction fee if you sponsor someone via them. Pffff... might have to do more direct sponsorship.