Show newer

ipv6 is cool because you can just.. netcat someone over the internet

very cute imo (haven't written a custom fetcher/motd script for ouroboros yet)

@CaribenxMarciaX huh I thought this is what authorized fetch is supposed to prevent (and scholar.social does have that enabled)

aww seem NixOS can't quite do seamless boot + plymouth with luks entry yet :\

maybe tomorrow i will

- write the pixie pages DNS stuff (for custom domains)
- think about gotosocial things

I WILL NOT DRINK WATER NO MATTER HOW MANY TIMES YOU GUYS TRY TO MAKE ME #FUCKWATER

0:50 seconds left till drop pod extraction so stressfull aaaa

> No space left on device

what how, goes checking things, huh there's still 50gb free

realizes that was something running over ssh..

wow barrier is pretty magical (network KVM switching), I can just move my desktop's mouse over to my laptop and type too

activitypub dev 

@garbados gotosocial might go the same way lol

the Javascript ecosystem is essentially a failed anarchist society (long) 

What it used to be:
- many early adopters were anarchists/communists/etc.
- a huge public commons of highly reusable, high-quality, collaboratively developed libraries on npm, built for the benefit of the public, not for profit
- high degree of interoperability between different people's work, no need for pointless busywork to redo the same work over and over again
- successful(!) 'community specs' designed through community consensus (Promises/A+, CommonJS, etc.), gaining near-universal adoption
- fundamentally different structures from other language ecosystems, both technical and social, to make this work

What went wrong:
- large influx of users from other ecosystems due to hype in startup circles, unfamiliar with the established practices and reasons why
- early adopters failed to effectively convey and explain the ideological basis
- corporate adoption and subsequent capture; increasing "business value", leading to corporate steering of many essential pieces of the ecosystem (language spec, Node.js, etc.)
- npm became npm inc., a for-profit corporation, eventually being acquired by Github due to its large userbase, placing control over the public commons and its namespace in private hands
- ideological basis was forgotten, early adopters eventually left for greener pastures, now an almost purely parasitic environment of people leeching off the commons without guarding its integrity or health
- community-consensus specs started being replaced by "official", by-decree-from-up-high language specs (CommonJS -> ESM, Promises/A+ -> ES Promises)
- widespread adoption of these "official" specs, even though they were in many ways worse, due to their "official" label and many people assuming that what a central authority says must be correct or better
- rapid increase in shiny, well-marketed new tooling that is not interoperable with the existing ecosystem at all, and frequently works less well
- more and more commercial/proprietary 'sidecar' services (eg. Snyk) that you are expected to use, sometimes replacing open initiatives
- now an ecosystem and public commons that is rotting in every aspect with no real hope for recovery

... we should probably learn from this?

Show older
Pixietown

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