BitHorde

Late yesterday, one of the final features planned for 0.2 landed in Git; Linked SourceAssets. With Linked SourceAssets, instead of uploading the asset to BitHorde, a new "-l" option to bhupload informs BitHorde of the local path of an existing file ... [More] on disk. This is great news for anyone interested in using BitHorde, while keeping assets visible in the normal filesystem for other applications. read more [Less]

Late yesterday, one of the final features planned for 0.2 landed in Git; Linked SourceAssets. With Linked SourceAssets, instead of uploading the asset to BitHorde, a new "-l" option to bhupload informs BitHorde of the local path of an existing file ... [More] on disk. This is great news for anyone interested in using BitHorde, while keeping assets visible in the normal filesystem for other applications. read more [Less]

After a great idea from our kind hosting sponsor, it is now dead-simple to quickly try out BitHorde. A demo-movie is now hosted on bithorde.org, on a BitHorde-demo-node, and the example-config distributed with BitHorde is already configured for it. ... [More] In short, download install and, provided enough bandwidth, enjoy Sintel streaming to you through BitHorde. Full instructions on the download page. read more [Less]

After a great idea from our kind hosting sponsor, it is now dead-simple to quickly try out BitHorde. A demo-movie is now hosted on bithorde.org, on a BitHorde-demo-node, and the example-config distributed with BitHorde is already configured for it. ... [More] In short, download install and, provided enough bandwidth, enjoy Sintel streaming to you through BitHorde. Full instructions on the download page. read more [Less]

Due to the massive improvements done so far in the 0.2-series, I've decided to release a preview alpha1-version. There are numerous changes, and important rewrites aimed at stability and restructuring for coming features. Some highlight include: 95 ... [More] commits since 0.1-branch. Some new features: Encryption / authentication between nodes HTTP monitor port to see open connections, asset statistics etc. Ping/heartbeat to detect stale connections. Important rewrites: read more [Less]

Due to the massive improvements done so far in the 0.2-series, I've decided to release a preview alpha1-version. There are numerous changes, and important rewrites aimed at stability and restructuring for coming features. Some highlight include: 95 ... [More] commits since 0.1-branch. Some new features: Encryption / authentication between nodes HTTP monitor port to see open connections, asset statistics etc. Ping/heartbeat to detect stale connections. Important rewrites: read more [Less]

Something significant just landed in git-master. Encryption. Yes, BitHorde now supports node-node encryption, and key-based cryptographic authentication. 4 different crypto-levels are supported at the moment; Cleartext. No encryption, just ... [More] cryptographic authentication. Fastest XOR. Not really encryption, just obfuscation, and still very fast. Insecure, but keeps nosy people away with very little performance-impact. (>10gbit encryption-rate on the Core i7used for test) read more [Less]

Something significant just landed in git-master. Encryption. Yes, BitHorde now supports node-node encryption, and key-based cryptographic authentication. 4 different crypto-levels are supported at the moment; Cleartext. No encryption, just ... [More] cryptographic authentication. Fastest XOR. Not really encryption, just obfuscation, and still very fast. Insecure, but keeps nosy people away with very little performance-impact. (>10gbit encryption-rate on the Core i7used for test) read more [Less]

Late this week, a significant bug was discovered in all versions of BitHorde. The bug, when triggered will cause data-loss. All users are strongly encouraged to update to 0.1.3, containing a fix for this. I sincerely apologize for any inconvenience this may have caused users. read more

Late this week, a significant bug was discovered in all versions of BitHorde. The bug, when triggered will cause data-loss. All users are strongly encouraged to update to 0.1.3, containing a fix for this. I sincerely apologize for any inconvenience this may have caused users. read more