#Hypercapitalism involves the devious practice of passing people 💩 turd sandwiches wrapped in glossy paper, and have the recipient be happy and surprised when opening them.
Because only outward packaging is all that matters, the superficial layer. Hypercapitalism aggressively teaches to look no further. To not see deeper value and meaning. For its practioners, which we all are to an extent, superficiality is thus the "Return on Lack of Investment" we get in return.
Hello fedi. i am trying to solve the "fetch all replies" problem once and for all that makes the fedi feel a lot more desolate and with a lot more reply guys in it than it should be. this is take two, where before i had it triggered by a button, but now i think it should happen on the server-side whenever you expand a post. can anyone help me out figure out how to make this more efficient by only fetching posts that the server doesn't already have? i am not sure what the best strategy would be, and if anyone with experience doing efficient rails and SQL stuff could give me some pointers that would be gr8. the patch is actually extremely simple it just needs a few nice things to make it not DDoS everyone.
> and with a lot more reply guys in it than it should be
As it happens this morning I was coincidentally side-tracked on a self-assigned quest to put thoughts on "Reply Guy" anti-pattern together on #SocialCoding movement's forum.
Witnessing another occurrrence of the #ReplyGuy anti-pattern this morning inspired me to write some thoughts about this social behavior that is so common on our #Fediverse that is based on #PublicSquare#Microblogging mechanics.
On the #SocialCoding forum I created a category for #SocialExperienceDesign (or #SX) patterns, and the "Reply Guy" #AntiPattern is the first entry in what might be turned into a pattern library collection.
https://discuss.coding.social/t/unionize-free-software-found-software-guilds/59 the recent #XZ disaster has prompted me to reread my own article from two years ago next month on "Free Software Unions". While I'd put some of the details in there differently today, I think the core point still stands: that free software maintainers are vulnerable to exploitation, both from Big Tech and, as is now evident, malicious attackers. And that the only way to protect them is to join into mutual support, solidarity groups.
For decades I'm learning to code on and off as a hobby. I feel like helping out in #foss would be a gamechanger for me but I cant identify where to help (I know some python and c# but nothing great).
My github account is meh at best and when TIL about git forges joining the #fediverse I was thunderstruck. Is anyone else eager to de-corpo git once we have it running? Forgejo seems to be pioneering atm.
58 rules for beautiful UI design: interesting rules, and I really like that “ELEGANCE” acronym, but, I always try to think critically when anyone brings some “design rules”.
For example:
“good design is as little design as possible”: while simplicity works for some B2C interfaces, oversimplification can lead to a lot of issues, especially in complex enterprise products, for expert users.
Years ago I was discussing a "Human Flourishing Design Guide" and thinking of launching a Flourishment Initiative within which a periodic table of patterns would shape up.
Right now I'm involved with #SocialCoding movement and reviving the field of Social experience design or #SX for the #SocialWeb. That periodic table is still a very nice way to present a pattern library.
I'd like to give a heads-up to #SocialCoding movement where I'm involved and plan to revive the notion of #SX or Social experience design, esp. for the #SocialWeb.
So much chatter on #Fediverse is either deeply technical or app-specific. The field of SX may offer a more holistic and inclusive perspective, focus on methods, guidance and best-practices.
I would love a #recipe manager with #ActivityPub integration. Like imagine how cool it would be to post your recipes, follow others, comment on each other’s recipes, and even fork/modify recipes and see that relationship from the original recipe. You could have instances focused on cuisine, dietary restriction, cooking method, zero waste, or even your own if you’re a blog… does this exist already? I really want it to exist. #OpenSource
my thermonuclear take is that the issue here isn’t whether it matters that we call AI “AI”
but that Mastodon’s culture is poorly socialized and people here have a hard time doing constructive conversation
This is frequently lamented as “replyguyism,” but I think that’s imprecise. Something happened along the way to mislead people here that derailing the conversation makes friends
Oww 😍 .. such fabulous discussion here. Sad thing is that given fleety nature of Microblogging, next week most has moved into forgetfulness and link rot sets in.
A side-note: #SocialCoding is technically no community-building effort. Given its very broad scope it is explicitly a Movement and a #DoOcracy. As a movement it should 'emerge' organically (or not, which is also fine, there are no expectations).
This may seem weird, but aligns to an effort I hope to launch regarding collaboration in grassroots movements and technology ecosystems, where broad-scoped community "herding of cats" doesn't work.
I've noticed some people refer to me as a dev, although I never claimed to be one. One person even accused me of not having recent commits in Firefish. So... I have to confess I am not a dev.
My role in Firefish was community manager/project coordinator. But isn't it interesting that people assume I'm a dev because I was in the core team? It's so often that community-driven open source projects are run only by devs, that people just assumed I am a dev too. And, with all the respect to the wonderful dev community, I think that's kind of a problem.
You see, an open-source project needs much more than coding. My role in #Catodon will include coordinating development, designing features, testing, communication and feedback from the community, managing issues on the repo, decision making, moderating catodon.social, participating and moderating the matrix channels and I'm sure more will be added to that list. Devs may or may not be good at these things - and this clearly affect some projects. Being a good dev doesn't necessarily mean being good at everything around running an open source project, and that's ok. There's a reason companies hire project managers when developing software. You can add every community request out there - if you don't keep UX on your mind and don't have a consistent vision for your software, it will end up poorly designed and bloated.
So, I have to warn you - I may not be suitable to answer your more technical questions! We have a support channel for that, and our lead dev Namekuji is more knowledgeable about the coding aspect - while other devs, who are interested in our direction, have already reached out and are starting to work with us. So hopefully we will soon have a lively dev and admin community where we can support each other.
I'd say that one of my main goals in Catodon is to offer a safe, inclusive and laid back environment where open source devs will be able to cooperate and contribute in a productive way. Making open source code is a wonderful gesture, you are sharing your work for everyone to freely use. And it deserves to be done in a well organized and self-fulfilling way! Good communication is not always easy, but it's definitely worth trying. We have incredibly talented coders here that can do wonders when working smoothly together. That's the mindset with which we'll be trying to make Catodon a community-driven project.
There's ultra-tech focus. Many projects start as hobbyism by a dev, then they grow and many different aspects come into play.
At (informal) #SocialCoding movement we defined the term #FSDL: Free Software Development Lifecycle, to include all good practices from inception to end-of-life of a project within its broader surroundings (community, ecosystem) to get to more inclusive processes.
Very interesting long read on “value capture” — when measurements like grades, citation counts, or step counts take over the true values (learning, writing, health) you actually care about. Also related to “stop the numbers game” by David Parnas (“Counting papers slows the rate of scientific progress”).
I'm fascinated by this. I began #SocialCoding movement ("Coding is Social") from observations on social dynamics in grassroots movements, particularly #FOSS and #Fediverse, where the former is inherently unsustainable (for participants) and the latter needs "substrate formation" (people + processes to evolve ecosystem/standards), which is ultra hard. We defined the #FSDL, a holistic Free Software Development Lifecycle. Research-to-practice is also part of it.
Just read about your intent to elaborate a bit on some of the #FediverseIdea issues. Would be wonderful, and most welcome.
The repository is under the #Fediverse org on Codeberg, where also the #FEP can be found, and fedi delightful lists I maintain (published to https://delightful.club ).
A student can't afford to pay the $8 per month for #Obsidian sync, so builds a #FOSS alternative. Then posts to HN and says "I probably violate ToS, so will take down the repo if asked".
Then the Obsidian CEO replies. Explains they aren't VC-funded and the $8 bucks subscription keeps the light on. Applauds the work of the student, points to other open ways that content sync can be handled and gives advice "if you rename, there's no ToS problem". 👍
@eternaltyro it is a good question. There's a need for it, and frequent discussion on the #Fediverse by interested people. But these discussions get lost in timeline history immediately.
There used to be #Flockingbird but this project is now archived.
If someone wants to start a project, then collecting a group of those interesting folks should be first, I think.
Places where the idea can be elaborated are on #SocialCoding forum:
Free and Open Source Content Circle is hosting an event next week and I'd like to invite you!
Exploring Self Governance in the Fediverse: A discussion about decision making among a federated ensemble
--> May 29th 15:00 - 16:30 UTC
We're a circle within @SociocracyForAll , so I'll be interested to find out how sociocracy can support you. There will also be time to chat about common governance models and tensions that arise.
For #FEP (Fediverse Enhancement Proposals) we think of specifying behavior as human-readable, tech-independent #Gherkin scripts. That can be a good approach. Same org has the #FediverseIdea repo.
Remind me: have we talked much, here, about my notion of the “convivial stack”? This is the idea that, to the greatest extent possible, community governance, the built environment and the technological surround should all, simultaneously be designed so that they are open, participatory and actively invitational; modular, user-modifiable and extensible; and reward experimentation?
Though topic isn't elaborated much, #SocialCoding adopts a holistic view on the entire Free Software Development Lifecycle, the #FSDL. Which then includes the question "How can fragmented small initiatives find cohesion and thrive in a sustainable ecosystem?"
Observation is that the ecosystem must be healthy, so it can evolve. And 'Ecosystem focus' is often absent.
And Free Software Development Lifecycle is this all-encompassing concept. FSDL includes Community, but also the role of the Ecosystem where projects operate.
Will arbitrary devs fall for the argument they better use a patchwork of #FreeSoftware tools rather than one-stop-shop integrated development experience?
I've been in the #openSource scene for a long time. From BEFORE this was even called "open-source" — back BEFORE the phrase "open-source" even got coined and became common.
Here is a problem with most open-source software projects have, including most #Fediverse software —
Though we do not have concrete plans yet (The Muskening™ thwarted thoughts about a public launch), the Social Coding Movement has exactly this scope that these toots are about.
The combination of considering the entire Free Software Development Lifecycle (FSDL) and how Sustainability should be holistically addressed, and with possible help of the supporting technology we are building on the Fediverse.
2023-09-04: Organise, Research & Document - Weekly Guild Report for Sprint #2 (discuss.coding.social)
2023-09-04: Organise, Research & Document...