0 sats \ 0 replies \ @eddieoz OP 8h \ parent \ on: GitHub - eddieoz/openxrypt: Secure Direct Messaging for Social Media privacy
Unfortunately yes. PGP has issues with usability, but it is safe.
The idea was to create something fast, reliable, simple, easy to verify, and trustworthy. This is the first version, and a lot can change.
For our community, I think it is better to release something safe and discuss what to change in usability than the opposite.
With the core working properly, the goal is to develop UX even if it means changing algos, etc. :)
Yes, and both should exchange their public keys between them.
This is because the plugin manages to encrypt the messages and decrypt the messages they identify.
Since there is no connection to APIs or the backend, imagine Twitter as the backend infrastructure for the messaging and the plugin as a layer over Twitter that handles the e2ee encryption.
I recommend using ECC 25519 in README because of RSA's massive and slow keys.
It is secure, fast, and widely used today.
GPG is not 'anti-goal'. It is about security and anti-surveillance.
Thank you for the feedback!
I believe GPG is a legacy, but far from obsolete.
There are definitely new protocols and developments, but this extension does not intend to be a full messenger.
As you said, it is an overlay encoding for social media. The tool was designed to not make online transactions like negotiating keys. It is designed to be simple, light and do everything locally.
I am willing to implement other functionalities and evolve the tool, but as a first version, I think it is safe enough to solve the problem of exchanging private messages on Twitter (and other social media soon)
Hopefully, I'll be able to publish the entire album as soon as Winamp resolves their current issues.
In the meantime, I've already published a few tracks on my pages at https://wavlake.com/eddieoz and https://soundcloud.com/eddieoz. And the lyrics for these tracks can be found on my website: https://www.eddieoz.com/tag/music/ :) I sincerely hope you enjoy the music!
Thank you very much for the kind mention!!
The idea behind this story was to create a Bitcoin journey through a cyberpunk realm, where a trader starts to learn more deeply about Bitcoin beyond just the investment aspect. The hero learns a lot of technical details, but also delves into the complex realms of morality and ethics within our ecosystem.
I sincerely hope the readers enjoy the story and find it engaging!
Hey, yeah!!! Let's do it!
I was waiting to publish another track because Winamp had 'internal issues' and was not able to distribute the album properly. I was waiting to release something. Because people were asking for this specific song, I published only it.
I hope you like the album! I'm getting good feedback about it! :)
counterparty is an option, also raretoshi as suggested by DarthCoin below.
I will check back with the community about the options. I need to understand if the person asking is just a degen or if they really value having a tokenized version of the autographed book on their wallets.
As I live far from the community, they asked to have an alternative of a signed book, in digital format. That's why I'm evaluating options and thinking about whether to do it on Bitcoin. I also have been reluctant to incentivize inscriptions.
the address is based on the hash of the document. it is unique for each document and used also to avoid storing duplicates.
you have good points. the only thing about ipfs, the pointer is a hash of the file, so there is no way of having the same pointer directing to another file. but I agree about the museum parallel.
your points make sense, and I follow the discussions about what can characterize spam since the counterparty war in 2014. it is a dense topic in bitcoin.
Yeah, I'm aware of opentimestamps, and I have a project using btc op_return running since 2015 to authenticate docs.
The audience asked for a personalised inscription to have on their wallets (probably degens).
I have a view about spamming the network like ordinals and inscriptions are doing in general. But maybe a few bytes in text mode, costing extra ~9k sats (I just discovered) is not a problem. But I'm not fully convinced.