Talk:I2P

Update about I2P publicity

The issues about limitations of TCP transport are by at large no longer relevant, as jrandom has updated the transport layer to utilize UDP, thus dramatically reducing the number of threads necessary to run. The article is short on information, especially technical information, and NPoV is not clearly there, however the rapid changes to I2P and its attendant software make it difficult to keep the article in sync, for which I would support that any statement about I2P would go accompanied by a version number of the program, so users could know at a glance if the recent versions of I2P suffer from a given problem, etc. --Eulen 15:33, 26 October 2005 (UTC)

I2P publicity problem

There has been some controversy over fully describing the I2P client applications here.

The controversy comes from the purported inability of the I2P network to handle high traffic loads and/or network sizes of more than ~500 routers. The limitation in network size is due to technical limitations in the TCP/IP transport, which will be fixed within a few months. The problem with high traffic loads is that programs such as BitTorrent generate lots of traffic, and this can "overwhelm" low-traffic programs such as IRC, thus making it difficult for anonymous developers to converse with the I2P community and contribute. I assume the traffic problem will be eventually fixed as well.

Many people in the I2P community- including the lead developer jrandom -- reason that if I2P is widely advertised, then large numbers of people will join the network, and it will "crash". Thus the I2P community has asked everyone to refrain from mentioning I2P in Slashdot postings, popular news sites, etc. I2P developer smeghead asks that Wikipedia hold off on its "holy knowledge crusade." He states that I2P's goal is to stay "under the radar until jrandom revamps the transport."

It's also problematic to explain the I2P applications, since some of these are alpha releases that are made available as "ongoing experiments" that change rapidly and do not have great reliability. Many of the programs currently described on the I2P page are not even functional!

I'm an I2P developer, but I don't currently see this as a big problem. I did however want to explain this controversy, so you will have some idea of why there are battles in the edit/revert history.

Apparently, there was a chat session involving Wikipedia admin silsor, Shaun MacPherson, I2P developer smeghead, and others, in which a "compromise" was made, but this conversation has not been made public. Developer smeghead alleges that User:ShaunMacPherson ignored the compromise and went ahead and published lots of I2P information on Wikipedia. --Connelly 21:17, 12 May 2005 (UTC)

Their fears should have no bearing on what we include. --Maru (talk) Contribs 17:33, 26 October 2005 (UTC)

That was two years ago, are they still afraid that it won't scale? From what is said above, it seems that the protocol was fixed. So does the developers have asked the user community not to mention the software in high publicity website reflect the current state?--87.162.59.250 (talk) 17:33, 23 January 2008 (UTC)

VPN vs Overlay Network

I came here from Hamachi entry - noticed that someone made a change saying that 'i2p is too nat-aware vpn' (or something to that extent). Also looking at I2P article tags, it is filed under 'virtual private networking' genre. Strictly speaking I2P is not VPN, it is an overlay networking framework. The difference is subtle, yet it exists. "VPN" typically refers to the system that transparently integrates with a host operating system either via use of virtual adapters or bump-in-the-stack traffic interception. I2P can potentially be used for implementing VPN, but this is not something that it supports at the moment.

PS. Don't mean to be anal :) I come from industrial VPN background and I felt that the clarification was in order. —The preceding unsigned comment was added by 24.87.213.133 (talk • contribs) .

I'm not familiar enough with these subtleties to do the edits myself, perhaps you could suggest what specific changes should be made to the article to clarify this point? Or even better, just go ahead and make the changes directly - be bold. :) Bryan 09:40, 13 January 2006 (UTC)

Lacking Features

(moved from the reverted POV from the main article, to keep the inspiration for developers)

• Shutdown option from the windows tray icon
• Plugin that configures windows to only use .i2p webpages to the proxy
• More peers (get on this everyone)
• Sleep mode (so it donates more bandwidth while at I'm at work)

What is with all the "a la"s? -anonymous user

I am pretty sure you can get the only i2p address proxying with a firefox plugin now. Anyway, it's not i2p's mission to write plugins for all browsers. --84.178.75.127 08:34, 7 September 2006 (UTC)

Version histroy

Do we want to keep some sort of version history in this article? Not noting every version of course, but the most important features that came with every new minor increment (next one would be 6.2). Adding dates to this would give a broad overview how this project moves along. --84.178.75.127 08:36, 7 September 2006 (UTC)

Technobabble

I believe the first paragraph should be cleaned of technobabble and give an overview of what I2P can do, because regular people may want to get at least some information before being turned away by a lot of words they don't understand. I have started this by adding the possible applications to the first paragraph. Maybe some stuff could be moved in the second paragraph and the anonymous / pseudonymous stuff could be worded better (however, there is no such thing as an anonymous network, this should be made clear). --84.178.75.127 08:57, 7 September 2006 (UTC)

Fair use rationale for Image:I2plogo.png

Image:I2plogo.png is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.

Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.

If there is other other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.BetacommandBot 00:17, 6 June 2007 (UTC)

Anarcho-capitalism??

I removed the link to anarcho-capitalism from "See Also", cause I can't figure out what, if anything, I2P has to do with it. Crypto-anarchism I can see (though it's a bit of a stretch), but anarcho-capitalism just seems random. Yourcelf (talk) 20:31, 6 May 2008 (UTC)

Proposed merge of .i2p

The .i2p stub can be added here, it's not really notable. Category:Pseudo-top-level domains can be preserved in a redirection from .i2p to I2P if desired. --217.184.142.28 (talk) 00:20, 31 May 2008 (UTC)