31–40 of 141 posts
One thing that wasn't clear in the protocol or explanation page was the favorite-of-a-favorite discovery. I'm assuming this works by including your personal favorites in your meta torrent, so when people get your new content, they also get a list of who you've favorited? Does this also mean that the meta update notification gets sent out when I favorite / de-favorite someone?
Earlier quoted context omitted.
I think it deserves it's own protocol nightweb:// . Will also make it easier for th iOS port later ;)
Using a nightweb.net http url on the other hand would allow a read-only web access to the service, increasing conversion rates ;)
One thing that wasn't clear in the protocol or explanation page was the favorite-of-a-favorite discovery. I'm assuming this works by including your personal favorites in your meta torrent, so when people get your new content, they also get a list of who you've favorited? Does this also mean that the meta update notification gets sent out when I favorite / de-favorite someone?
Yeah, your favorites are stored in your meta torrent, so it will be updated every time you add a favorite user or post.
Nice take on announce_meta, btw. I had mused over something similar (though not as well fleshed out) to the Nightweb concept but kept bumping my ahead against the notion of how to announce additional content when the bittorrent protocol ties info hashes (and magnet links) to a direct hash of the content - meaning you could never update something already announced for a specific key. And since the hashes are content based, it's not like you could say "my next content will be >".
Extending the protocol to include a new announcement method side-steps this very nicely :) Kudos.
I wonder how they're going to get around the problem of malicious collectives and Sybil attacks, given the anonymity constraint. You should be able to set up dozens of fake accounts to vouch that you're a "good" person, or that someone else is a "bad" person, use astroturf tactics to wage malicious campaigns against other parties, and basically sow havoc.
Earlier quoted context omitted.
http://nightweb.net/#type=user&userhash=fcx2ahb4vuobu7ej... That's mine ... awww feels like the beginnings of ICQ ;) But ... we can hack on it ... finally a good reason to learn Clojure.
Exactly, I've been both wanting to learn Clojure and develop for Android (but no Java thanks) for a while. So here's mine http://nightweb.net/#type=user&userhash=dtvjjjuk7eai42xx...
Earlier quoted context omitted.
Once you've bootstrapped/integrated with the network, it takes a minute or two for a new update to reach you in my testing. The initial time to bootstrap onto the network is around five minutes. The traffic consumption is pretty high, because it becomes a full peer on the I2P network. Over a month I would expect it to consume around 1GB or more. If this becomes an issue for people, I may add the ability to be a non-c…
You might want to add a status text to the service notification, displaying how far bootstrapping is.. Please make the non-contributing status the default then, or at least ask the user on installation... capped data plans are still the default in many places... :(
Can we haz a desktop or web version?
Earlier quoted context omitted.
Using a nightweb.net http url on the other hand would allow a read-only web access to the service, increasing conversion rates ;)
But it would undermine the "distributedness". Maybe Nightweb could serve a website on the device itself and one could use pagekite or a dynamic dns to serve it.
The third party would be running their own Nightweb client, then visitors to the website would trigger content downloads on the client, rendered out as a webpage.
This would provide the "public view" without sacrificing the decentralized nature.
Earlier quoted context omitted.
Using a nightweb.net http url on the other hand would allow a read-only web access to the service, increasing conversion rates ;)
But it would undermine the "distributedness". Maybe Nightweb could serve a website on the device itself and one could use pagekite or a dynamic dns to serve it.
I think it would provide a window into the social network, kind of "Oscar is using this, join him now by downloading the app!"
The implication I see is privacy of people clicking a user link, but the problem already exists now.