Show HN: 1Kb Webspace (onekb.uber.space)
Hey guys, I wanted to introduce you my hacknight project.
It is a tribute to onekb.net which has stopped its service a few years ago. Currently it is still a beta where external resources are also possible (but not the point ;) ) to get your opinions.
When it is finished, the source code will be open source. The secret word is therefore also hackernews.
P.S.: The source code is currently 2.4Kb I'm trying to make it smaller. 1Kb would be my goal.
64 comments
[ 3.5 ms ] story [ 138 ms ] thread0: https://1kB.club
Betas ftw!
We roped off all of /.well-known/ and it is after all under a dot directory which ought to have been caught by a lot of existing software anyway, it seems like if people have things they want treated this way they ought to live in /.well-known/ too, it's not as though the registration process is onerous, you just need to write a specification for your thing.
Here’s the one for my site: https://memalign.github.io/googlefc60e159eedb4219.html
https://wgx.github.io/anypage/editor
https://mkaandorp.github.io/hdd-of-babel/
It broke 3256x880 (225 kByte) PNG image, drastically ripping it to 407x110 (3.4 kByte) JPEG image.
I do not handle people who act in such a volatile and aggressive manner well, especially if so spontaneously. I appreciate Patrick for having good sportsmanship, keeping the situation calm, not re-engaging, then publishing the exchange for everyone to see.
I recently had an exchange like this where someone blew up at me in a very toxic manner over a text-based medium, and having the messages saved certainly helped from an accountability standpoint.
Thank you again for sharing this anecdote, it was very interesting.
After then, the word will be the same as before.
Is there a list of pages people have made?
So with out src & href you can't have links, seem like a massive limitation. Was trying to a submit a personal site with external links, guess it's no use now.
Anyway, the secret word is changing and will be reset in about 15 hours. So far the beta has been quite successful though, as I've been pointed to many things that I didn't notice when I created it.
If I decide to use the whole thing with my own domain and webspace instead of uberspace (which were only for the beta test), you will find out here. At the moment it doesn't look like it will be profitable.
I suspect it's just people experimenting with how it works, what it allows or doesn't, and so on. I wouldn't focus much on the cruft.
Okay? Which words? Fuck that. I just said Hello..
But please, if you are in IT, don't mix up kb and kB. There is a x8 size factor from the bit to the byte!
[Edit: and "kilo" is a lowercase k]
> Sorry to tell you, but this is an absolutly useless comment. Even if I would say your right, is the only point an uppercase mistake. Yay. FeelGreatMan.
Someone was teaching you the difference between a kilobit and a kilobyte in notation, and you responded this way? Sheesh.
OP: I like the idea. How can we keep up with what you're doing/when it's back online? I have some code to post :)
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.
1.: Theres an email on the buttom. ;) 2.: I thought of it, but that would make everything more complicated. So, no, not for now. 3.: In the new beta is an temp secret word. Not the best captcha, but yeah, it works. And I think about a localhost entry if the user made a website before. May in mix with the edit function. If someone would spam, they will do, no matter if I save the IP or did hundred checks. Thats the net. :)
I saw this, but if it was to for some reason to get even remotely popular or abused, this would not scale.
> 2.: I thought of it, but that would make everything more complicated. So, no, not for now.
Sure, but it also allows for the right to delete content, etc. I don't think it has to be complicated.
> 3.: In the new beta is an temp secret word. Not the best captcha, but yeah, it works. And I think about a localhost entry if the user made a website before. May in mix with the edit function. If someone would spam, they will do, no matter if I save the IP or did hundred checks. Thats the net. :)
I don't think it needs to be fool-proof, just add enough resistance that it's not worth it. It is just 1kB after all, if the barrier is significant enough people just won't bother.