ZeroNet Blogs

Static ZeroNet blogs mirror

Recently, ZeroNet had implemented a security improvement: cross-site blocking. Basically, sites now can't do file requests to other sites. Isn't this that Kaffiene and other search engines does? Yes. They can have problems with the new ZeroNet update? Sure.

@Kaffie said here: Already not a fan of the new ZeroNet updates. Completely kills some Kaffiene features.

@Kaffie commented:

**@Musickiller**: There's more strict cross-origin blocking, which kills a method I use to fetch files from the same+other sites. So here's a list of things I worked on that have broke because of this new update:

  • ZeroWiki support on Kaffiene
  • Other site indexes on Kaffiene
  • Every index besides basic searching on Kaffiene (though local indexes will come back soon)
  • ZeroMovie's frame escape
  • [http://zero/](http://zero/) protocol testing on Kaffie.bit

Luckily, due to an issue submitted [here](https://github.com/April93/Kaffiene/issues/20) I went ahead and fixed it for the main Kaffiene search. So at least it's not _complete_ disaster. But I've got a lot of work put on my plate now. And some features (ZeroWiki info boxes, for instance) might not come back.

@jro commented: Yah. Having "big" problems here with new rules for optional files patterns ([https://github.com/HelloZeroNet/ZeroNet/issues/989](https://github.com/HelloZeroNet/ZeroNet/issues/989)). 2 sites down here :-( Do not like updates that "destroys" old zites :-( Can be fixed but extra work

@Peeper (@Plasmmer) commented:

**@jro**: "Do not like updates that "destroys" old zites". Security improvements are welcome, also the updates that are for the future, so the old sites needs to be updated. But about the archiving/nostalgy, ZeroNet needs a GIT/blockchain system like IPFS have. About the cross-origin blocking, its a problem, since ZeroNet needs to be the Internet we know + better (security/privacy).

Why not simple use a API/wrapper/sandbox for the cross-site requests instead of blocking it? Following this logic, Windows would block apps instead of creating antivirus. Its sadly funny. Also I heard that Nofish plans to block javascript in future. I don't know how this will be done.
@Kaffie: I'm very sad about this, since the ZeroWiki cards was my suggestion as @Plasmmer: and I plan to read infos about hubs from Peeper.

As seen, ZeroNet's developers are facing problems with his sites that uses advanced features, in that exact case, the file access of other sites.

The developers are trying to circunvent this issue. In another post, @Kaffie said here:

'Fixed' Kaffiene after the disastrous result of cross-site requests being blocked. Had to remove ZeroName, CensoredSearch, and ZeroWiki stuff. Hopefully there'll be a way to access other sites' content in the future. Of course, changing your browser to ignore CORS will bring back the ZeroWiki cards. You can do that in chrome by launching with --args --disable-web-security --user-data-dir

What do you think? Is ZeroNet right or there can be another way to improve security without making ZeroNet worst than surface-web/clearnet? Don't forgot to comment.

Source: Peeper.

Kaffiene is now open-source

- Posted in Zero News by with comments

The leading search engine Kaffiene - developed by Kaffie - received suggestions to be open-source from Plasmmer.

"I try to contact you by email, but isn't working. I have some nice ideas for Kaffiene. Do you have a GitHub page for it?" - said Plasmmer.

"No github just yet. And yes, I understand a reworked database would be nice. As I mentioned, my dev work has kinda grinded to a halt and I'm not sure when I'll be able to resume. I have some personal issues and I'm not sure how long it'll take me to work through them. Sorry >_<" - replied Kaffie.

"If you open it in GitHub the work can be less slow with help of community." -replied Plasmmer.

This conversation was in April first, and can be found here.

In April 07, Plasmmer posted:

"@Kaffie: Why do you can't reply emails on ZeroMail?" - said Plasmmer.

"Lazy, mostly. I hardly ever check it, and when I do I just put off responding. Sorry. I'm kinda shitty like that." - replied Kaffie.

"Why do not create a GitHub repo for Kaffiene? The development will grow, and we can suggest indexing with issues/pull requests." - replied Plasmmer.

"I believe I answered that one already ;). Like the previous answer, mostly it's just because I haven't gotten around to it. I really don't have an answer besides that. That's literally the entire reason you haven't seen much of my development lately. I'd rather not go into the personal details of my life, but I've got some issues I need to work through before I can resume ZN development. Any sort of dev question almost certainly has the same answer; to save you some time. I haven't done much dev work in general, off and on ZN. And likely before that I need to get my actual income and living situations fixed. Github is honestly on the to-do, but not for a while. The original plan was to get Kaffiene more or less automated and then move the code to github. But neither has happened yet." - replied Kaffie.

Then, Plasmmer forked the Kaffiene search engine, modified the branding/design, added little functions, indexed more sites and turned it open-source. From this, was born the Snifferdog search engine. See the announcement.

After this idea, mkg20001 (creator of ZeroMe Beta) begins his work in the Zule search engine, also open-source.

Then - in April 23 - Kaffie posted: "Kaffiene is finally on Github. Bear with me while I deal with this. I've got no idea what I'm doing haha. https://github.com/April93/Kaffiene

And yes, my name is April." - said Kaffie.

Now we have 2 open-source Kaffiene versions: But Plasmmer seems to have interest in contribute with Kaffiene, and also to merge Snifferdog for focus in one only project.

"@Kaffie: I think Snifferdog did a enough sound. Good to see now Kaffiene is open-source. @mkg20001: How will be Zule after this announcement? I'm fine with moving Snifferdog's ideas to Kaffiene." - said Plasmmer in the Kaffie's post.

Will Kaffie accept the help of Plasmmer and mkg20001? Will mkg20001 merge Zule into Kaffiene?

"The original plan was to get Kaffiene more or less automated and then move the code to github." - quote for Kaffie.

Is Kaffiene already "more or less automated" or it is now open-source because Zule and Snifferdog? Visit the comments section.

Source: Peeper. Links: https://github.com/April93/Kaffiene, https://github.com/Plasmmer/Snifferdog, https://github.com/ZeroNerds/Zule.