@codewiz @maiyannah Slack nailed identity? You have a new one for each community, and in tighter communities you even have to tie each identity to a different mail address.
If #sandstorm solves a problem very few people had, that's because today the problem is so intractable that very few people are even aware that they would like to have that problem.
Projects like sandstorm are essential for finding the solution to #userops, and userops is essential for solving decentralization.
Decentralization is essential for saving the internet.
In my Copious Spare Time, I will make an OStatus/ActivityPub bridge, including general web bridge. Right after I finish my other vaporware project. Right after I learn all the OStatus ropes by digging into #pleroma.
I checked out the Pleroma repo 4 months ago. That's a start.
@cwebber On the other side of the coin we have https://identi.ca/mlinksva who has said a couple of times that large flagship nodes are the only thing that could be powerful and convenient enough to fight the big social silos. I'm not so sure.
Regardless if we try to solve centralization with federation or we believe true peer-to-peer is key, we need to solve #userops. From what I read, the people who are closing their OStatus nodes these days, be they Mastodon or GNU Social, are mainly doing it due to the burden of maintaining them.
This point of view is that devops was about teaching ops how to dev, and now it's time to teach dev how to ops, as if the positions were permanent.
The way I always perceived it was that devops was about devs and small companies being tired of the overhead of having an ops team, and trying to do it all by themselves.
With no ops team to defend their existence, devops had no qualms in trying to eliminate the position altogether, but in the end all that happened (like with all automation?) was that better ops was created/discovered, enabling more complex solutions like microservices, and now we're back at having ops, only at a higher level.
At small companies, it's still about having devs do ops, but I think we're at a position where we know better what that means.
@maiki Software providing users with some kind of deployment-ready bundle is next-next-level magic. We don't even know what a deployment-ready bundle are at today's level of #userops.
I've contributed one patch to the #Guix package tree and I've met and talked to Chris Webber, who contributes more to the Guix and Guile communities.
I just really want both #Nix and Guix to succeed, because they uniquely solve both essential problems and problems of convenience, and if I can't find the time to contribute to the code, at least I'll contribute in evangelism.
I think the problems of 1) service administration usability ( #userops ) 2) reproducibility and 3) polyglot package building, testing and development can only be properly solved by these systems, or something like them that doesn't yet exist.