#psa

GitHub: "Here’s what we plan to do for maintainers."

https://github.blog/open-source/maintainers/welcome-to-the-eternal-september-of-open-source-heres-what-we-plan-to-do-for-maintainers/

If you use AI-generated code, you currently cannot claim copyright on it in the US. If you fail to disclose/disclaim exactly which parts were not written by a human, you forfeit your copyright claim on *the entire codebase*.

This means copyright notices and even licenses folks are putting on their vibe-coded GitHub repos are unenforceable. The AI-generated code, and possibly the whole project, becomes public domain.

Source: https://www.congress.gov/crs_external_products/LSB/PDF/LSB10922/LSB10922.8.pdf

https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me/

As a free software maintainer, this is entirely unacceptable. Now I have to spend time figuring out how to tell AI agents to *fuck off* so I don't have to deal with this.

The Open Source Lab is on the move!

Moving a data center is about more than just hauling servers—it’s an opportunity to modernize. We’re raising funds to cover the critical extra expenses incurred during this transition, including new high-speed networking equipment, remote management tools, and hardware upgrades.

Support our student-led team as they build a faster, more resilient network for the open source community.

https://osuosl.org/blog/data-center-migration-update-fundraising/
https://www.beavsgive.org/organizations/open-source-lab

inspired by CLAUDE.md, I’ve started putting markdown files named after coworkers into work code repos so I can remind them to stop doing shit to the codebase that annoys me

for some reason they’re all mad at me now, which means ill be adding commands to JEREMY.md for an attitude adjustment

oh good, my 25G NIC was manufactured by NVIDIA

that means I can use this meme every time it pisses me off

Hot #UX take: Instead of showing "unexpected #error", apps should expect more errors.

Story time!

We've had our cats for 2 years, they were 5 months old when we got them.

They both have their favorite toys, but Rory will carry his around howling into it. He sounds like he is in pain! (He is not, he has been checked out. I have trauma from an incompetent vet) He likes to take his toy, sit on the edge of the sink with the toy in his mouth and sing like Taylor Swift, if she were being strangled during a concert. (Sorry swifties!)

So at night we pick up their favorite toys.

Now reader, you may be thinking, "That's mean!" and we felt mean at first but we can SLEEP. And they have 2 large cat towers, 1 medium cat tower, 3 scratching posts, 2 cat tunnels, 2 interactive toys, and a toy box with a plethora of toys. They are fine.

But those toys aren't their FAVORITE.

Until last night.

The toy box is empty, I could hardly walk into my bathroom and I will spend a good part of the morning picking up the toys because apparently they "discovered" the toy box! 😳😆

Teenage cats are fun!
#CatsOfMastodon with #AltText always.

Do any moots know someone who we might be able to consult about restructuring a mid-size FOSS project? Essentially to migrate from a BDFL model to a more flat-structured democratic organisation.

We are discussing how to restructure #postmarketOS so that it can continue to scale up and be a truly community-run project.

We have some idea of how co-ops like Igalia do this, but we have a lot of differences (like being largely volunteer run and having very different goals) which leave us with a lot of unknowns.

To give an example of the kind of structure we're thinking of (by no means final, there hasn't been any broad agreement on a new structure yet):

We have the relevant pieces in place to form an assembly (everyone listed on https://postmarketos.org/team/ ) which could then democratically form teams and delegate responsibilities to them (e.g. finance/budget, technical policy-making, maintainers for various OS components).

The assembly would then also be responsible for deciding on focus areas and long term goals for the project (e.g. improving reliability, building a production-ready immutable version of the distro)

We could then form working groups to enable cross-team collaboration to move towards our specific goals.

Currently we lack a lot of understanding of the potential implications of something like this, how we can ensure the project doesn't get hijacked, that we don't drift too far from our mission statement, etc etc...

If you have a background in sociology and/or relevant experience from other projects then I would love to reach out and be able to discuss this in more detail!

#decentralization #opensource #freesoftware #foss

Fujitsu LifeBook T4215 Tablet PC from 2006

I recently saw someone leave fedi at least temporarily as a result of harassment, and one thing they highlighted was that most of us don't see the harassment they were getting because of how federation works and the fact that our instances block all the vile ones most of the harassment was coming from.

They were running their own single-user instance. 🙁

We really need better resources for single user instances to benefit from third-party moderation resources, but we also need to get the narrative out that running a single user instance is a horrible idea unless you want to be your own fulltime moderator or drowned in engagement from the worst parts of the net. Treating it as a viable option now really sours folks to the whole concept.

PSA: Did you know that it’s **unsafe** to put code diffs into your commit messages?

Like https://github.com/i3/i3/pull/6564 for example

Such diffs will be applied by patch(1) (also git-am(1)) as part of the code change!

This is how a sleep(1) made it into i3 4.25-2 in Debian unstable.

Achievement unlocked: present on an actual production device, step up after preseting on the devkit 2y ago! Switching back to Plasma mobile and running games, live at #FOSDEM !

https://fosdem.org/2026/schedule/event/SXNNMZ-snapdragon_8_gen_3_mainline_from_day-1_patches_to_product_reality/