The size of optional files of my ZeroMe account is reaching 10 MB, and Orange hub has max_optional_file_size settings in ./data/users/content.json (For official hubs only Orange hub and Sun hub have such a setting, other hubs don't, so I guess it's an experiment for Nofish to test max_optional_file_zite feature, and Nofish created White hub by cloning another hub, but created Sun hub by cloning Orange hub), therefore I can't sign and publish my content if I post a large image with that account. I try to ask Nofish for removing that setting or adding extra permission for my account, by both ZeroMe and ZeroMail, but didn't receive reply or change for several days.. So I have to deal it by myself.
I clone a new hub, create a new profile with a different id (0ch.anonymous by 0chan.bit, because a user can't have two same ZeroID in users.json iirc, also 0chan.bit is retired in favor of Milchan.bit, so.. :3) and use the script below to copy posts with image to my new account in my own hub:
old_data = json.load(open('data-old.json'))
posts_with_image = []
for post in old_data['post']:
if 'meta' in post and post['meta'] != '{}':
posts_with_image.append(copy.copy(post))
del(post['meta'])
post['body'] += "\n\n--- ---\n[archived image](?Post/1Mf7JmunnJXvvPospsw85GoZP5ZRxMNKi5/1CC9pMzxP3CEuJLmkK1GBgGMHZdh1Zj9Fv/" + str(post['post_id']) + ") in my own hub"
new_data = json.load(open('data-new.json'))
new_data['post'] += posts_with_image
new_data['next_post_id'] += len(posts_with_image)
json.dump(old_data, open('data-old.json','w'), indent=2)
json.dump(new_data, open('data-new.json','w'), indent=2)
As you see I didn't remove my old posts, but just remove image items and add a link to the related new post. Good idea, isn't it :D
Doing this kind of thing is a bit ridiculous imho, but I have to. Because the admin/owner of Orange hub is Nofish and you probably know that the whole ZeroNet project, as well as all official zites, are almost developed and maintained by himself/only one person. So I won't complain any thing when some of my voices didn't get caught by his eyes.
Even so, I'd like to think of some better solution for solving the issue I have in this time:
Firstly, I like very much the idea of DAO (Decentralized autonomous organization), for creating an organization without any centralized administration/management (Wikipedia doesn't have a decent definition for it, I don't trust Wikipedia for infomation about this kind of things either, and too lazy to discover some good instructions, so.. sorry that no further info :P). Although ZeroNet itself doesn't have adminstration, but a zite has ownership, and the owner can modify all the data of her/his zites, including other users' data.json, aka comments, posts, etc. It may sound a little scary, but unfornutately this is how ZeroNet works. A lot better than clearnet if you agree..
Are there some methods to avoid bad things?
Yep, keep backing up your data, as a mistake or zite bug can delete all your content. If you are worried that the zite owner may change your content, you can write a bot to keep tracking if your content on the zite matches the content of your backup, we can even create a clonable zite for this purpose. With ZeroHello the zite may even provide an alert when content gets changed, but probably it's not worth for developing such a site.. For more secure conversation, a user can use ZeroMail.
And some possible solutions?
Using ZeroMe as example, you may know that your data on ZeroMe are stored in hub zite but not ZeroMe (frontend) zite itself. So just as mentioned before, a user can create and use a hub for himself. But according to the current design of ZeroMe, when you comment on a post of a user from another hub, you actually created a new data.json in that hub and are writing data there. Why design in this way? Because if the comment is stored in your own hub, and if the post owner doesn't add your hub, then s/he won't be able to view your comment ><
