@Visurox Didn't work for me (wrong secret), but I like the idea.
I was thinking about a variant of this, but I am somewhat concerned about abuse of such a service. Being 1kB you aren't going to get much in the way of image media, which is a major concern. Objectionable text I care less for. The concern I have is malicious JS (but I couldn't see how you handle this).
A few things you would definitely need:
1. The ability to handle takedowns (i.e. somebody adds doxxing information, or uses it to launch some attack script).
2. The ability to edit content. My solution to this was that a key would be generated and this could be used to edit.
3. Some protection against creation abuse. You better believe somebody would create 1 billion 1kB pages, just because they can. I would maybe have it so that the user puts in an email and a page edit code is sent to that email address after some artificial delay. It's not fool-proof but might slow them down. Maybe you also do some additional checks, like keywords, entropy, etc.
Anyway, all of these problems are precisely why I never decided to go through with this.
Another idea was to provide an ultra-minimal VM web server, where you run some lightweight byte code to process requests. Maybe there are some exciting possibilities with this, but similar concerns are still there.
I was thinking about a variant of this, but I am somewhat concerned about abuse of such a service. Being 1kB you aren't going to get much in the way of image media, which is a major concern. Objectionable text I care less for. The concern I have is malicious JS (but I couldn't see how you handle this).
A few things you would definitely need:
1. The ability to handle takedowns (i.e. somebody adds doxxing information, or uses it to launch some attack script).
2. The ability to edit content. My solution to this was that a key would be generated and this could be used to edit.
3. Some protection against creation abuse. You better believe somebody would create 1 billion 1kB pages, just because they can. I would maybe have it so that the user puts in an email and a page edit code is sent to that email address after some artificial delay. It's not fool-proof but might slow them down. Maybe you also do some additional checks, like keywords, entropy, etc.
Anyway, all of these problems are precisely why I never decided to go through with this.
Another idea was to provide an ultra-minimal VM web server, where you run some lightweight byte code to process requests. Maybe there are some exciting possibilities with this, but similar concerns are still there.