I'm coming to the conclusion that community-owned and operated small clouds (co-ops) with easy onramps for self-hosting open source services like mail, storage, and VPN are the only way forward.
-
@T2R That sounds pretty good as well, although I suspect some level of community support makes that a lot smoother.
@mttaggart right but only as supporters and maintainers. Not hosts. Probably some sort of containerized system. That way it can run on NAS devices or full on servers.
-
I'm coming to the conclusion that community-owned and operated small clouds (co-ops) with easy onramps for self-hosting open source services like mail, storage, and VPN are the only way forward. Every corpo service is eventually going to make you ashamed to use it.
@mttaggart I don't know if you've seen this thread but it discusses some of the challenges involved, you might find it helpful.
-
@mttaggart I don't know if you've seen this thread but it discusses some of the challenges involved, you might find it helpful.
@ShaulaEvans Yes, it's been shared elsewhere in here! I think it's important to think about the issues of scale and what staying small might change about the calculus—both good and bad.
-
I guess I need to clarify that this model does not solve every ill of the current state of technology in society. It is an exit from reliance on corporate services that don't align with one's principles. What you're willing to pay for that is a decision for each community to make.
I guess I should also note I think private VPN is a solution unfit for the problems for which it is mostly used. But I do want people to have options to exit the corporate internet that don't require years of IT experience.
-
I'm coming to the conclusion that community-owned and operated small clouds (co-ops) with easy onramps for self-hosting open source services like mail, storage, and VPN are the only way forward. Every corpo service is eventually going to make you ashamed to use it.
@mttaggart I have heard of this model being used in Barcelona. I think that @brunovianna might be able to provide further information.
-
@mttaggart @philcowans @vfrmedia it's not scale that we're concerned about. scale is not the blocker we are identifying.
@ireneista @philcowans @vfrmedia I understand. That was more in response to the DEF CON conversation. I think and hope I understand your concerns.
-
@ireneista @philcowans @vfrmedia I understand. That was more in response to the DEF CON conversation. I think and hope I understand your concerns.
@mttaggart @philcowans @vfrmedia yeah, we do think you do. sorry if that was intense, the feelings we're having are about us, not you, don't worry.
-
@mttaggart @philcowans @vfrmedia yeah, we do think you do. sorry if that was intense, the feelings we're having are about us, not you, don't worry.
@ireneista @philcowans @vfrmedia Not at all. I deeply share your concerns, although I am not living them as y'all are. I wish I had better answers.
-
@ireneista @philcowans @vfrmedia Not at all. I deeply share your concerns, although I am not living them as y'all are. I wish I had better answers.
@mttaggart @philcowans @vfrmedia all anyone can do is our best
-
@mttaggart I love that. Need to do some more research, but would love to get involved with making a US, or even US regional version of this happen.
-
I'm coming to the conclusion that community-owned and operated small clouds (co-ops) with easy onramps for self-hosting open source services like mail, storage, and VPN are the only way forward. Every corpo service is eventually going to make you ashamed to use it.
@mttaggart see @thedarktangent recent post on the difficulties of hosting email and VPN services.
-
I'm coming to the conclusion that community-owned and operated small clouds (co-ops) with easy onramps for self-hosting open source services like mail, storage, and VPN are the only way forward. Every corpo service is eventually going to make you ashamed to use it.
@mttaggart yeah i agree with this, my main issue right now is that making software for the average person that happens to be properly decentralized is quite hard
they struggle a lot to understand the separation between the app and the server, or what a server even is, and i feel that if we want to make huge change, we have to educate the people and redo the way people see these kinds of services altogether
(... plus build less technical spaces that offer a better and more interesting service than the corpo alternative)
-
@mttaggart see @thedarktangent recent post on the difficulties of hosting email and VPN services.
@deepthoughts10 @thedarktangent It's been shared a few times in here
-
@mttaggart see @thedarktangent recent post on the difficulties of hosting email and VPN services.
@deepthoughts10 @mttaggart @thedarktangent Do you have a link to that post?
-
@ShaulaEvans Yes, it's been shared elsewhere in here! I think it's important to think about the issues of scale and what staying small might change about the calculus—both good and bad.
@mttaggart I hope you can find a way to do it! I wish you all the best.
-
@mttaggart yeah i agree with this, my main issue right now is that making software for the average person that happens to be properly decentralized is quite hard
they struggle a lot to understand the separation between the app and the server, or what a server even is, and i feel that if we want to make huge change, we have to educate the people and redo the way people see these kinds of services altogether
(... plus build less technical spaces that offer a better and more interesting service than the corpo alternative)
@nelson I would venture that "we just have to educate them" is a strategy with a poor track record. And that's coming from an educator.
I suggest that the tools must make those distinctions effortless or unnecessary to the user.
I think @HolosSocial is on the right track.
-
@deepthoughts10 @mttaggart @thedarktangent Do you have a link to that post?
-
@nelson I would venture that "we just have to educate them" is a strategy with a poor track record. And that's coming from an educator.
I suggest that the tools must make those distinctions effortless or unnecessary to the user.
I think @HolosSocial is on the right track.
@mttaggart @HolosSocial i disagree with making it 100% turbo decentralized and exist kind of like a cloud in the middle of nowhere because that has been tried in stuff like matrix and others and it just has led to a lot of different issues, mostly because of how media proxies work and how it entirely destroys any sense of moderation.
i still think it is a good idea to create something more akin to... towns, that specific people with enough time can dedicate their resources to mantaining, so that other people can join freely and adhere to existing rules, kind of like the fediverse, but removing the "black box" element of "you just join and it just works" even though it's a federated system
i think the way through is not unification, but intentional separation of the presentation and rules and structure of each instance, but total unification of the protocol and basics so that people can choose their own client and technology can be simplified to them
i think that... there's also a nomenclature issue in how we manage this kind of thing, right? where we call it "the fediverse" and "federated" and "decentralized" on "servers" that "speak activitypub" and use the "mastodon api" for the "client", it's just very confusing when you frame it as open source tech specifications when it should be treated instead with analogies and metaphors, which is how the early days of personal widespread computing got their way with letting people understand how the underlying tech works: the wallpaper, the files, the desktop, the recycle bin... all of these are analogs for real life objects
-
@deepthoughts10 Thank you!
-
@mttaggart @HolosSocial i disagree with making it 100% turbo decentralized and exist kind of like a cloud in the middle of nowhere because that has been tried in stuff like matrix and others and it just has led to a lot of different issues, mostly because of how media proxies work and how it entirely destroys any sense of moderation.
i still think it is a good idea to create something more akin to... towns, that specific people with enough time can dedicate their resources to mantaining, so that other people can join freely and adhere to existing rules, kind of like the fediverse, but removing the "black box" element of "you just join and it just works" even though it's a federated system
i think the way through is not unification, but intentional separation of the presentation and rules and structure of each instance, but total unification of the protocol and basics so that people can choose their own client and technology can be simplified to them
i think that... there's also a nomenclature issue in how we manage this kind of thing, right? where we call it "the fediverse" and "federated" and "decentralized" on "servers" that "speak activitypub" and use the "mastodon api" for the "client", it's just very confusing when you frame it as open source tech specifications when it should be treated instead with analogies and metaphors, which is how the early days of personal widespread computing got their way with letting people understand how the underlying tech works: the wallpaper, the files, the desktop, the recycle bin... all of these are analogs for real life objects
@nelson @HolosSocial I don't disagree here with any particular point, but I again believe that the burden is on system designers, not users.
