ADAMANT would become the world first truly decentralised and censorhip resistant messenger.
For sure you Adamant can leverage Massa’s MNS (Massa Name Service) already existing on mainet.
Massa was created with the intent of making it easy to transfert existing website and dApp to the DeWeb. Especially right now with $MAS being very cheap, storing the app on Massa will be very cheap compare to next year and the best part, there is no ongoing storage costs and when you remove the stored data from the network, a $MAS are reimbursed!
What about even leveraging Massa’s Autonomous Smart Contract to automate tasks or seek the possibility to even move some of it on Massa DeWeb.
Definitly many possibilities. Look at the bounty offers as well.
All of these, including ADAMANT app itself are open-source.
As I see, an app hosted on .massa will do external requests to nodes and services, or… run .massa resolvers on these nodes also, similar how .onion nodes currently do. You can see that ADM’s Tor app adamant6457join2rxdkr2y7iqatar7n4n72lordxeknj435i4cjhpyd.onion doesn’t do external requests.
If its possible and also relevant and interesting for the community to run ADM messenger on .massa, it would de great to provide MAS grant for this.
As Massa’s mobile wallet is a priority (DeWeb on mobile devices and built in browsers - #4 by damir), may be it’s also interesting adding MAS support to ADAMANT (along with creating a special wallet for MAS, which is in development already). It will open these possibilities:
Storing and transferring MAS on different platforms (ADAMANT has iOS, Android, Web, Tor and desktop apps)
Show tx list for a user wallet (thought current MAS node implementation doesn’t provide such API)
Sending MAS in chats
My concern is ADM apps doesn’t have Web3 possibilities yet (like WalletConnect), and interacting with dApps like Dusa is essential. I’ll speak with ADM dev community if they are going to implement this in the nearest future.
The concept is great, and technically it works well. But in practice, adoption is almost zero — users still prefer the classic https://adm.im or the GitHub-hosted PWA ADAMANT Messenger .
Why?
Trust: when you open massahub.network, you still rely on a provider. It’s not obvious to users why they should trust this one over any other.
Setup: running ADAMANT fully self-hosted on DeWeb isn’t straightforward. Having a Massa wallet is not enough — you still need to configure nodes and services. So something like adm.massa won’t just work out-of-the-box.
Awareness: Massa hasn’t really promoted the unique advantages of DeWeb to end-users. For most, the benefits aren’t clear yet.
So the tech is there, but the communication and onboarding aren’t. Maybe the missing piece is stronger messaging from Massa about why DeWeb matters (vs. classic web), plus tools/tutorials that make self-hosting as simple as “1 click.”
Any thoughts on how we can push DeWeb adoption forward together?
native support with partners, in the Decentr browser bringing both partnerships and true Onion-style usability: https://x.com/massachain/status/1929818127300268130 (there you can directly type mysite.massa in the address bar and it will open the site through a local provider)
In the last few AMAs we explain that we shift from trying to sell the decentralized cloud services by themselves (which we had limited success with) to building our own real-world products on top of them to:
illustrate what the Massa services allow and attract both users and builders
provide an actually useful flagship product that can reach communities even beyond web3
Given our positioning on decentralization & freedom of speech, the ChatControl mess in Europe, and rapid increase in need for private communications, we naturally went to build the decentralized chat Gossip that makes use of Massa for DeWeb, p2p and payments.
Of course in the meantime we continue marketing, outreach, hackathons, node improvements, wallet improvements, trying to onboard people on deweb and so on.
