Show newer

Stop normalizing that you need to go find an alternative to a FOSS project the very hecking moment it goes into maintenance mode/read-only/archival.

Good gods people are already going "Neofetch is dead what's the alternative". It still works fine!

Normalize the idea that software can be "finished" and not be updated until a major feature shortfall or security issue arises, then someone can fork it. Or fork it now, I'm not your mom, but the original is still okay.

This May Day the cops are really working overtime to demonstrate why they should never be considered workers or part of the labor movement

vague 

@freakazoid Actually not a fedi thing I'm referring to, in this case

Hi friends,

The alt-text.org alt text library project needs a new leader, I have brain cancer.

I built a working, scalable, proof of concept library of shared alt text with fuzzy matching.

I'd like to connect with the #accessibility dev community. I want to hand the project off to a team or a leader if anyone is willing to take it over.

Github: github.com/alt-text-org
WIP MVP: a site designed for writing alt text with a private library: my.alt-text.org

Boosts appreciated

vague 

I guess DDoSing a moderation team with spurious complaint threads is a thing now

@bug Lots of folks have been working very hard to make it happen!

“this is `aynrando1970`s first contribution, please welcome them to the #NixOS Discourse!”

@elilla (Small correction: Eelco (project lead) and Graham (who posted on Twitter) are different people, though they started a company together)

After countless hours of pushing for change in the project's governance, there's a result!

discourse.nixos.org/t/nixos-fo

We're certainly not there yet, but this is definitely an important step forward, that hopefully finally creates space for solving the rest of the issues.

Now excuse me while I hibernate for the next 3 years to recover...

@algernon I would recommend giving it a few days to see what comes out of the board statement tomorrow. It's unlikely that anything will spontaneously stop working, because contributors are in the same boat of being tied to it - it's just not clear whether it can continue as NixOS or whether a (compatible) fork will be needed.

personally, if someone on cyberpunk.lol tried to report a post on here or elsewhere for "begging" i'd nuke the entire account without hesitation

it speaks to a sort of horrible cruel capitalism-poisoned mindset that can take shitloads of time and effort to overcome, and i am under no obligation to let other people get caught in that crossfire

Show thread

Who called it “search engine optimization” instead of adversarial attacks on ranking algorithms? #SEO

@AngryAnt @soupglasses@hachyderm.io @jakehamilton@hachyderm.io I imagine that Guix is its own project for a reason, and they may not appreciate a sudden influx of former NixOS users and the cultural divide that that introduces, either.

I'm not saying there's anything wrong with working together, but definitely don't assume that "moving to a pre-existing fork" is the right solution either! It can just as easily turn one governance problem into two governance problems.

“How do you accidentally run for President of Iceland? | by Anna Andersen”

Glad somebody wrote about this because it’s an objectively hilarious UX case study

(And they just announced that eleven people managed to get the requisite number of endorsements in time) uxdesign.cc/how-do-you-acciden

@Jo TL;DR: years of moderation and governance issues going unresolved, environment having become unworkable, volunteers leaving over it, and a fork seems imminent if there is no rapid solution.

I wouldn't recommend diving into the details unless you have the time and energy to commit to it, because there is a long history, most of it is badly documented, and a lot of it involves subtle abuses.

There is likely to be a resolution soon, one way or another.

:boost_requested: : I'm looking to find new programming languages that meet all(!) of the following criteria:

1. Dynamically typed.
2. Has a conflict-free module system. Not namespaces, not a flat dependency tree. It must support conflicting versions of the same module at different places in the (transitive) dependency tree.
3. Suitable for 'systems programming' tasks like OS kernel development, microcontrollers, ideally also the ability to write C-compatible libraries (some static typing for the API surface there is acceptable).
4. There is usable documentation (it does not need to be perfect).
5. Memory-safe (to at least the level you would find in JS/Python/etc.)

The language doesn't need to be well-known! And it doesn't need to have a lot of libraries available for it, but it should be usable for a real-world personal project. Hit me with your niche recommendations :)

(Please do not argue with me about the requirements. I am aware of what is and isn't possible.)

The more I'm involved in governance issues, the more convinced I've become that social decentralization is a critical component of a functioning society, and scale is the enemy.

There doesn't even have to be any malice involved.

I hope this emali finds you at all.
sent from a self-hosted email server

Hey, anyone on the NixOS subreddit. Note that no one from the NixOS community moderates the avenue. It is not an official location for NixOS discussions. And yes, individuals are now adding more FUD to the fire they lit. Again and again. Froggo's sad and hot.
Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.