? Editing: Post:21.body Save Delete Cancel
Content changed Sign & Publish new content


Free Culture, yay!

“But I don’t want to go among mad people," Alice remarked.
"Oh, you can’t help that," said the Cat: "we’re all mad here. I’m mad. You’re mad."
"How do you know I’m mad?" said Alice.
"You must be," said the Cat, "or you wouldn’t have come here.”

Follow in NewsfeedFollowing

Latest comments:

How to encrypt and share content

on Mar 19, 2016

encrypt with:

  @cmd "aesEncrypt", [unencryptedText], (encrypted) =>
    @log "key: ", encrypted[0]
    @log "iv: ", encrypted[1]
    @log "encrypted text: ", encrypted[2]

generate URL with key:

  url += "#iv:#{encrypted[1]}&key:#{encrypted[0]}"

make sure you get the hashes:

  init: ->
    window.onhashchange = (e) =>
    @cmd "innerLoaded", true #zeroframe will forward hash then

parse URL with key:

  routeUrl: (url, hash) ->
    hash = window.location.hash.substring(1)
    iv = ""
    if match = hash.match /iv:([^#&]*)/
      iv = match[1]
    key = ""
    if match = hash.match /key:([^#&]*)/
      key = match[1]

decrypt with:

  @cmd "aesDecrypt", [iv, encryptedText, key], (decrypted) =>
    @log "decrypted text: ", decrypted


Read more


on Mar 18, 2016

just including some stuff from other zites (0chan), though these two images are obviously not cc-by-sa

content from 0chan not accessible

content from 0chan not accessible

Read more

Now for real

on Mar 17, 2016

My blog is now really working, forgot to sign and publicsh /data/users/content.json. From now on it should be possible to like and comment stuff.

Read more


on Mar 15, 2016

We could try to create new private keys for some kind of virtual users (data/users/virt). Those keys could be stored in an encrypted file (AES) within the real users directory.

I'm working on an proof-of-concept, not sure if it will work out, I'm low on motivation.

You can give siteSign a custom private key.


Read more

Distributed Free Culture

on Mar 06, 2016

This blog now states the license without depending on web. The image is hosted directly on the blog. License is distributed via a magnet-link.

Maybe it would make more sense to set up a zite, which hosts all licenses as well as related images.

Next step would be to change ZeroTalk in a way, that it states the used license in every script file as well as in the final all.js.

see https://www.gnu.org/software/librejs/free-your-javascript#magnet-link-license

Read more


on May 31, 2015

Your zeronet blog has been successfully created!

Read more
Add new post


21 hours ago · 2 min read ·
Read more


21 hours ago · 2 min read


user_name1 day ago
This page is a snapshot of ZeroNet. Start your own ZeroNet for complete experience. Learn More