Commit Graph

2432 Commits

Author SHA1 Message Date
Anthony Laibe 97a99d6254
fix: get balance with multiple chain (#2689) 2022-05-26 06:44:29 -04:00
Sale Djenic 78cba969cc notifications settings end points added and `notification_settings` table 2022-05-26 11:49:08 +02:00
Anthony Laibe 7227ae1c8e
fix: merge node config allows overide (#2664) 2022-05-24 12:57:45 +02:00
Richard Ramos 3e2ce20f0e
fix: ping dns4 multiaddresses (#2678) 2022-05-19 10:23:25 -04:00
Vitaliy Vlasov 011238b1d1 Wallet sync 2022-05-18 15:25:20 +03:00
Khushboo-dev-cpp 15e5584ed2
feat: Add hasActivity param to derived addresses (#2663)
Added functionality to find target address when 6th param in path is added
for ex: "m'/44'/60'/0'/0/500" reperents the Address at the 500th index

Added a api to get the Address derived from a private key
2022-05-18 13:31:45 +02:00
Pascal Precht 714c03c635 feat: introduce `CommunityAdminSettings` in `CommunityDescription`
This allows to store community admin settings that are meant to be propagated
to community members (as opposed to the already existing
`CommunitySettings` which are considered local to every account).

The first setting introduced as part of this commit is one that enables
community admins to configure whether or not members of the community
are allowed to pin messages in community channels.

Prior to this commit, this was not restricted at all on the protocol
level and only enforced by clients via UI (e.g. members don't see an
option to pin messages, although they could).

This config setting now ensures that:

1. If turned off, members cannot send a pin message
2. If turned off, pin messages from members are not handled/processed

This is needed by https://github.com/status-im/status-desktop/issues/5662
2022-05-18 09:58:11 +02:00
hesterbruikman a506bea6e5
Add user-facing explainer metrics (#2211)
* Add user-facing explainer

Added a user-facing explainer at the top of the doc as we link to this file from the UI.

Moved all content that was already in the doc to below the divider with the heading 'How it works'

* Update _docs/app-metrics.md

Co-authored-by: Samuel Hawksby-Robinson <samuel@samyoul.com>

* Update _docs/app-metrics.md

Co-authored-by: Samuel Hawksby-Robinson <samuel@samyoul.com>

* Update _docs/app-metrics.md

Co-authored-by: Samuel Hawksby-Robinson <samuel@samyoul.com>

* More text edits based on comments

Session key > Batch ID
Regular Chat key > Chat key

* Remove spaces

* Update app-metrics.md

- Remove 'anonymous' claim
- Correct that we believe the data cannot be linked back to you

* Add criteria to include data in validator rules

* Update app-metrics.md

* Replace anonymous from intro

Removing anonymous reference as discussed on Discord. 'Anonymous' is a claim we logically can't make in spite of best effort and current insights; we are not delivering proof. In addition there is the threat model of a phone ending in the wrong hands with the collected data, albeit temporarily stored locally, falling in the wrong hands.

We do want to communicate that the approach is "as privacy preserving as we could possibly make it without it being useless"

anonymous > privacy-preserving
over Waku > over Status' peer-to-peer network (Waku)

* Update app-metrics.md

- Add warning at top
- Update text at the bottom of 'what will never be shared'
- Remove 'Time since last data message sent'
- Changed 'Time since last session' to 'Time since last batch sent' @shivekkhurana can you confirm this is accurate?

* Update app-metrics.md

Replace instance of 'anonymous' in `How it works` with 'end-to-end encrypted'

* Update app-metrics.md

Added: "Status will never use these data for profit."

* Edit to Transmission and deletion

Added that data is deleted locally if not transmitted after 7 days

@Samyoul can you take a look to see if there are more details to add to this section?

* Update app-metrics.md

Remove privacy-preserving as claim in intro and end-to-end encryption to reduce perception of privacy

* Added info banner

Added info note to explicitly state that usage data service is not included in release or nightly builds

* Added links to related PRs

These PRs include a lot of additional information that will be useful for a future dev, also probably me too.

Co-authored-by: Samuel Hawksby-Robinson <samuel@samyoul.com>
2022-05-17 12:55:53 +02:00
Anthony Laibe 997708bc82 fix: flakey test with order of chats 2022-05-13 16:17:24 +02:00
Richard Ramos 2be7e53a89 fix: community was not updated when creating general chat 2022-05-13 16:17:24 +02:00
Sale Djenic b4fd62df58 tests update 2022-05-13 16:17:24 +02:00
Sale Djenic 4018e4334b Added mixed case address to the `Account` struct 2022-05-13 16:17:24 +02:00
Anthony Laibe cf8941c1d8
fix: delete account sync keystore (#2652) 2022-05-12 13:06:58 +02:00
Audrius Molis a244d77657 Enable currency settings and sticker pack synchronization 2022-05-11 16:59:12 +03:00
Andrea Maria Piana 4d15ae8a85 Upgrade to go 1.18 2022-05-11 12:39:54 +01:00
Jakub Sokołowski 57e5fd66fa ci: pin builds to hosts with specific Go version
Otherwise Go version upgrades are a pain due to randomly hitting a host
with newer version of Go compiler.

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2022-05-11 12:25:35 +02:00
Anthony Laibe 6b9f9a896a
feat: create General channel with community creation (#2662) 2022-05-10 15:25:08 +02:00
Pascal Precht d884749ebf Update version number 2022-05-10 11:27:31 +02:00
Pascal Precht d11290ef4a fix: only dispatch magnetlink when owner of community 2022-05-10 11:27:31 +02:00
Pascal Precht 43d6305157 Handle history archive magnetlink messages
This introduces the ability for status notes to handle community
history archive magnetlinks. To make this work, a few things are needed:

1. A new database table has been introduced to store message archive
   hashes. This is necessary so status nodes can determine whether or
   not they need to download a certain archive
2. The messenger's `handleRetrievedMessages()` has been exteded to take
   magnetlink messages into account
3. New APIs were added to download torrent data given a magnetlink and
   also to extract messages from downloaded archives, which are then
   later fed to `handleRetrievedMessages`

Closes #2568
2022-05-10 11:27:31 +02:00
Jakub Sokołowski bee9b4afd5 Makefile: check for Go compiler, suggest version
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2022-05-10 10:38:04 +02:00
Anthony Laibe e199ddbe9d
feat: get wallet api (#2619) 2022-05-10 09:48:05 +02:00
Adam Babik 017ae1e205 Update package-lock-snitch recipients 2022-05-09 17:24:16 +02:00
Richard Ramos 0048aaebcc
feat: add IPFS rate limiter for downloading stickers and use http server for retrieving stickers (#2611) 2022-05-09 09:07:57 -04:00
Anthony Laibe 2485e84bf5
fix: default derived from for status account (#2651) 2022-05-09 10:00:48 +02:00
Richard Ramos c71ccdb4e2
chore: test that login still works with 0.97.3 (#2661) 2022-05-04 10:46:49 -04:00
Pascal Precht 07c6808385 Make `GetNodeConfig` retrieve config from DB
Prior to this commit, this API returns the in memory `NodeConfig` which
might not be the latest state.
This is the case when for example clients update any `NodeConfig` and
retrieve it right afterwards via `GetNodeConfig`.
To get the latest state of `NodeConfig` it has to be fetched from DB
instead.
2022-05-04 10:25:00 +02:00
Khushboo-dev-cpp 5f92e84c19
feat: Add "alreadyCreated" field for a derived address to state if that wallet address is already used (#2644) 2022-05-03 10:14:49 +02:00
Andrea Maria Piana 640793fe85
Bump version to 0.98.5 2022-04-26 12:42:50 +01:00
Richard Ramos f66ad3d3dd fix: marshal pubkey correctly 2022-04-25 17:50:35 +04:00
Richard Ramos fe50f12ac9 fix: pubkey marshalling 2022-04-25 17:50:35 +04:00
Richard Ramos 85ba54f24f fix: remove unneeded lock 2022-04-25 14:48:14 +04:00
Roman Volosovskyi c531bf2ca1
Fix syncing of adding contact after removal 2022-04-25 11:02:49 +02:00
Pascal Precht 6ca86b6b99 Fix call to get node config 2022-04-22 12:30:46 +01:00
Richard Ramos d21b89ccc6 fix: code climate warnings 2022-04-22 11:25:33 +04:00
Richard Ramos 1e29948a3d fix: saving config after updating it with defaults 2022-04-22 11:25:33 +04:00
Richard Ramos b537ff9f02 refactor: reuse nodeconfig instead of loading it from DB 2022-04-22 11:25:33 +04:00
Vitaliy Vlasov 16197dc807 Sync profile picture 2022-04-21 19:50:31 +03:00
Roman Volosovskyi 9de4eb3c8a
Backup deleted communities 2022-04-14 18:01:07 +02:00
Richard Ramos e215e7b923 fix: change add_derived_from_accounts migration timestamp 2022-04-13 17:02:56 -04:00
Khushboo-dev-cpp b83f4a6c83
fix: Add derivation path to wallet account generation (#2618) 2022-04-13 11:15:26 +02:00
Patryk Osmaczko 5e2a33115c fix: defer functions overriding `err` return value 2022-04-13 11:04:26 +02:00
Anthony Laibe 907ba8ee5c
feat: visible token api (#2624) 2022-04-13 09:55:38 +02:00
Andrea Maria Piana 23c9618b0e Fix deserialization multiaccounts 2022-04-12 12:53:57 -04:00
Sale Djenic 4c993a8610 feat: generate images in desired size function added 2022-04-12 11:55:13 +02:00
Sale Djenic 10d0133974 fix: set only blocked flag to blocked contact for desktop app 2022-04-12 09:42:43 +02:00
Anthony Laibe 9fef24917a
fix: generation path (#2637) 2022-04-11 12:35:18 -04:00
Anthony Laibe f1cd9120c9
fix: prevent to import same account twice (#2633) 2022-04-11 11:18:28 -04:00
Pascal Precht 631907839a Enable history archive support for all non-admin communities
Previously, we've turned archive support off by default, this means,
community member nodes won't try to download torrent data when they
receive a magnetlink.

This commit ensures that communities joined in the future will have
this setting on, and also all existing communities that the node
isn't admin of will have this feature enabled.
2022-04-11 15:41:36 +02:00
Richard Ramos b0af0507b6 fix: do not export all symbols in windows 2022-04-11 13:12:19 +00:00