Recommendation | Status.im #1837

New Issue

jonah · 2020-04-18T05:46:46Z

jonah commented

2020-04-18 05:46:46 +00:00

Basic Information

Name: Status.im
Category: Real Time Communication > Federated IM
URL: https://status.im/

Description

I'm opening this issue to keep track of Status as far as potentially making it a recommended service. Status has some issues that would prevent me from recommending it for general use, but as they are resolved we can consider recommending them. And as we test if we discover more issues we can add them here.

Blocked: We cannot recommend it at this time because [edit list as needed]:

Push notifications are not implemented https://github.com/status-im/status-react/issues/10363

Notes

We did discuss removing Status in https://github.com/privacytoolsIO/privacytools.io/issues/1661, but I believe they have removed their dependencies on Google Play and have launched on F-Droid recently, indicating their app is more stable (also as indicated by their 1.0 launch).

## Basic Information **Name:** Status.im **Category:** Real Time Communication > Federated IM **URL:** https://status.im/ ## Description I'm opening this issue to **keep track** of Status as far as potentially making it a recommended service. Status has some issues that would prevent me from recommending it for general use, but as they are resolved we can consider recommending them. And as we test if we discover more issues we can add them here. **Blocked**: We cannot recommend it at this time because [edit list as needed]: 1. Push notifications are not implemented https://github.com/status-im/status-react/issues/10363 ## Notes We did discuss removing Status in https://github.com/privacytoolsIO/privacytools.io/issues/1661, but I believe they have removed their dependencies on Google Play and have launched on F-Droid recently, indicating their app is more stable (also as indicated by their 1.0 launch).

cyanlemons commented

2020-09-30 21:05:48 +00:00

(Migrated from github.com)

Hey @jonaharagon as of today, Status V1.7 is out with iOS notifications. The issue you've referenced has been closed.

As for the category of the recommendation goes, I believe it would likely fit the "P2P" category more than the "Federated" one. Status' procotol is just a fork of Ethereum's Whisper protocol. You don't really need to trust any specific node, but you need to put some trust into the server administrators of a federated server, i.e. the matrix.org homeserver. "Federated servers generally require trusting your server's administrator" wouldn't apply to Status.

Of course, the current list of advantages/disadvantages for the "P2P" category don't match Status either. For instance, the "reduced feature set" isn't really applicable, and IPs aren't leaked to contacts, only nodes, who don't actually know who you are talking to. I suppose Status is just the P2P architecture without the downsides ;)

Hey @jonaharagon as of today, [Status V1.7](https://our.status.im/v1-7-release-ios-notifications-mentions-nicknames/) is out with iOS notifications. The issue you've referenced has been closed. As for the category of the recommendation goes, I believe it would likely fit the "P2P" category more than the "Federated" one. Status' procotol is just a fork of Ethereum's Whisper protocol. You don't really need to trust any specific node, but you need to put some trust into the server administrators of a federated server, i.e. the matrix.org homeserver. "Federated servers generally require trusting your server's administrator" wouldn't apply to Status. Of course, the current list of advantages/disadvantages for the "P2P" category don't match Status either. For instance, the "reduced feature set" isn't really applicable, and IPs aren't leaked to contacts, only nodes, who don't actually know who you are talking to. I suppose Status is just the P2P architecture without the downsides ;)

👍 1

dngray commented

2020-11-20 08:24:34 +00:00

(Migrated from github.com)

I also noticed you're approaching completion of https://github.com/status-im/status-react/issues/8512

We should also look at this in the description https://our.status.im/status-mobile-app-security-audit-complete-ahead-of-v1-launch/

Of course, the current list of advantages/disadvantages for the "P2P" category don't match Status either. For instance, the "reduced feature set" isn't really applicable, and IPs aren't leaked to contacts, only nodes, who don't actually know who you are talking to. I suppose Status is just the P2P architecture without the downsides ;)

I'm thinking this actually has a similar model to Session, in that it is more of a "distributed" model, than a P2P one.

I also noticed you're approaching completion of https://github.com/status-im/status-react/issues/8512 We should also look at this in the description https://our.status.im/status-mobile-app-security-audit-complete-ahead-of-v1-launch/ > Of course, the current list of advantages/disadvantages for the "P2P" category don't match Status either. For instance, the "reduced feature set" isn't really applicable, and IPs aren't leaked to contacts, only nodes, who don't actually know who you are talking to. I suppose Status is just the P2P architecture without the downsides ;) I'm thinking this actually has a similar model to Session, in that it is more of a "distributed" model, than a P2P one.

This repo is archived. You cannot comment on issues.