From fc07bd0d33e21d980401cc31ef466c6904ebf3ac Mon Sep 17 00:00:00 2001 From: mildrette Date: Wed, 2 Apr 2025 15:10:53 +0100 Subject: [PATCH 1/7] fixed link error --- _posts/New-Features-on-RelaySMS.md | 4 +- et --hard HEAD~3 | 64 ++++++++++++++++++++++++++++++ package.json | 3 +- 3 files changed, 68 insertions(+), 3 deletions(-) create mode 100644 et --hard HEAD~3 diff --git a/_posts/New-Features-on-RelaySMS.md b/_posts/New-Features-on-RelaySMS.md index a12bb3e..0e8f32e 100644 --- a/_posts/New-Features-on-RelaySMS.md +++ b/_posts/New-Features-on-RelaySMS.md @@ -14,7 +14,7 @@ At SMSWithoutBorders, we're constantly working to improve how users stay connect ## 📩 Replies for Bridges: Receive Responses Even Offline -One of the greatest challenges of offline communication is knowing if the recipient has responded. We introduced **(bridges)[https://blog.smswithoutborders.com/posts/Bridges]** in a previous update, which enables users to communicate without saving their accounts; but are given primary aliases which act as their default RelaySMS accounts. The new feature **Replies for Bridges**, enables users who send messages through **Bridges** to now receive replies directly via SMS. +One of the greatest challenges of offline communication is knowing if the recipient has responded. We introduced **[bridges](https://blog.smswithoutborders.com/posts/Bridges)** in a previous update, which enables users to communicate without saving their accounts; but are given primary aliases which act as their default RelaySMS accounts. The new feature **Replies for Bridges**, enables users who send messages through **Bridges** to now receive replies directly via SMS. ### Here’s how it works: @@ -38,4 +38,4 @@ We understand how crucial it is to know if your message was successfully sent, a With these updates, **RelaySMS continues ensuring users can send and receive messages even during internet shutdowns.** Stay connected, no matter what. -📢 (Try out )[https://apps.apple.com/us/app/relaysms/id6630382970] these new features today! Coming soon to Androids +📢 [Try out ](https://apps.apple.com/us/app/relaysms/id6630382970) these new features today! Coming soon to Androids diff --git a/et --hard HEAD~3 b/et --hard HEAD~3 new file mode 100644 index 0000000..9a949ab --- /dev/null +++ b/et --hard HEAD~3 @@ -0,0 +1,64 @@ +991e094 (HEAD -> develop, origin/develop) still fixing error +191c650 fix code +5a23f33 update to the develop branch +49dbfb3 Merge branch 'staging' into develop +a087356 remove text +26358c4 (origin/staging) Merge pull request #46 from smswithoutborders/develop +c8d3dbe Merge branch 'staging' into develop +304a7d6 Merge branch 'main' of github.com:smswithoutborders/SMSWithoutBorders-Blog into develop +de19cbf Merge pull request #44 from smswithoutborders/develop +2ed6c49 added the bridges feature +9faec61 Merge pull request #41 from smswithoutborders/staging +40904f7 Merge pull request #43 from smswithoutborders/develop +204813f fixed linke issues +63f25f0 Merge pull request #42 from smswithoutborders/develop +8756350 Merge branch 'staging' into develop +6b63a99 pull from main +f1e7526 Merge branch 'main' of github.com:smswithoutborders/SMSWithoutBorders-Blog into develop +723b032 Merge pull request #40 from smswithoutborders/develop +1f65c2c added the new feature on relaysms +56f8732 Merge pull request #39 from smswithoutborders/staging +97bdcf6 Merge pull request #38 from smswithoutborders/develop +eada637 Merge branch 'staging' into develop +5e07712 added blog post for relaysms desktop +3d05879 Merge pull request #37 from smswithoutborders/staging +1bcd65f Fix: Use Node.js 20 and SSH keys for deployment. +1c3a92f Merge pull request #36 from smswithoutborders/develop +afaab47 Merge branch 'staging' into develop +28b87a7 update to the new blog +7214c1f added blog post about bridges +4c4ff90 Merge branch 'main' of github.com:smswithoutborders/SMSWithoutBorders-Blog into develop +1f5694c Merge pull request #35 from smswithoutborders/develop +f6c086d Fix code formatting issues using Prettier +9ad7b40 audit blog post +1ce3abc build(ci): add run_compose for docker compose builds +cbcbad4 Remove pnpm lock file from tracking and ignore it +6a764ce Merge pull request #34 from smswithoutborders/staging +81c5ddb Merge branch 'main' into staging +7db4e25 Merge pull request #33 from smswithoutborders/develop +bc5a0fb Merge branch 'staging' into develop +3f1b134 chenged website link +30a12b3 Merge pull request #32 from smswithoutborders/staging +5b20266 Merge pull request #31 from smswithoutborders/develop +855ff60 Merge branch 'staging' into develop +ab113b6 space edit +719bba2 Merge pull request #30 from smswithoutborders/develop +acfe9ba Merge branch 'staging' into develop +0c07ff6 refactor: rename post files +03fa9b6 Merge pull request #29 from smswithoutborders/develop +f8803f0 refactor: remove draft tag from recent posts +57b4ad7 Merge branch 'develop' of https://github.com/smswithoutborders/blog into develop +08c1716 rebrand and device id blog posts +c2ed828 Merge branch 'main' into develop +bcb9b20 correction to device id post +784165b Merge pull request #26 from smswithoutborders/develop +0e75ff5 device ID blog post +d15b15d rebranding blog post +ecbbf51 Merge pull request #25 from smswithoutborders/release/vault-0.1.0 +707efba refactor: update vault-0-1-0 release note +2531f0d Merge pull request #24 from smswithoutborders/release/vault-0.1.0 +c3a6985 refactor: add source code section to vault release +ad8d1e5 release: vault-0.1.0 +1d49f22 Merge pull request #23 from smswithoutborders/staging +4e512ad Merge pull request #22 from smswithoutborders/develop +7d614da fixed image issues on reliability blog post diff --git a/package.json b/package.json index 9124bde..c5c8f01 100644 --- a/package.json +++ b/package.json @@ -45,5 +45,6 @@ "lint-staged": { "*.js,jsx,ts,tsx": "eslint --cache --fix", "*.{js,jsx,ts,tsx,json,css,md}": "prettier --cache -w" - } + }, + "packageManager": "pnpm@10.7.1+sha512.2d92c86b7928dc8284f53494fb4201f983da65f0fb4f0d40baafa5cf628fa31dae3e5968f12466f17df7e97310e30f343a648baea1b9b350685dafafffdf5808" } From 97061edea5fd4d9e09f460071d66d62a4951a8e5 Mon Sep 17 00:00:00 2001 From: Vanessa Christopher Date: Tue, 27 May 2025 15:17:33 +0100 Subject: [PATCH 2/7] new post: Local Storage for Your Access Tokens --- _posts/local-storage-for-access-token.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 _posts/local-storage-for-access-token.md diff --git a/_posts/local-storage-for-access-token.md b/_posts/local-storage-for-access-token.md new file mode 100644 index 0000000..f9acfb7 --- /dev/null +++ b/_posts/local-storage-for-access-token.md @@ -0,0 +1,21 @@ +--- +title: "Take Control of Your Privacy: Introducing Local Storage for Your Access Tokens" +excerpt: "Keeping your online account credentials safe is a tricky balance between convenience and privacy. To give you more control ..." +coverImage: "/icon.png" +date: "2025-05-27" +author: + name: "Aysha Musa" + picture: "/anon-avatar.jpeg" +ogImage: + url: "/icon.png" +--- + +Keeping your online account credentials safe is a tricky balance between convenience and privacy. To give you more control, we’ve rolled out a new feature that lets you store your access tokens (the digital keys to your online platforms) right on your phone, not on our cloud servers. + +Storing your tokens locally means reducing your reliance on our servers and minimizing the risk of your sensitive account information being exposed or compromised. This is especially valuable for users who live or work in places with limited or unreliable internet access, or for anyone who values privacy and control over their own data. +Here’s how it works: when you turn this feature on, any access tokens currently stored in the cloud are securely transferred to your device. From that moment, new tokens will be saved only on your device and never sent back to the cloud. If you decide to turn the feature off later, new tokens will once again be stored on our servers, but the ones already on your phone remain safe and encrypted. + +Due to the platform’s security policies, when Twitter tokens are stored locally, you can only send one message before you need to revoke and restore the token to send another. While this requires a bit more effort, it adds an extra layer of security for your Twitter account and aligns with best practices for handling sensitive credentials. + +This new feature reflects our ongoing commitment to strengthening privacy and security without sacrificing functionality. We want to empower you with tools that keep your communications private and your data in your hands. +Update your SMSWithoutBorders app and find the new option for store tokens on device in your settings and let us know what you think of this new feature. From 4a71a3da43e8213c57f7098fa5889613a521bcdf Mon Sep 17 00:00:00 2001 From: Vanessa Christopher Date: Tue, 27 May 2025 15:21:38 +0100 Subject: [PATCH 3/7] remove packagemanager --- package.json | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/package.json b/package.json index c5c8f01..9124bde 100644 --- a/package.json +++ b/package.json @@ -45,6 +45,5 @@ "lint-staged": { "*.js,jsx,ts,tsx": "eslint --cache --fix", "*.{js,jsx,ts,tsx,json,css,md}": "prettier --cache -w" - }, - "packageManager": "pnpm@10.7.1+sha512.2d92c86b7928dc8284f53494fb4201f983da65f0fb4f0d40baafa5cf628fa31dae3e5968f12466f17df7e97310e30f343a648baea1b9b350685dafafffdf5808" + } } From ba2933bd1dfa7a2fe8d6c56bac0bdee773b77986 Mon Sep 17 00:00:00 2001 From: mildrette Date: Thu, 5 Jun 2025 15:47:18 +0100 Subject: [PATCH 4/7] added blog post Local Storage for Your Access Tokens --- _posts/Bridges.md | 7 +----- .../Local-Storage-for-Your-Access-Tokens.md | 24 +++++++++++++++++++ 2 files changed, 25 insertions(+), 6 deletions(-) create mode 100644 _posts/Local-Storage-for-Your-Access-Tokens.md diff --git a/_posts/Bridges.md b/_posts/Bridges.md index 9fc758a..327d010 100644 --- a/_posts/Bridges.md +++ b/_posts/Bridges.md @@ -1,6 +1,6 @@ --- title: "RelaySMS Bridges" -excerpt: "SBefore now RelaySMS required online setup processes, including account creation and saving platforms. RelaySMS Bridges breaks these barriers." +excerpt: "Before now RelaySMS required online setup processes, including account creation and saving platforms. RelaySMS Bridges breaks these barriers." coverImage: "/icon.png" date: "2024-11-14" author: @@ -16,11 +16,6 @@ Before now RelaySMS required online setup processes, including account creation When the user chooses to use bridges they receive a one-time code and a special phrase via SMS to verify their identity and encrypt their messages. Bridges uses the phone number to create a temporary alias (e.g.,[123456789@relaysms.me](123456789@relaysms.me)) which will be used to send messages. - - RelaySMS Bridges prioritize security. The one-time code verifies your number, and the special phrase creates an encrypted connection for your messages. Users are required to paste the entire authentication message to ensure the process is completed successfully. Once verified, you can now send messages to your preferred online platforms, without the need for internet. This functionality empowers individuals, organizations, and communities to stay connected and informed, regardless of their internet access. Whether facing internet outages, censorship attempts, or simply needing reliable communication in remote regions, Bridges ensures your voice remains heard. diff --git a/_posts/Local-Storage-for-Your-Access-Tokens.md b/_posts/Local-Storage-for-Your-Access-Tokens.md new file mode 100644 index 0000000..4812df6 --- /dev/null +++ b/_posts/Local-Storage-for-Your-Access-Tokens.md @@ -0,0 +1,24 @@ +--- +title: "Local Storage for Your Access Tokens" +excerpt: "Storing your tokens locally means reducing your reliance on our servers and minimizing the risk of your sensitive account information being exposed." +coverImage: "/icon.png" +date: "2025-06-05" +author: + name: "Aysha Musa" + picture: "/anon-avatar.jpeg" +ogImage: + url: "/icon.png" +--- + +## Putting Your Access Tokens Where They Belong: On Your Device + +Keeping your online account credentials safe is a tricky balance between convenience and privacy. To give you more control, we’ve rolled out a new feature that lets you store your access tokens (the digital keys to your online platforms) right on your phone, not on the RelaySMS servers. + +Storing your tokens locally means reducing your reliance on our servers and minimizing the risk of your sensitive account information being exposed. This is especially valuable for users who value privacy and control over their data. + +**Here’s how it works:** when you turn this feature on, any access tokens currently stored in the cloud are securely transferred to your device. From that moment, new tokens will be saved only on your device and never sent back to the cloud. If you decide to turn the feature off later, new tokens will once again be stored on our servers, but the ones already on your phone remain safe and encrypted. +Due to the platform’s security policies, when Twitter tokens are stored locally, you can only send one message before you need to revoke and restore the token to send another. Therefore, refreshed Twitter tokens will be sent via sms to the user after every successfully sent Twitter message, and the users will need to paste said tokens into the app to be able to send new tweets without the need for revoking and restoring. While this requires a bit more effort, it adds an extra layer of security for your Twitter account and aligns with best practices for handling sensitive credentials. + +This new feature reflects our ongoing commitment to strengthening privacy and security without sacrificing functionality. We want to empower you with tools that keep your communications private and your data in your hands. + +Update your SMSWithoutBorders app and find the new option for **‘store tokens on device’** in your settings, and let us know what you think of this new feature. From f6de02d4aeecdc8af833647d96f351ab2516aa0a Mon Sep 17 00:00:00 2001 From: mildrette Date: Tue, 10 Jun 2025 10:07:28 +0100 Subject: [PATCH 5/7] fixing error --- .../Local-Storage-for-Your-Access-Tokens.md | 9 ++++---- _posts/local-storage-for-access-token.md | 21 ------------------- package.json | 3 ++- 3 files changed, 7 insertions(+), 26 deletions(-) delete mode 100644 _posts/local-storage-for-access-token.md diff --git a/_posts/Local-Storage-for-Your-Access-Tokens.md b/_posts/Local-Storage-for-Your-Access-Tokens.md index 4812df6..b4a19ac 100644 --- a/_posts/Local-Storage-for-Your-Access-Tokens.md +++ b/_posts/Local-Storage-for-Your-Access-Tokens.md @@ -1,6 +1,6 @@ --- title: "Local Storage for Your Access Tokens" -excerpt: "Storing your tokens locally means reducing your reliance on our servers and minimizing the risk of your sensitive account information being exposed." +excerpt: "Storing your tokens locally means reducing your reliance on our servers and giving you total control of your stored tokens. This is especially valuable for users who value privacy and control over their data." coverImage: "/icon.png" date: "2025-06-05" author: @@ -14,11 +14,12 @@ ogImage: Keeping your online account credentials safe is a tricky balance between convenience and privacy. To give you more control, we’ve rolled out a new feature that lets you store your access tokens (the digital keys to your online platforms) right on your phone, not on the RelaySMS servers. -Storing your tokens locally means reducing your reliance on our servers and minimizing the risk of your sensitive account information being exposed. This is especially valuable for users who value privacy and control over their data. +Storing your tokens locally means reducing your reliance on our servers and giving you total control of your stored tokens. This is especially valuable for users who value privacy and control over their data. + +**Here’s how it works**: when you turn this feature on, any access tokens currently stored on the RelaySMS server are securely transferred to your device. From that moment, new tokens will be saved only on your device. If you decide to turn the feature off later, new tokens will once again be stored on our servers, but the ones already on your phone remain safe and encrypted. -**Here’s how it works:** when you turn this feature on, any access tokens currently stored in the cloud are securely transferred to your device. From that moment, new tokens will be saved only on your device and never sent back to the cloud. If you decide to turn the feature off later, new tokens will once again be stored on our servers, but the ones already on your phone remain safe and encrypted. Due to the platform’s security policies, when Twitter tokens are stored locally, you can only send one message before you need to revoke and restore the token to send another. Therefore, refreshed Twitter tokens will be sent via sms to the user after every successfully sent Twitter message, and the users will need to paste said tokens into the app to be able to send new tweets without the need for revoking and restoring. While this requires a bit more effort, it adds an extra layer of security for your Twitter account and aligns with best practices for handling sensitive credentials. This new feature reflects our ongoing commitment to strengthening privacy and security without sacrificing functionality. We want to empower you with tools that keep your communications private and your data in your hands. -Update your SMSWithoutBorders app and find the new option for **‘store tokens on device’** in your settings, and let us know what you think of this new feature. +[Update](https://play.google.com/store/apps/details?id=com.afkanerd.sw0b) your SMSWithoutBorders app and find the new option for **‘store tokens on device’** in your settings, and let us know what you think of this new feature. diff --git a/_posts/local-storage-for-access-token.md b/_posts/local-storage-for-access-token.md deleted file mode 100644 index f9acfb7..0000000 --- a/_posts/local-storage-for-access-token.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: "Take Control of Your Privacy: Introducing Local Storage for Your Access Tokens" -excerpt: "Keeping your online account credentials safe is a tricky balance between convenience and privacy. To give you more control ..." -coverImage: "/icon.png" -date: "2025-05-27" -author: - name: "Aysha Musa" - picture: "/anon-avatar.jpeg" -ogImage: - url: "/icon.png" ---- - -Keeping your online account credentials safe is a tricky balance between convenience and privacy. To give you more control, we’ve rolled out a new feature that lets you store your access tokens (the digital keys to your online platforms) right on your phone, not on our cloud servers. - -Storing your tokens locally means reducing your reliance on our servers and minimizing the risk of your sensitive account information being exposed or compromised. This is especially valuable for users who live or work in places with limited or unreliable internet access, or for anyone who values privacy and control over their own data. -Here’s how it works: when you turn this feature on, any access tokens currently stored in the cloud are securely transferred to your device. From that moment, new tokens will be saved only on your device and never sent back to the cloud. If you decide to turn the feature off later, new tokens will once again be stored on our servers, but the ones already on your phone remain safe and encrypted. - -Due to the platform’s security policies, when Twitter tokens are stored locally, you can only send one message before you need to revoke and restore the token to send another. While this requires a bit more effort, it adds an extra layer of security for your Twitter account and aligns with best practices for handling sensitive credentials. - -This new feature reflects our ongoing commitment to strengthening privacy and security without sacrificing functionality. We want to empower you with tools that keep your communications private and your data in your hands. -Update your SMSWithoutBorders app and find the new option for store tokens on device in your settings and let us know what you think of this new feature. diff --git a/package.json b/package.json index 9124bde..c5c8f01 100644 --- a/package.json +++ b/package.json @@ -45,5 +45,6 @@ "lint-staged": { "*.js,jsx,ts,tsx": "eslint --cache --fix", "*.{js,jsx,ts,tsx,json,css,md}": "prettier --cache -w" - } + }, + "packageManager": "pnpm@10.7.1+sha512.2d92c86b7928dc8284f53494fb4201f983da65f0fb4f0d40baafa5cf628fa31dae3e5968f12466f17df7e97310e30f343a648baea1b9b350685dafafffdf5808" } From 13d964588fc9ab2254815df49f39beccfcdf153e Mon Sep 17 00:00:00 2001 From: mildrette Date: Tue, 10 Jun 2025 10:26:29 +0100 Subject: [PATCH 6/7] edited package.json --- package.json | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/package.json b/package.json index c5c8f01..9124bde 100644 --- a/package.json +++ b/package.json @@ -45,6 +45,5 @@ "lint-staged": { "*.js,jsx,ts,tsx": "eslint --cache --fix", "*.{js,jsx,ts,tsx,json,css,md}": "prettier --cache -w" - }, - "packageManager": "pnpm@10.7.1+sha512.2d92c86b7928dc8284f53494fb4201f983da65f0fb4f0d40baafa5cf628fa31dae3e5968f12466f17df7e97310e30f343a648baea1b9b350685dafafffdf5808" + } } From 2e3f827e4c119356cf82437c6f5e097202ede1d3 Mon Sep 17 00:00:00 2001 From: Promise Fru Date: Tue, 10 Jun 2025 13:19:42 +0100 Subject: [PATCH 7/7] Delete et --hard HEAD~3 --- et --hard HEAD~3 | 64 ------------------------------------------------ 1 file changed, 64 deletions(-) delete mode 100644 et --hard HEAD~3 diff --git a/et --hard HEAD~3 b/et --hard HEAD~3 deleted file mode 100644 index 9a949ab..0000000 --- a/et --hard HEAD~3 +++ /dev/null @@ -1,64 +0,0 @@ -991e094 (HEAD -> develop, origin/develop) still fixing error -191c650 fix code -5a23f33 update to the develop branch -49dbfb3 Merge branch 'staging' into develop -a087356 remove text -26358c4 (origin/staging) Merge pull request #46 from smswithoutborders/develop -c8d3dbe Merge branch 'staging' into develop -304a7d6 Merge branch 'main' of github.com:smswithoutborders/SMSWithoutBorders-Blog into develop -de19cbf Merge pull request #44 from smswithoutborders/develop -2ed6c49 added the bridges feature -9faec61 Merge pull request #41 from smswithoutborders/staging -40904f7 Merge pull request #43 from smswithoutborders/develop -204813f fixed linke issues -63f25f0 Merge pull request #42 from smswithoutborders/develop -8756350 Merge branch 'staging' into develop -6b63a99 pull from main -f1e7526 Merge branch 'main' of github.com:smswithoutborders/SMSWithoutBorders-Blog into develop -723b032 Merge pull request #40 from smswithoutborders/develop -1f65c2c added the new feature on relaysms -56f8732 Merge pull request #39 from smswithoutborders/staging -97bdcf6 Merge pull request #38 from smswithoutborders/develop -eada637 Merge branch 'staging' into develop -5e07712 added blog post for relaysms desktop -3d05879 Merge pull request #37 from smswithoutborders/staging -1bcd65f Fix: Use Node.js 20 and SSH keys for deployment. -1c3a92f Merge pull request #36 from smswithoutborders/develop -afaab47 Merge branch 'staging' into develop -28b87a7 update to the new blog -7214c1f added blog post about bridges -4c4ff90 Merge branch 'main' of github.com:smswithoutborders/SMSWithoutBorders-Blog into develop -1f5694c Merge pull request #35 from smswithoutborders/develop -f6c086d Fix code formatting issues using Prettier -9ad7b40 audit blog post -1ce3abc build(ci): add run_compose for docker compose builds -cbcbad4 Remove pnpm lock file from tracking and ignore it -6a764ce Merge pull request #34 from smswithoutborders/staging -81c5ddb Merge branch 'main' into staging -7db4e25 Merge pull request #33 from smswithoutborders/develop -bc5a0fb Merge branch 'staging' into develop -3f1b134 chenged website link -30a12b3 Merge pull request #32 from smswithoutborders/staging -5b20266 Merge pull request #31 from smswithoutborders/develop -855ff60 Merge branch 'staging' into develop -ab113b6 space edit -719bba2 Merge pull request #30 from smswithoutborders/develop -acfe9ba Merge branch 'staging' into develop -0c07ff6 refactor: rename post files -03fa9b6 Merge pull request #29 from smswithoutborders/develop -f8803f0 refactor: remove draft tag from recent posts -57b4ad7 Merge branch 'develop' of https://github.com/smswithoutborders/blog into develop -08c1716 rebrand and device id blog posts -c2ed828 Merge branch 'main' into develop -bcb9b20 correction to device id post -784165b Merge pull request #26 from smswithoutborders/develop -0e75ff5 device ID blog post -d15b15d rebranding blog post -ecbbf51 Merge pull request #25 from smswithoutborders/release/vault-0.1.0 -707efba refactor: update vault-0-1-0 release note -2531f0d Merge pull request #24 from smswithoutborders/release/vault-0.1.0 -c3a6985 refactor: add source code section to vault release -ad8d1e5 release: vault-0.1.0 -1d49f22 Merge pull request #23 from smswithoutborders/staging -4e512ad Merge pull request #22 from smswithoutborders/develop -7d614da fixed image issues on reliability blog post