add draft of safety post
This commit is contained in:
idk
135
i2p2www/blog/2022/09/24/i2p-safety-reminder.draft.rst
Normal file
135
i2p2www/blog/2022/09/24/i2p-safety-reminder.draft.rst
Normal file
@ -0,0 +1,135 @@
|
||||
{% trans -%}
|
||||
==================================
|
||||
A Reminder to be Safe as I2P Grows
|
||||
==================================
|
||||
{%- endtrans %}
|
||||
.. meta::
|
||||
:author: idk
|
||||
:date: 2022-09-24
|
||||
:category: general
|
||||
:excerpt: {% trans %}{% endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
A Reminder to be Safe as I2P Grows
|
||||
{%- endtrans %}
|
||||
==================================
|
||||
|
||||
{% trans -%}
|
||||
It is an an exciting time for The Invisible Internet Project (I2P). We
|
||||
are completing our migration to modern cryptography across all of our
|
||||
transports, ( Java and C++), and we have recently gained a high-capacity
|
||||
and professional outproxy service, and there are more applications
|
||||
integrating I2P based functionality than ever. The network is poised to
|
||||
grow, so now is a good time to remind everyone to be smart and be safe
|
||||
when obtaining I2P and I2P-related software. We welcome new
|
||||
applications, implementations, and forks with new ideas, and the power
|
||||
of the network comes from its openness to participation by all I2P
|
||||
users. In fact, we don’t like to call you users, we like to use the word
|
||||
“Participants” because each of you helps the network, in your own way by
|
||||
contributing content, developing applications, or simply routing traffic
|
||||
and helping other participants find peers.
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
You are the network, and we want you to be safe.
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
We have become aware of attempts to impersonate I2P’s presence on the
|
||||
web and social media. To avoid offering momentum to these campaigns, we
|
||||
will not mention the actors affiliated with them, However, in order to
|
||||
help you recognize these campaigns should you encounter them in the
|
||||
wild, we are documenting their tactics:
|
||||
{%- endtrans %}
|
||||
|
||||
- Copying text directly from the I2P Web Site without acknowledging our
|
||||
licence requirements in a way that may suggest endorsement.
|
||||
- Involvement or promotion of an Intial Coin Offering, or ICO
|
||||
- Crypto-Scam like language
|
||||
- Graphics that have nothing to do with the textual content
|
||||
- Click-farming behavior, sites that appear to have content but which
|
||||
instead link to other sites
|
||||
- Attempts to get the user to register for non-I2P chat servers. We
|
||||
come to you or you come to us, we will not ask you to meet us at a
|
||||
third-party service unless you already use it(Note that this is not
|
||||
always true for other forks and projects, but it is true of
|
||||
geti2p.net).
|
||||
- The use of bot networks to amplify the message on social media.
|
||||
I2P(geti2p.net) does not use bots to spread the message.
|
||||
|
||||
{% trans -%}
|
||||
These campaigns have had the side-effect of “shadow-banning” some
|
||||
legitimate I2P-related discussion on Twitter and possibly other social
|
||||
media.
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}Our Sites{%- endtrans %}
|
||||
---------
|
||||
|
||||
{% trans -%}
|
||||
We have official sites where people may obtain the I2P software safely:
|
||||
{%- endtrans %}
|
||||
|
||||
- `Official Website - i2p.net - TLS Fingerprint(SHA256) -
|
||||
5B:09:29:D9:26:64:7D:0E:33:B6:4A:9D:6F:58:FA:5E:24:EF:18:81:21:A9:A9:4F:8B:D2:CE:D8:74:91:60:8B <https://i2p.net>`__
|
||||
- `Official Website - geti2p.net - TLS Fingerprint(SHA256) -
|
||||
5B:09:29:D9:26:64:7D:0E:33:B6:4A:9D:6F:58:FA:5E:24:EF:18:81:21:A9:A9:4F:8B:D2:CE:D8:74:91:60:8B <https://geti2p.net>`__
|
||||
- `Official Gitlab - i2pgit.org - TLS Fingerprint(SHA256) -
|
||||
0E:90:B8:61:AA:38:AB:4A:A4:F3:54:07:AC:8B:B6:FF:03:3D:DC:18:31:BD:BA:EA:4C:A9:73:28:22:CB:97:30 <https://i2pgit.org>`__
|
||||
- `Official Debian Repository - deb.i2p2.de - TLS
|
||||
Fingerprint(SHA256) -
|
||||
17:42:0B:AB:B6:4F:24:51:5E:BC:AD:10:44:9E:2C:C9:37:BB:28:89:74:62:6B:0A:9F:23:4C:5E:A5:EA:64:91 <https://deb.i2p2.de>`__
|
||||
- `Official Debian Repository - deb.i2p2.no - TLS
|
||||
Fingerprint(SHA256) -
|
||||
EC:43:E8:DC:29:8E:BB:78:B9:88:70:ED:21:1A:8E:AD:FA:8D:6F:5E:D9:56:54:89:9F:7B:30:58:1E:03:02:CE <https://deb.i2p2.no>`__
|
||||
- `Official Forums - i2pforum.net - TLS Fingerprint(SHA256) -
|
||||
7B:1E:B6:5D:C7:5A:DE:32:E6:08:DB:8E:3C:4C:DB:5F:67:DB:13:A3:C8:1F:F9:26:53:C9:49:94:8E:CD:90:D1 <https://i2pforum.net>`__
|
||||
|
||||
{% trans -%}Invisible Internet Project Forums, Blogs and Social Media{%- endtrans %}
|
||||
---------------------------------------------------------
|
||||
|
||||
{% trans -%}Hosted by the project{%- endtrans %}
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
- `I2P Forums <https://i2pforum.net>`__ and it’s `I2P
|
||||
Mirror <https://i2pforum.i2p>`__
|
||||
- irc: `#i2p-dev` on Irc2P(`127.0.0.1:6668` in a standard I2P
|
||||
installation)
|
||||
|
||||
{% trans -%}Hosted by Others{%- endtrans %}
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
{% trans -%}
|
||||
These services are hosted by third-parties, sometimes corporations,
|
||||
where we participate in order to provide a social media outreach
|
||||
presence to I2P users who choose to participate in them. We will never
|
||||
ask you to participate in these unless you already have an account with
|
||||
them, prior to interacting with us.
|
||||
{%- endtrans %}
|
||||
|
||||
- `Launchpad : https://launchpad.net/i2p <https://launchpad.net/i2p>`__
|
||||
- `Twitter : https://twitter.com/GetI2P <https://twitter.com/GetI2P>`__
|
||||
- `Reddit :
|
||||
https://www.reddit.com/r/i2p/ <https://www.reddit.com/r/i2p/>`__
|
||||
- `Mastodon:
|
||||
https://mastodon.social/@i2p <https://mastodon.social/@i2p>`__
|
||||
- `Medium: https://i2p.medium.com/ <https://i2p.medium.com/>`__
|
||||
|
||||
{% trans -%}Forks, Apps, and Third-Party Implementations are Not Evil.{%- endtrans %}
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
{% trans -%}
|
||||
This post attempts to provide ways of vetting the source for obtaining
|
||||
the Java I2P package represented by the source code contained in
|
||||
https://i2pgit.org/i2p-hackers/i2p.i2p and
|
||||
https://github.com/i2p/i2p.i2p, and which is available for download from
|
||||
the web site https://geti2p.net/en/download. It is not intended to pass
|
||||
judgement on third-party forks, downstream projects, embedders,
|
||||
packagers, people experimenting in laboratories, or people who just
|
||||
disagree with us. You are all valued members of our community who are
|
||||
trying to protect, and not compromise, the privacy of others. Since we
|
||||
are aware of attempts to impersonate I2P project community members, you
|
||||
may wish to review the download, verification, and installation
|
||||
procedures which you recommend to your users in order to document your
|
||||
official sources and known mirrors.
|
||||
{%- endtrans %}
|
||||
Reference in New Issue
Block a user