> Also, the most popular XMPP clients (such as Conversations and ChatSecure) have OMEMO built-in and use it by default. So I think for most users, privacy is indeed the default with XMPP.

These are mobile OS only based clients Conversations for Android only , Chatsecure for IOS only , what about Desktop? nothing active available with builtin encryption.

So lets say secure chatting over insecure operating systems (insecure endings)

> We are of course happy to receive merge requests if you believe the wording could be clarified. I'm not sure exactly what wording you would find suitable, which is why I suggest submitting a merge request, so I know what would be satisfactory. You can do so here if you like (or by email to me if you prefer)

sure i will look into what i can improve and email it to you

> If you have any particular tips for the easiest/fastest ways to do that, let me know.

Tips are not easy since we are dealing with sysadmin stuff, this is depend on your server side what are you using and how are you connecting things...etc.

If you want sysadmin (in case needed) which i recommend check this one:

https://mig5.net/

> Also, if there are more than just .onion and .i2p that you think we should add, please send those too.

No only those are recommended for privacy/anonymity protocols. others like:

GNUnet: worth it but far in the future currently not for users or normal usage.

Freenet: Very low userspace and questionable security due to the fact its distributed storage (like downloading jmp website into my local machine in order to view it..).

Zeronet: not anonymous by itself and relies on Tor for its anonymity


ThX again :)


Denver Gingerich:
On Fri, Apr 24, 2020 at 10:28:03AM +0000, bo0od wrote:
nice idea but on the same has some issues/questions:

Happy to answer them, including others' as well.

- JMP mention "Jabber is long-standing, widely-used, and privacy-focused."
WHAAA!! , xmpp/jabber doesnt has any privacy within it. Thats why we use
either OTR,OMEMO,PGP to encrypt messages and all of the clients available
today dont use these encryption as built-in but instead as plug-in (except
CoyIM which is dead project atm) and thats bring all of the problems of
plug-ins issues like not functioning or disabled due to client upgrade
...etc (i can give examples if you like). why xmpp not secure? because xmpp
made in a time of no security in mind times similar to IRC and other
protocols.

The specific line you mentioned was offered by a community member as part of 
their merge request:

https://gitlab.com/ossguy/jmp-register/merge_requests/1/diffs

I agree that XMPP on its own does not have E2EE built in.  However, XMPP 
clients and servers today all do encryption between client and server, and 
between servers.  So it is at least better than IRC and many other chat 
protocols in that regard.

Also, the most popular XMPP clients (such as Conversations and ChatSecure) have 
OMEMO built-in and use it by default.  So I think for most users, privacy is 
indeed the default with XMPP.

We are of course happy to receive merge requests if you believe the wording 
could be clarified.  I'm not sure exactly what wording you would find suitable, 
which is why I suggest submitting a merge request, so I know what would be 
satisfactory.  You can do so here if you like (or by email to me if you prefer):

https://gitlab.com/ossguy/jmp-register/merge_requests

- It needs a phone application? well i want to use a virtual phone number
because i dont wanna have a cell phone or phone number at the first place.
Why would i use another phone number while i own one? So better support
Desktop application for GNU/Linux and BSD ...

While we do provide familiar buttons to people on https://jmp.chat/ for installing mobile 
applications, the text above the buttons says "Get a Jabber client" with a link 
to https://jmp.chat/#jabber where other clients (including desktop clients such as Gajim) 
are described.  Again, we are happy to receive merge requests for this if you think it's 
unclear.

- Mirror your website to Onion Hidden Services or I2P Eepsite (as you wish)
for better privacy/security connection

Thanks very much for the suggestion.  We have been looking at adding a .onion 
address for our site and hope to do so in the future.  If you have any 
particular tips for the easiest/fastest ways to do that, let me know.  Also, if 
there are more than just .onion and .i2p that you think we should add, please 
send those too.

- I assume your service available worldwide regardless from where the user
is living, but he will get one of two countries numbers either US or Canada
right? or he should be living in those countries as well?

Yes, the service is available worldwide.  You don't need to live in any 
particular country in order to use JMP (we don't know or care where JMP users 
live, and never ask for this info).

All JMP numbers can send and receive text messages with any other number in the 
world (i.e. international texting is fully supported).

- JMP twitter not active since 2 years https://nitter.net/JMP_chat (just
saying...)

We have a pretty small team so we aren't always able to keep our secondary 
communication methods updated at all times.  Our email notification list at 
https://soprani.ca/cgi-bin/mailman/listinfo/jmp-news receives updates more 
regularly.

- (unrelated to product JMP but) your own website blocking Tor users: (just
worries me..)

Indeed, I am aware of this issue with https://ossguy.com/ and hope to fix it 
soon.  The change that caused Tor users to be blocked was implemented about 13 
years ago, when I installed the Bad Behavior plugin to cut down on comment 
spam.  I intend to turn off comments and then remove this plugin, though I'm 
happy to hear about other potential solutions as well.

ThX!

Thanks for your comments and suggestions!

Denver
https://jmp.chat/


--
Liberationtech is public & archives are searchable from any major commercial 
search engine. Violations of list guidelines will get you moderated: 
https://lists.ghserv.net/mailman/listinfo/lt. Unsubscribe, change to digest mode, 
or change password by emailing [email protected].

Reply via email to