vinney on Nostr: Every user should host their own static content. Setting up such a service provider ...
Every user should host their own static content.
Setting up such a service provider should be single-click easy (no harder than signing in to nostr), and either free (if you do it on your own metal) or requiring of whatever minimal monthly cost the cloud provider of your choice charges.
Whether you choose local or remote, redundancy (backups) should be just as easy to opt-into (again, free if you provide the compute/disk, fee if someone else is providing it).
Not only does that completely remove the “but who’s gonna provide this and how?!” problem, but it also removes the content moderation problem. if users are hosting their own files, the liability stays with them.
Published at
2024-06-25 04:13:02Event JSON
{
"id": "e0f9fcd2522567f55fec5dfaa771c2da90eeee3415ffa4dd44b0c32c1913e3ca",
"pubkey": "2efaa715bbb46dd5be6b7da8d7700266d11674b913b8178addb5c2e63d987331",
"created_at": 1719281582,
"kind": 1,
"tags": [],
"content": "Every user should host their own static content.\n\nSetting up such a service provider should be single-click easy (no harder than signing in to nostr), and either free (if you do it on your own metal) or requiring of whatever minimal monthly cost the cloud provider of your choice charges.\n\nWhether you choose local or remote, redundancy (backups) should be just as easy to opt-into (again, free if you provide the compute/disk, fee if someone else is providing it).\n\nNot only does that completely remove the “but who’s gonna provide this and how?!” problem, but it also removes the content moderation problem. if users are hosting their own files, the liability stays with them.",
"sig": "bd42eb1dd83a49cff6c73f664d5f8935a50aa51017cc9c38bbb1ac35a09e6e666cf8bf31b01cc142ed5ca2c693fea490cf4d0082bdd89dee7624811dc84e9d6b"
}