adding in this stupid segment for the discussion:

https://www.youtube.com/watch?v=izwwIcqOUnM

Reply to this note

Please Login to reply.

Discussion

I think right now 230 skews responsibility away from platforms. While I don’t think they should be blamed for everything there seems to be (just being pragmatic) a need for a more balanced approach to the unintended consequences to how the current 230 protects big tech at this moment in time.

if you or i were to run a relay 230 protects you and i as well.

there is a big disease called lawyer, and lawyer enables normal people that don't claim PERSONAL RESPONSIBILITY for their lives and actions, to hire lawyer, and then attempt to extract money from people that never meant them any wrong.

Great point. I don’t know the answer. I think it’s more the incentives and how tech controls/makes money via our data…and protection is the Trojan horse maybe ?

I think 230 is great. Nostr relays should also be protected by 230

agreed!

How are you doing my friend?

Oh I'm alright. Just working on sorting out various Bitcoin guides I've read over the years into a like a community helpdesk standard operating procedures repo in github.

that sounds rad. have you considered using write.as as well? a lot of people that aren't programmers get really confused by trying to read files in github. :D

No. Here's my readme

"Standard Operating Procedures for storing and using Bitcoin.

A repo created in the style of an I.T. helpdesk standard operating procedures guide for resources, guides, and methodology explainations for understanding how to properly use, store, and secure Bitcoin.

Prior to this repo, most Bitcoiners learned proper Bitcoin usage through word of mouth. Getting the right video suggested to them, getting the right social media post, or even just being on the right platform and knowing the right people. In this repo, we combine all these resources into one guide so that the Bitcoin community organizers or family computer wizards can help the people around them with maximum effectiveness.

This repo is written in markdown so that references to other files can be made easily."

I dig it. :-)

Nicely worded.

PS, I'm not gunning for you to still use write.as, but I will mention the reason I was originally attracted to running a writefreely instance was that it natively supported markdown. :D