A sincere tip for longtime fediverse people who would like their friends to stick around here longer than a week:
If you're on Mastodon or Hometown, you can click the "bell" icon in the profile of someone you follow. This will make it so that every time they post, it will appear in your notifications like an "@". I am enabling this temporarily for friends so that I remember to interact with them. This is important for making this place feel more lively and helps people stick around!
Created an intro page and a few issues for the social network moderation backend. https://github.com/weex/wot-server/wiki
The idea is to leverage emergent social structure to shun bad actors without needing to explicitly ban anyone or create collateral shunning of folks who seem to have joined the wrong server.
My favorite book about writing is Writing Down The Bones. https://nataliegoldberg.com/books/writing-down-the-bones/
It motivated me to write a lot more and with less purpose. Very freeing.
Hey #Fediverse the results of the #poll are in and the majority guessed in the right direction.
August last year @weex did a count of the 'Social Media Apps' section of https://delightful.club/delightful-fediverse-apps/ and counted 76 active developers.
What does this mean?
If you're interested in learning how writers write, check out The Paris Review Interviews series. For decades they've been talking with some of the best: https://store.theparisreview.org/products/the-paris-review-interviews-i
For someone like me who's can get a bit obsessed with process, these interviews read themselves.
Thank you @PaulaToThePeople for including me in your #followrecommendations. I just reached 100 followers which doesn't sound like a lot but feels like 10-50k bird site equivalent. One of my motivations for coming to the fedi was to have an impact and it's been heartwarming to see the response from so many real people from the work I care about.
This whole episode is confirming for me that the migration to the fediverse is inevitable and that every action taken in cweb is good for us.
What's particularly exciting about this is that nobody can know the result of thousands of communities molding the software to suit their needs.
Remember Twitter's super uber-secret project Bluesky? They finally explained what they're up to, and it's spicy 🌶️
So spicy that I had to write a 1,200 blog post one what exactly it entails. Key learning: Twitter doesn't like Mastodon. 🧵 https://blog.peerverse.space/lets-talk-about-project/
If you maintain open source software and don't use C4, I'd be really interested to hear your thoughts on this talk by the late Pieter Hintjens. The talk doesn't depend on video much so it works as a podcast. https://peertube.co.uk/w/2cw9QGY51ey6SiF3zPPtvW
The best feature of Git is that decentralization is baked right in. upstream
is just a label, and one that doesn't come along in a clone. This clean slate of context makes a first class citizen of every single copy of the source code. When you clone a repo, I feel like git should say something like "You now have the ball. What will you do with it?"
As the git/pull request flow becomes the norm, innovation in development process would seem naturally to look toward tooling for forks. How could we make forks interoperate more seamlessly? By perhaps making tools that transplant PRs from one repo to another with higher success.
Is it possible to develop better techniques for merge conflict resolution? I'm sure better understanding of the source of conflict could help.
How could we make package managers more flexible about which fork of a package to link into a stack? Working protocols and API specs seem promising avenues.
Been writing a lot more recently and it's just good. One trick to try is stream-of-consciousness, not stopping or going back to edit. I found myself still using backspace and stopping so made this single pager to help turn it into an exercise.
Write Without Stopping:
https://codeberg.org/weex/write-without-stopping
Join Magic Stone. It's a good community. You should contribute. Visit the website. Say hi in the Matrix. Discuss problems. Write code and get it merged. It's very simple and we can have some fun making accurate software.
You know when you search for information about an obscure library you need to get working, and the only relevant thing you find is a single forum post from 15 years ago asking your question, and the only response is "google it, idiot"?
In ten years, what you'll find instead is "join the discord for help" with a dead server link.
does anyone who is visually impaired or otherwise rely on screen readers have any experience with trying to use linux ?
from what i can tell the linux experience seems pretty hostile to screen readers, and there's not very much resources dedicated to orca, which seems to be the main implementation .
please share your experiences with me if you can, i want to try to make things better .
please boost
Software developer, IT consultant, FOSS proponent, editor on Fediverse Enhancement Proposals.
Founded: Magic Stone