PrivateTalk – Encrypted & Self-Destructing Messages [100% Privacy | Open-Source]

[bitmover]

Congratulations joker_josue! Your coding skills are improving a lot!

I don't know why, but there is some kind of region block. I couldn't see your website from Brazil. I needed to turn on a VPN (netherlands) to be able to see it.
Maybe you should take a look at it!

[joker_josue]

I don't know why, but there is some kind of region block. I couldn't see your website from Brazil. I needed to turn on a VPN (netherlands) to be able to see it.
Maybe you should take a look at it!

That's strange. I just logged in with VPN Brazil and it worked. Can you access https://talk2tag.com/ ?

And you can access this website: https://jokerartgallery.com/ ? It's on the same server.

[bitmover]

I don't know why, but there is some kind of region block. I couldn't see your website from Brazil. I needed to turn on a VPN (netherlands) to be able to see it.
Maybe you should take a look at it!

That's strange. I just logged in with VPN Brazil and it worked. Can you access https://talk2tag.com/ ?

I see just coming soon.

And you can access this website: https://jokerartgallery.com/ ? It's on the same server.

Yes

[Satofan44]

I don't know why, but there is some kind of region block. I couldn't see your website from Brazil. I needed to turn on a VPN (netherlands) to be able to see it.
Maybe you should take a look at it!

That's strange. I just logged in with VPN Brazil and it worked. Can you access https://talk2tag.com/ ?

I see just coming soon.

That's correct then, that's also what I see.

I don't know why, but there is some kind of region block. I couldn't see your website from Brazil. I needed to turn on a VPN (netherlands) to be able to see it.
Maybe you should take a look at it!

Can you share what particular error you are experiencing? Since you can access https://talk2tag.com/, it should not be a DNS thing. What browser error do you get?

[joker_josue]

I see just coming soon.

And you can access this website: https://jokerartgallery.com/ ? It's on the same server.

Yes

Okay! Then you shouldn't have any problems accessing https://talk2tag.com/privatetalk/

It's all on the same server/DNS/domain, if you see one thing the other must not be blocked.

[bitmover]

I see just coming soon.

And you can access this website: https://jokerartgallery.com/ ? It's on the same server.

Yes

Okay! Then you shouldn't have any problems accessing https://talk2tag.com/privatetalk/

It's all on the same server/DNS/domain, if you see one thing the other must not be blocked.

It worked now without VPN

I don't know what happened, but its fine now

[NotATether]

Maybe if there is enough demand, you can also create a Pastebin.

I just had an untimely reminder today when I was trying to share a link of how unreliable other pastebins are. It would be nice to have a Bitcointalk Pastebin.

Also, what do you say about somehow integrating this into Personal Messages? They can basically be delivered as links instead of encrypted text, but that requires good uptime.

[TryNinja]

I had to analyze this possibility very carefully. Well, I have to ensure that security and privacy were guaranteed. Since it's all done in the browser, on the client side, it can be more complicated.

But, there is a point to analyze.

Oh, right... If all the encryption is done locally with javascript, embedding this into a script that also runs locally while on the forum is pretty easy.

So all I will need to do is send the encrypted text to your API so it is published for the other user to read.

I'll take a look at the source code and cook something.

[dkbit98]

Also, what do you say about somehow integrating this into Personal Messages? They can basically be delivered as links instead of encrypted text, but that requires good uptime.

I already asked the same question not long ago in this topic
After having some time thinking about it I think that moderators would also be able to read those messages,
unless message is created in that way that only one specific member can decrypt and open it.

[joker_josue]

Also, what do you say about somehow integrating this into Personal Messages? They can basically be delivered as links instead of encrypted text, but that requires good uptime.

I already asked the same question not long ago in this topic
After having some time thinking about it I think that moderators would also be able to read those messages,
unless message is created in that way that only one specific member can decrypt and open it.

This could really be interesting. But how?  
An element had to be used that only the target user knew in order to access it.

But I'll think about it. Maybe I can come up with something that might work.

Also, what do you say about somehow integrating this into Personal Messages? They can basically be delivered as links instead of encrypted text, but that requires good uptime.

I already asked the same question not long ago in this topic
After having some time thinking about it I think that moderators would also be able to read those messages,
unless message is created in that way that only one specific member can decrypt and open it.

Sorry for the double post... but I thought about several things and found an idea that might have potential. And I'd like to hear your opinion, so I know if I should add it to the roadmap or not. _{Then I will ask the moderator to merge the posts.}

The idea would be for users to create a secure identity (key pair) within PrivateTalk, publicly sharing only the public key.
This would allow any user to send encrypted messages directly to that user using this public key. However, only those who have the private key saved can read it.

It would be a "super simple PGP-like" approach. What do you think? Does it make sense?
Comments and suggestions are welcome!

[dkbit98]

The idea would be for users to create a secure identity (key pair) within PrivateTalk, publicly sharing only the public key.
This would allow any user to send encrypted messages directly to that user using this public key. However, only those who have the private key saved can read it.

It would be a "super simple PGP-like" approach. What do you think? Does it make sense?
Comments and suggestions are welcome!

Your idea sounds good, but how would a member who receives the message know a private key?
I don't fully understand how this secret identity would work with bitcointalk messages, unless we are using some other way of communication.
If you can show some demo example that would be great.

[joker_josue]

The idea would be for users to create a secure identity (key pair) within PrivateTalk, publicly sharing only the public key.
This would allow any user to send encrypted messages directly to that user using this public key. However, only those who have the private key saved can read it.

It would be a "super simple PGP-like" approach. What do you think? Does it make sense?
Comments and suggestions are welcome!

Your idea sounds good, but how would a member who receives the message know a private key?
I don't fully understand how this secret identity would work with bitcointalk messages, unless we are using some other way of communication.
If you can show some demo example that would be great.

The idea still needed to be developed further. But basically it would be like this:

1. Go to PrivateTalk and create a personal key. This personal key is made up of two parts: a public key and a private key.
2. Don't give the private key to anyone! You can put the public key in your Bitcointalk profile, for example.
3. If I want to send you a secret message, I go to PrivateTalk, create the message and enter your public key.
4. A link will be generated and sent to you via PM.
5. You enter the link and have to use your private key to open the message (password type).

What do you think of the idea?

[dkbit98]

1. Go to PrivateTalk and create a personal key. This personal key is made up of two parts: a public key and a private key.
2. Don't give the private key to anyone! You can put the public key in your Bitcointalk profile, for example.
3. If I want to send you a secret message, I go to PrivateTalk, create the message and enter your public key.
4. A link will be generated and sent to you via PM.
5. You enter the link and have to use your private key to open the message (password type).

What do you think of the idea?

OK I get it now, you first need to know the public key of member who is receiving your message.
It sounds good in theory, but clear and simple instructions must be written for people to actually use this.
I can this can be very useful for keeping privacy in some dark scenarios of a hacked forum.

[joker_josue]

I released version 2.0.0, with a new feature that allows you to create a public/private key, to send/receive messages: https://talk2tag.com/privatetalk/identity.php

- Added new Identity (ECC) system using P-256 asymmetric encryption.
- Users can generate public (PTPUB1) and private (PTPRIV1) keys in the browser — private keys never leave the client.
- Messages encrypted for a public key can only be decrypted by the matching private key.
- Automatic message deletion from the server after successful read.
- Includes key pair generation, copy, and download tools.
- Updated UI with dedicated sections for composing and reading identity messages.
- Added clear instructions for both sending and reading messages.

They can create a public/private key, save the private key, and present the public key to anyone who wants to send a message so that only the person with the private key can read it.

For example, instead of sending a PM here on the forum with a PrivateTalk link containing sensitive data, you can now send a link to the message that only the recipient can read, having the private key.
This way, even if the PM is intercepted by a third party, you won't be able to read the message with the link.

I appreciate your feedback.


What do you think about me opening a thread for users who want to share their public keys?
Do you think this thread is in the correct thread, or should it be in a different thread?

[Satofan44]

What do you think about me opening a thread for users who want to share their public keys?
Do you think this thread is in the correct thread, or should it be in a different thread?

Definitely a different one, keep this for updates, reviews and feedback. Just include a link to the new one in this one too.

[NotATether]

1. Go to PrivateTalk and create a personal key. This personal key is made up of two parts: a public key and a private key.
2. Don't give the private key to anyone! You can put the public key in your Bitcointalk profile, for example.
3. If I want to send you a secret message, I go to PrivateTalk, create the message and enter your public key.
4. A link will be generated and sent to you via PM.
5. You enter the link and have to use your private key to open the message (password type).

What do you think of the idea?

I would really like it if we could import our own public keys (NOT private keys) and then users could verify that messages are coming from us.

We would simply sign and encrypt our own messages, paste the "BEGIN PGP ENCRYPTED MESSAGE" part, and then PrivateTalk will simply serialize it and act as the medium for obtaining such message.

It would be like a key server, but it actually works properly because it has a delete feature, unlike keyservers, which was a flaw that was widely abused.

[joker_josue]

1. Go to PrivateTalk and create a personal key. This personal key is made up of two parts: a public key and a private key.
2. Don't give the private key to anyone! You can put the public key in your Bitcointalk profile, for example.
3. If I want to send you a secret message, I go to PrivateTalk, create the message and enter your public key.
4. A link will be generated and sent to you via PM.
5. You enter the link and have to use your private key to open the message (password type).

What do you think of the idea?

I would really like it if we could import our own public keys (NOT private keys) and then users could verify that messages are coming from us.

We would simply sign and encrypt our own messages, paste the "BEGIN PGP ENCRYPTED MESSAGE" part, and then PrivateTalk will simply serialize it and act as the medium for obtaining such message.

It would be like a key server, but it actually works properly because it has a delete feature, unlike keyservers, which was a flaw that was widely abused.

What is implemented at the moment is like this
https://talk2tag.com/privatetalk/identity.php

Your idea is the person who sends it, also indicate your public key, so that whoever receives it can be sure of the origin of the message?
Interesting.

Now there needed to be a public place where people put their public key.