• 3 Posts
  • 31 Comments
Joined 22 days ago
cake
Cake day: November 10th, 2025

help-circle

  • If I’m reading(skimming) the documentation right, it seems like anyone who can pass the challenge can download the full node and see the full record of interactions. IPFS is not a perfect privacy network, so user accounts can in theory be traced back.

    So basically as with Fedi instances it is fully on the Node host to set who can get in based on the challenge, and what is hosted there is their liability. Only difference is Plebbit allows any user to spin up a new instance/community node ad-hoc and they aren’t responsible for maintaining infrastructure beyond what is required seed the nodes they host.

    Is that right? I’m not sure but hopefully someone better in the know will correct me if not.




  • I’m ok with both, but prefer co-ops because the members get direct voting on large decisions by default, rather than a proxy vote via an appointed government worker who answers to the municipal government.

    That said, there is no reason these can’t be one and the same, the local government could fund the establishment of a regional co-op and maintain audit and some other limited authority over it.

    I also support long-distance fiber infrastructure being built and maintained by worker’s co-ops that would then get paid for service by the regional ISPs. Worker members would be highly motivated to maintain good uptime, and hiring/training members who live local to the fiber lines in remote regions would be possible with the incentive of worker ownership. Once built it is a long term maintenance and security business with steady return, perfect for a worker’s co-op that could be financed with private capital at decent ROI.




  • Prohibition leads to the propagation of means of evasion. By attempting to ban teenagers from popular means of communications they will incentivize mass adoption of “illicit means” of communications, and create another generation both familiar and comfortable with “illegal online activity” like the Napster generation. Just like Napster, this will also accidentally push youth into online platforms and channels where they are more likely to encounter content not suitable for minors and malware.

    The only “truly effective” form that this type of internet control can take is requiring a digital ID verification to establish a connection to the network at the ISP, and that is a nightmare setup we should be prepared to fight tooth and nail.














  • As a non-coder interested in self hosting and somewhat aware of cybersecurity, this is the most relevant take for me.

    An application that facilitates safe self-hosting of many different service is great, however for it to be actually safe and useful it must either be a cybersecurity service keeping up with the pace of threats (which is essentially the corporate closed source model) or from the ground up be an educational platform as much as an application. Documentation needs to not only be comprehensive, but also self-explanitory to a non-technical audience. It is not enough to state that a setting or feature exists, it must also be made clear why it should be used and what the consequences of different configurations are.

    This approach is almost never done effectively by FOSS projects unfortunately. Fortunately I think we are at the point where it is completely feasible for this type of educational approach to be fully replicable and adaptable from a creative commons source to the specific content structure of the application user manual using LLMs (local ones). The big question is, what is the trusted commons source of this information? I suppose there are MIT and other top university courses published for open use online that could serve as the source material, but it seems like there is likely a better formatted “IT User Guide Wiki” and “Cybersecurity Risk and Exploit Alert List” with frequent updates out there that I’m not aware of, perhaps the annals of various cybersecurity and IT associations?

    Anyway I’m aware this is basically calling for another big FOSS project to build a modular documentation generator, but man would it help a lot of these projects be viable for a wider audience and build a more literate public.