Welcome, Guest. Please login or register.

Author Topic: Self-contained client  (Read 1846 times)

LateToTheParty

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Self-contained client
« on: July 14, 2015, 12:56:39 PM »
Have any self-contained clients been developed? Perhaps a mobile client that doesn't require RPC to an external process? A Javascript implementation that runs in the browser?

I'm looking for something my mother could use--a one-click install and a simple UI.

Thanks

Darth.Severus

  • Newbie
  • *
  • Posts: 38
  • Karma: +2/-0
    • View Profile
Re: Self-contained client
« Reply #1 on: July 16, 2015, 10:17:56 AM »
- Mobile devices are even more insecure then home computers
- BM will always need strong hardware for spam protection
- Services in the browser are less secure then standalone programs

What's the usability problem with the standard client?

AyrA

  • BM-Bc7Rspa4zxAPy9PK26vmcyoovftipStp
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1262
  • Karma: +75/-7
  • bitmessage.ch and timeservice operator
    • View Profile
    • AyrAs Homepage
Re: Self-contained client
« Reply #2 on: July 23, 2015, 03:54:25 AM »
The client for windows is self-contained: https://bitmessage.org/download/windows/Bitmessage.exe
My Address: BM-Bc7Rspa4zxAPy9PK26vmcyoovftipStp
Bitmessage Time Service (Subscribe): BM-BcbRqcFFSQUUmXFKsPJgVQPSiFA3Xash
Support the Multipart Message Declaration Draft for Bitmessage: https://bitmessage.org/forum/index.php/topic,1553.0.html
Free Bitmessage to E-Mail Gateway: https://bitmessage.ch

AJAr

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Self-contained client
« Reply #3 on: September 02, 2015, 01:24:54 PM »
https://blinked.ca is another excellent solution that popped up in the relatively near past. Runs in the browser, does all crypto in native JS while syncing with server to keep track of which messages have been seen (i.e. messages the client has attempted to decrypt) with no mention of which messages have been decrypted successfully. Form what I can gather, there is no plaintext information stored on the server that indicate what addresses are known to, owned by, or sent to/from a given registered user. Seems very solid.