Translated Topic in Pidgin Language;
PrivateTalk – Encrypted & Self-Destructing Messages [100% Privacy | Open-Source]Original Topic: PrivateTalk – Encrypted & Self-Destructing Messages [100% Privacy | Open-Source] Author:
joker_josue PrivateTalk - Encrypted & Self-Destructing Messages [[100% Privacy | Encrypted | No database | No tracking | Open-Source]] [ Official Website ] | [ Official GitHub ]I dey very glad to inform una about Private Talk, e bi open source project wey dey make for people 2 dey use am send message secretly between d person wey send am nd d person wey go receive am, and e go delete d message after dey read am, u no need to register am oooo, nd e still dey secure becos e dey secrets well well.
After, I don observe plenty projects wey dey create for people 2 dey snd message and d e go fit delete d message after dey read am, I con see say those people no dey bother about privacy. I con say, okay make I develop this project.
D community wey create dis Private Talk dey value anonymity, protection and make am easy for people. As I dey talk to you now, e dey available nd na free of charge 2 everybody. Secret massages wey dem encrypt 4 browser and e go delete himself after dey read am, u no need to register am, e no dey use cookies, e no dey hide logs, e no dey track IP, e no get any place where e go dey store data.
Wettin b d meaning of PrivateTalk? - PrivateTalk na tool or device wey dem dey use to snd secret messages wey encrypt himself for browser.
- D message go delete himself after dey read am, or after d time wey d person wey dey use am set.
- U no need to register am ooo, e no dey store your personal information, nd e no dey use cookies.
- D code na open-source nd anybody fit go through am.
Features - Dem go encrypt ur messages for browser like secret code (AES-GCM)
- E get single or split link 4 maximum privacy.
- U get choice and chance, if you wan add another password 4 more security or protection, u re free to do am.
- U fit set a time when d messages go expire or delete, and also d specific time when the message go appear. (“scheduled message”)
- E get public logs wey go show when d messages destroy/expire (mathematical proof).
- E get local dashboard where u go fit manage your messages (so u need 2 send anytin to server)
New in v2.0.0 — Identity (ECC) As I dey talk to u now, PrivateTalk get identity (ECC) module, wey dey keep massages safe, using asymmetric encryption (P-256).
U fit generate public key (PTPUB1) wey u go share nd a private key (PTPRIV1) 2 dey keep secret. Na only u go fit read the messages wey dey sent 4 u, for ur public key - nd d messages are deleted and destroyed after you read am.
Wettin b d tins wey PrivateTalk dey do differently? | e dey 100% secure 4 keeping secrets: | e dey encrypt messages for browser like secret code through AES-GCM, dem no dey send any messages or key 2 d server in clear text. Even d administrator no fit access d content, even if e get full access 2 d server.
Privnote: no dey encrypt 4 browser; d text goes to d server in clear text (dem talk say "nobody dey read am" so, d only tin now na to trust d operator).
One-Time Secret: dey do encryption, but sometimes, d key dey dey for d server nd d security depend on how dem dey implement am.
BurnNote/QuickForget: generally e no dey do client-side encryption; e bi like say na "delete after read" approach dem dey make use of.
|
| Self-destruction and public logs: | After dey don read am finish, d message go delete automatically and e no go fit reverse again. D system dey generate special SHA-256 hash 4 each message, wey dey publish logs wey go dey show say dem don destroy or delete/ expire -- anybody fit check am nd dey go know say d file don delete, but no one fit bring am back.
Others: Most of dem no dey show public logs or proof to show say something delete. So, u no go fit know wettin dem delete for there.
|
| Advanced sharing: | E get d power 2 divide d secure link into two parts so dat e go get big privacy -- u fit share d link nd key for different channels, e dey increase privacy wen u dey use multiple channels.
Others: Dey go provide only link, dem no dey suggest whether dey should separate d shard/key.
|
| Time-lock and custom expiration: | E go allow you to set timer on a specific dates/times wen you go dey read the message (e.g only after 8pm and until 10pm), on top of dat of traditional automatic expiration.
Privnote/One-Time Secret: upon all, d only tin wey e dey support na d expiration after dey don read am finish or after d time wey dem fixed don reach.
|
| Database no dey, tracking no dey, cookies no dey: | Everything works with just flat files on the server. Dey no dey track, dey no dey do analysis, zero external scripts. Dey no even get d tools wey dem dey use 4 analysis.
Privnote: E dey use databases, e fit log accesses, normally e dey get cookies nd e dey also get analytics scripts.
Others: dey get ads wey u go fit use to track user's browsing.
|
| Private Dashboard: | dey allow d user to dey monitor d status of their messages, wen dem dey (read, active, expired) locally nd manually, nd dey no need to send sensitive information 2 d third party (dey no need 2 bring another person into the picture). E dey completely private, without any automatic communication 2 d server.
Others: no dey allow d user 2 manage d state of d messages -- na only server dey control am.
|
| Simple and auditable code: | all is focus na on transparency, easy auditing, nd how dem go dey increase d security 4 end users. Na Open-Source e bi, nd u go fit follow am easily, e no get any obscure dependencies.
Others: dey no bi open source, nd dey no have code dat dey very complex/ difficult to audit.
|
| No registrations, emails, SMS or Telegram: | E no dey collect email, phone or other user's information, so dey no get dat kind of notifications -- e dey maintain more privacy nd less tracking.
Others: users go do registration, dem go put their email, put their phone number or other information where dem go receive notifications, Wey go make dem link am with other tins.
|
FAQ How e dey take work? U go to the type d message, d browser go generate d link wey u go use 4 encryption, nd na only d people wey get the link/key go fit read am. Wen dey read am finished or e expired nd deleted, nobody go fit bring back the message.
Does the server see the messages? No. D text no dey leave ur in a readable format.
How does d Dashboard dey take work? After u don create d message finish, you fit save am 4 ur computer with d link nd a tag
(link,tag) - one line 4 each line. 4 d Dashboard, u fit load d file 4 d browser nd e go analyzes d logs 2 check d status of d message. Na 4 browser u go check am, dey no dey ever send any files 2 d server.
If u get any feedback, suggestions, or questions, space dey for u, so feel free to talk nd you are free to ask! Test am nd leave ur comment or contribute/ share d ideas/bugs wey u get here in d topic (or 4 GitHub). If you like d project nd and u wan support (or buy beer 4 me), i dey accept donations:
bc1q9f2dhfdrzruyecfwea3n6nt2nuaj6htzgke5q2Dey don add dis project 4 Talk2Tag project, where dem go dey give useful tools 4 forum users. I go give una more information soon.