by mediocregopher on 3/13/22, 4:03 PM with 34 comments
by throwaway984393 on 3/13/22, 7:52 PM
If you want "open" public services, form a co-op or nonprofit to develop the service. Make all users 'members' who fund it. Make both the workers and users the owners. Create a public independent board to oversee it. Put any profit back into the service. The architecture will not matter.
by rapnie on 3/13/22, 6:38 PM
Also a self-hosted alternative to KeyBase is at: https://keyoxide.org (minus the chat parts).
by thayne on 3/14/22, 2:19 AM
Really? My understanding was that the client and some libraries they use are open source, but the actual server code is closed source. Although if Zoom isn't going to continue maintaining keybase, then open sourcing the server code seems like "the right thing to do" (at least morally, and probably from a PR standpoint as well). Even if they did want to continue maintaining it, it would be a good thing in my opinion, but moreso if the project will die otherwise.
by ram_rar on 3/13/22, 7:24 PM
by rgbrgb on 3/13/22, 8:58 PM
Any frameworks people like for building stuff with distributed or federated architecture? Thinking about this in relation to how one could build long-lived web services (like bandcamp [0]) that aren't owned by a single entity (or can't be sold at least).
by ganzuul on 3/13/22, 6:03 PM
Smartphones are like thin clients. If you already subscribe to bandwidth, why not compute too?
by nonrandomstring on 3/13/22, 6:33 PM
I think we should be very careful about casually using that word.