Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

RedditStorage

github.com

Post reply on HN
Print view View original

111–120 of 175 posts

Re: RedditStorage

#111

Post by tacone »

mafuyu wrote: post #106
jordigh wrote: post #98

Earlier quoted context omitted.

The problem is that the address is typically larger than the actual data you want to store.

Luckily, I know of a scheme to compress the address 100%! ;)

Oh no! I sketched up a script to gzip the chunks, hashsum them, and then find out how many collisions there are before the real occurrence starting from an approximate address in the PI digits chain, so that I could have: ($address*1e12)$hash$collisioncount

The resulting string is 10% of size of the gzipped string, at the expense of CPU. But when I read you achieved 100% compression I just deleted the script and got out to get a beer. :-(((

Re: RedditStorage

#112

Post by [deleted] »

joliv wrote: post #109
notacoward wrote: post #56

Earlier quoted context omitted.

Erasure-coded comments distributed across the huge number of abandoned Wordpress blogs and phpBB forums that are out there. Plenty of storage, pretty readily accessible, low probability that even one fragment will get deleted, and even if one does that's what the erasure coding is for. EDIT: also, Wikipedia never deletes anything. Even if your "edits" get reverted, you can still find them via the history page. Hmmm.

Wikipedia is a bit more vigilant with banning than abandoned blogs are :)

[deleted]

Re: RedditStorage

#113

Post by cmdrfred »

joliv wrote: post #109
notacoward wrote: post #56

Earlier quoted context omitted.

Erasure-coded comments distributed across the huge number of abandoned Wordpress blogs and phpBB forums that are out there. Plenty of storage, pretty readily accessible, low probability that even one fragment will get deleted, and even if one does that's what the erasure coding is for. EDIT: also, Wikipedia never deletes anything. Even if your "edits" get reverted, you can still find them via the history page. Hmmm.

Wikipedia is a bit more vigilant with banning than abandoned blogs are :)

A single user storing a reasonable amount of data though might get away with it... I know what I'm doing this weekend.

Re: RedditStorage

#114

Post by elinchrome »

huckyaus wrote: post #107
darkstar999 wrote: post #105

Earlier quoted context omitted.

The new Google Photos storage is lossy unless you pay for it. That doesn't rule out using the images in a different way though.

I thought it was only lossy if the originals you uploaded were >16MP. I tested uploading some <16MP images and redownloading them, and they didn't seem to have undergone any lossy conversion.

Did you compare a hash of the file, or did they just look the same?

Re: RedditStorage

#115

Post by Hello71 »

notacoward wrote: post #56
rndn wrote: post #4

There should be a contest: Who can find the most implausible data storage medium? (Rated according to various criteria such as ingenuity, reliability, max. data read/write rates, latency, storage size, costs…)

Erasure-coded comments distributed across the huge number of abandoned Wordpress blogs and phpBB forums that are out there. Plenty of storage, pretty readily accessible, low probability that even one fragment will get deleted, and even if one does that's what the erasure coding is for. EDIT: also, Wikipedia never deletes anything. Even if your "edits" get reverted, you can still find them via the history page. Hmmm.

no, deleted media is gone forever IIRC.

deleted pages are not visible to people with less than sysop rights (on enwp), and multiple methods are always available to deal with troublesome people, ranging from revision deletion to blocks and eventually ISP contact.

Re: RedditStorage

#116

Post by _lce0 »

SilasX wrote: post #91
cmdrfred wrote: post #45

Earlier quoted context omitted.

Every time I see an api for sending and receiving any type of file or text, I think botnet/building a secret chat system on top of it.

Every time I see a service offering some resource as "unlimited", I think of using it as a free backend.

google photos!!

encode your info as bits in the image ;)

Re: RedditStorage

#117

Post by hippich »

nissehulth wrote: post #78
hippich wrote: post #34

Earlier quoted context omitted.

actually, i personally witnessed C&C based on BBS :)

Fidonet, in some obscure distributed echomail area? :)

No, actual BBS with software running, processing uploaded files, and software running on machines calling in at night. It was proof of concept and not malicious, but rather fun exercise :) It was too long time ago, the only thing I remember now is that BBS software was ProBoard, and bot was spread via demo .exe file using fidonet echo :)

Re: RedditStorage

#118

Post by _lce0 »

alfg wrote: post #52
rndn wrote: post #4

There should be a contest: Who can find the most implausible data storage medium? (Rated according to various criteria such as ingenuity, reliability, max. data read/write rates, latency, storage size, costs…)

Something not too far off that I made a couple of years ago for fun. Stores small snippets of data in the URL. https://github.com/alfg/jot with demo.

genius!! ready for t.co and bit.ly

perfectly for small pieces of immutable data!

Re: RedditStorage

#119

Post by xanderjanz »

pimlottc wrote: post #83
elwell wrote: post #40

Earlier quoted context omitted.

Convert data to binary. Use Amazon Mechanical Turk API to create tasks for people to remember the index of each bit (the value of the task would be $0.01 for binary 0 and $0.02 for binary 1). And, for reading memory, a new task to input the index they remembered and the value they were paid.

You'd have to factor in a ton of redundancy to account for the human bits who just got bored and wandered off. Anyway, people would probably just start saving the bits on this computers after first job or two. Which would be an amusing result for being just a convoluted interface to a remote hard drive, but it's conceptually less interesting then actually using distributed human memory as a digital storage medium...

you could structure it such that the longer they sit there remembering the data, the more they get paid. When they want to leave, they enter what they remember and get paid.
Post reply on HN