Tootfinder

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

@chiraag@mastodon.online
2026-02-08 02:29:20

Linus on point as always.
lkml.org/lkml/2021/6/10/957
(yes it's old, but I just found it haha)

@kubikpixel@chaos.social
2026-02-05 17:15:13

Vibe Coding Is Killing Open Source Software, Researchers Argue
‘If the maintainers of small projects give up, who will produce the next Linux?’
Vibe Coding Is Killing Open Source.
According to a new study from a team of researchers in Europe, vibe coding is killing open-source software (OSS) and it’s happening faster than anyone predicted.
💻

@ruario@vivaldi.net
2026-01-06 14:30:44

@… I saw it. I already guessed what the issue was before I read the whole thing. I inheritted the Vivaldi Sbo. For unknown reasons, one of the previous maintainers long ago decided they did not like the name vivaldi-stable and changed both the package and various internal references to just vivaldi but the thing is a bunch of this stuff internally assumes everything w…

@tante@tldr.nettime.org
2026-02-05 22:00:04

"The study Vibe Coding Kills Open Source, takes an economic view of the problem and asks the question: is vibe coding economically sustainable? Can OSS survive when so many of its users are takers and not givers? According to the study, no."
(Original title: Vibe Coding Is Killing Open Source Software, Researchers Argue)

@hynek@mastodon.social
2026-01-23 12:48:14

DAE see lower-than-expected GitHub Sponsors payouts? (link is to the official but application-required maintainer community maintainers.github.com/ so you might not have access)

@karlauerbach@sfba.social
2025-12-03 23:32:24

Once again I wonder "Do the authors/maintainers of LibreOffice actually use it?"
For example, I am here on MacOs (Tahoe) and the buttons in LibreWriter to control Bold, Italic, etc are effectively same-color-on-same-color-background, in other words, unreadable. The only time they are actually visible is when the "Dark" theme is used.
Almost every time I use LibreOffice I am reminded why people pay actual $$ for products like Word/Office365.

@mela@zusammenkunft.net
2025-12-02 22:29:33

Wichtige Info für Syncthing-Nutzer auf Android: linuxnews.de/neuer-maintainer-

@khalidabuhakmeh@mastodon.social
2025-12-02 13:15:43

For folks forking IdentityServer. It's not "just code". There are decades of understanding specs, working with security teams around the world, ongoing support, and doing all those things continually.
When it comes to security, staying behind, or even worse, standing still, is the worst option.
From a maintainers perspective, think of doing all of the above for FREE to save your employer money for the "atta boys". In the meantime wasting the most precious …

@newsie@darktundra.xyz
2026-02-05 16:51:04

Vibe Coding Is Killing Open Source Software, Researchers Argue 404media.co/vibe-coding-is-kil

@frankel@mastodon.top
2026-02-01 09:19:43

The Most Important Code Is the #Code No One Owns
techyall.com/blog/the-most-imp

@cdamian@rls.social
2026-01-31 18:23:15

Following some PR discussions from open source projects in the time of LLMs is truly depressing.
I don't understand how maintainers can cope.

@pre@boing.world
2025-11-22 15:23:38
Content warning: re: bitcoin conference report

Bit root is explaining why there will only be 21 million bitcoin.
Block rewards every ten minutes halving every for years is an infinite sum tending to that 21m supply. In fact a few sats less due to rounding errors.
She explains why bit shift in the code is the same as halving due to the way binary number representation works.
The code stops shifting at 64 halvings , despite the fact the reward will be zero after 32. This is since c leaves 64 bits shifted off a 64 bit number as undefined.
But could the code just be changed? No. The source code maintainers could try, but node runners would refuse the update, it being against their financial interests to do so. Even if some nodes did do, you on your own node can resist.
When people created forks with more supply, the market sent it's price to zero.
#bitfest #bitcoin

@andres4ny@social.ridetrans.it
2025-11-22 19:50:50

Wow. I've dealt with various toxic personalities in software development, but a good portion of the time those toxic personalities were at least extremely knowledgeable in their (often, very limited) domain.
AI, however, seems to be enabling toxic personalities *who are completely clueless*. Impressive!
github…

quoted text: "Your approach of submitting very large relatively-low-effort PRs creates a very real risk of bringing the Pull-Request system to a halt, especially given that, in my personal experience, reviewing AI-written code is more taxing that reviewing human-written code."

response: "I do not intend to submit any more PRs of this kind. This was a proof of concept and an attempt to push AI as far as it would go. I believe that it has succeeded brilliantly! Also, *I would not call this a l…
quoted text: "we have in fact known this for years and the difficulty is to find a way to do it that maintainers agree comes at a reasonable maintenance burden)."

response: "I’m not a compiler developer by trade, although I’ve done all sorts of development over the years. I’m approaching this strictly as a user, perhaps a power user. I used to look at my needs and wants, and sulk because they were not addressed.

Damn, I can’t debug OCaml on my Mac because there’s no DWARF info.

Oh, wow…
quoted text: "I think that it is a case of different-to-the-point-of-being-incompatible software development processes (rather than a given process being fundamentally right or wrong), and I think that the uncertainty here is in part caused by our lack, on the upstream side, of a clear policy for what we expect regarding AI-assisted code contributions."

response: "That is something I’ve been pondering myself. I tried approaching several projects this way, trying to take care of things that b…
@adulau@infosec.exchange
2025-12-09 09:12:37

GCVE-BCP-02 Published - Version 1.3 (2025-12-09)

We’re pleased to announce the publication of GCVE-BCP-02 – Practical Guide to Vulnerability Handling and Disclosure, now available in its version 1.3.
This Best Current Practice document provides actionable guidance for organisations, researchers, and GCVE Numbering Authorities (GNAs) on managing and disclosing vulnerabilities effectively, both within the GCVE ecosystem and beyond

@UP8@mastodon.social
2025-12-12 21:43:51

🪞 Inside a global campaign hijacking open-source project identities
fullstory.com/blog/inside-a-gl

@schtobia@augsburg.social
2026-01-11 06:35:50

#cromite zeigt gerade wieder mal, was das Problem an Aftermarket-Lösungen bei Browsern ist - letztes Update am 13.12, Fdroid-Repo down, keine Reaktion seitens des Maintainers auf Github. War bei #Bromite auch schon so.