/hydrus/ - Hydrus Network

Archive for bug reports, feature requests, and other discussion for the hydrus network.

Index Catalog Archive Bottom Refresh
Name
Options
Subject
Message

Max message length: 12000

files

Max file size: 32.00 MB

Total max file size: 50.00 MB

Max files: 5

Supported file types: GIF, JPG, PNG, WebM, OGG, and more

E-mail
Password

(used to delete files and posts)

Misc

Remember to follow the Rules

The backup domains are located at 8chan.se and 8chan.cc. TOR access can be found here, or you can access the TOR portal from the clearnet at Redchannit 3.0.

Uncommon Time Winter Stream

Interboard /christmas/ Event has Begun!
Come celebrate Christmas with us here


8chan.moe is a hobby project with no affiliation whatsoever to the administration of any other "8chan" site, past or present.

(735.97 KB 1200x1880 decboo.png)

Experimental decentralized booru software Anonymous 01/28/2018 (Sun) 00:12:03 Id: 8fd53e No. 7858
Hello Hydrus Network community. I am a programmer familiar with booru development. I have written my own private booru software that scrapes public websites for images much like Hyrdrus Network, it currently has 10 million files, but this isn't what I am here to talk about. I am very interested in Hydrus Network's goals of decentralized zero-authority sharing and collaborative organization of images as developments towards these goals benefits my own booru. I have recently created a proof of concept decentralized booru called "Decboo", it uses IPFS for image distribution and the Ethereum blockchain for tag distribution. Decboo is not the booru I spoke of earlier, it is an extremely basic program made only to demonstrate blockchain-based tag distribution, functionality that I hope the Hydrus Network developer(s) will integrate into the Hydrus Network software. A zip file containing Decboo's software can be downloaded here: https://ipfs.io/ipfs/QmZvYUrXFwpqCognaLm6ecSixQRuXbeXScrZKA71VRUsgE
Is a block chain for tags even a good idea? Merkle trees are fine, but it occurs to me that a stupid content tracker thing like Git-adapted-for-tags or just the typical distributed database ways will perform better than a blockchain. It's not like you want to use a large fraction of the total computation power just to confirm tags, right?
This looks interesting! I hope it goes well. I am afraid I don't know much about blockchain development, but I would like to know how it works and scales for you as you go on. I am all for connecting hydrus with other projects. If enough of my users pick up your software and ask me to put work into it, I would love to. Do you expect to make an API that hydrus could send/receive files and other data to/from?
>>7858 >the ethereum blockchain for tag distribution how the fuck did you make a cryptocurrency distribute tags for images of taiwanese tapestries?
>>7883 Most things cryptocurrency enthusiasts do with blockchains are not actually a good idea. They somehow generalize from "blockchains are the decentralized trustless cryptographically secure ledger" into "blockchains are the first decentralized thing" or "blockchains are the first ledger" or sometimes even "blockchains are the first cryptographically secure thing, satoshi nakamoto invented cryptography". Then they try to use them for things that already have long-standing solutions. Trying to get businesses or governments to store databases in centrally controlled blockchains when the only measure blockchains don't lose horribly to traditional databases on is decentralization, trying to cryptographically verify things by putting them in a blockchain instead of just using public-key encryption, etc… Blockchains make a lot of sacrifices in terms of efficiency and speed to achieve that decentralized trustless shit. (Trustless here meaning it's infeasably hard for an attacker to send a fake currency transaction to defraud people, or in this case infeasably hard to… add fake tags to the tag list?) As you mentioned, 39-year-old Merkle trees (and thus Git, which uses them) can do everything in that list except "trustless", and do it with one billionth the electricity and hardware cost. Blockchains are just not very useful for anything other than libertarian internet money. For any other task, there's a better tool (though the old tool is probably not currently as trendy or fashionable).
(647.26 KB 500x289 sensible chuckle.gif)

>>8122 >satoshi nakamoto invented cryptography
I think a blockchain is probably overkill, especially since in the long run blockchains tend to grow very large and unwieldy. The bitcoin blockchain is currently more than 100GB. While technically blockchains provide the strongest guarantee of decentralized trust, they are only necessary when you're expecting the network to be attacked by technically skilled people with lots of time and deep pockets. In practice the worst kind of attack a network like this could expect would come from particularly autistic shitposters with relatively little disposable income. Even things like the bittorrent network still function fine despite being targeted by the likes of Hollywood. Proof-of-work algorithms are a good idea though. They can be used to increase the computational cost of attacks and prevent a malicious entity from doing damage faster than a few humans can undo it. If I was designing something like this I'd require proof-of-work both for node ID generation (to prevent sybil attacks) and for any edits made to the image/tag database. Let leaf nodes query the network for free (within certain bandwidth limits), but make them generate a computationally intensive ID if they want to push any changes to it. Each node should adjust its trust in its neighbors depending on how often they agree with the consensus, blacklisting any nodes which consistently give bad responses.
>>7858 IPFS based image sharing is awesome
>>7858 Still no source code one year on… please show us more


Forms
Delete
Report
Quick Reply