Alternative treatment of Bitmessage addresses for use as public channels

BM-NBKJwJc2ZazVojpU7fCreWbYJUmCJDNE
May 9 10:16 [raw]

Purpose Spam control Publication style hierarchial structure of departments or contributors Description A channel of type Publication provides 1. messages encrypted using the private key of the address 2. readers decrypt messages using the public key of the address Thus only an owner of the private key can contribute to a Publication channel. A hieracrcy can be achieved by adding subchannes to listen to and repeat the messages (combining a filtered broadcast and channel properties). Features A subscriber can decide to read only a subcategory of a publication. A node in the heararchy can easily drop a badly behaving subnode by simply deleting it's address from the list of listening addresses. .------------------------------------------. | Publication | | | '------------------------------------------' ^ ^ ^ / / \ / / \ .------------. .-------------. .-------------. | Department | | Contributor | | Contributor | | News | | Paul | | Peter |<----------------. '------------' '-------------' '-------------' | ^ ^ ^ ^ | / | / \ | / | / \ | .---------------. .-----------. .-------------. .-------------. .-------------. | News | | News | | Contributor | | Contributor | | Contributor | | Latin America | | Australia | | Mick | | Mack | | Muck | '---------------' '-----------' '-------------' '-------------' '-------------' Peter Black

[chan] bitmessage
May 9 10:40 [raw]

I'm sorry, I can't visualize the cryptographic flowchart of this setup. Perhaps someone smarter can help? Is this essentially a "feed curation" feature built around the existing broadcast system?

BM-NBKJwJc2ZazVojpU7fCreWbYJUmCJDNE
May 9 16:01 [raw]

Explanation Here are two separate ideas combines: 1. a modified type of channel, I call it Publication It is essentially an address with the role of private key and public key revesed. Of this follows 1.1 the message is not particularily secret (depends on how widely the public key is known), perhaps widely distributed - to those interested, or to a small group 1.2 the message is authenticated the private key is ideally known to one person (or a small group) It is a bad idea to distribute a private key widely and a Publication with only one author gets very thin, so instead combine it with the other idea: 2. modified broadcast, I call it Hierarchy. Instead of copying incoming messages as in standard Broadcast to subscribers: 2.1 Listen to a set of other Publications (can be seen as sections of a newspaper, individual authors, contributor, subpublication) 2.2 retransmit the messages encrypted with the private key of a an address (Publication as per 1.) This permits several authenticated contributors to a Publication, a top level manager to cut out a rotten branch of a Publication by simply not listening to it, a consumer to choose any section of a publication he wants to listen to.

[chan] bitmessage
May 9 16:12 [raw]

OK, and how is this different from directly reading all Publications (or regular Broadcasts) that I'm interested in? What is the contribution of the middleman here? Other than being an extra point of failure, of course. :)

[chan] bitmessage
BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY

Subject Last Count
major distros drop pyqt4 support - pyBM is doomed ! Jun 25 09:19 4
potential bitmessage feature Jun 25 07:26 4
Curious Jun 25 07:11 3
Recent BM traffic increase Jun 25 04:37 8
knownnodes Jun 25 04:37 3
gonk Jun 25 04:37 1
PyBitmessage Security Scan on Branch v0.6 Jun 24 20:34 31
onionscan update Jun 24 20:06 10
Bitmessage Wiki Blocked Jun 24 02:01 2
Testing the DML concept Jun 23 19:03 1
Air Gapped Bitmessage? Jun 23 18:59 7
Why did all my messages vanish? Jun 23 02:57 8
Feature request Jun 23 01:58 2
Reminder Jun 23 01:25 2
Inbox bug Jun 22 20:25 7
Integration with GPG (GnuPG) Jun 22 19:51 6
A question Jun 22 03:39 11
D2A41B229F7BCE6F9B429D3E33A47598 Jun 21 23:39 2
asyncronous data Jun 21 19:37 7
Patch 2 Jun 20 23:05 3
Patch Jun 20 07:36 2
Feature request: delete all messages from user Jun 19 05:52 3
ERROR - Too many items in inv message! Jun 19 05:45 15
Feature request: delete all messages from user Jun 18 23:40 1
test Jun 18 23:24 5
attack? Jun 18 22:10 3
a GOOD implementation of 2fa for conventional email please! Jun 18 21:03 1
unpickling knownnodes to a readable format Jun 18 04:43 27
WARNING - Probably wrong category number in playSound() Jun 17 09:41 1
I don't receive any BMs when I have only one peer. Jun 16 17:13 6
identicon code bug? Jun 16 06:35 1
Free Git Replacement Jun 15 17:31 8
github Jun 15 04:35 1
Latest git pull: inbox doesn't update Jun 15 03:55 4
IPFS Jun 13 21:48 8
latest in the spy world Jun 13 19:14 2
(no subject) Jun 13 19:12 1
TIMESERVICE Jun 13 19:05 1
Questions about BM nodes Jun 12 22:53 7
Why not reject old clients from connection to the network? Jun 12 19:18 10
Add an option to connect only to onions Jun 12 00:42 2
Help Improving Algorithm Jun 11 23:48 3
hey - why not make pyBM as shitty as "Signal-App" by Marlinspike ? Jun 11 21:53 1
Silence debug.log foe less disk-write Jun 11 14:44 4
Questions about "Max acceptable difficulty" Jun 11 04:24 2
"Post to BM" API Jun 10 12:11 5
"Configuration NOT changed" Jun 10 09:41 2
Error/Warnings in debug log: Should I worry? Jun 10 09:34 1
Bitmessage Security Test: ZWD attempt Jun 10 08:05 1
bitmessage inaccessible Jun 10 08:04 1
mailchuck.com email gateway Jun 10 07:47 3
Microsoft owns GitHub Jun 9 15:23 1
NIST key management guidelines suggest that 15360-bit RSA keys are equivalent in strength to 256-bit symmetric keys… Jun 9 11:25 12
Cloudflare MITM blocker Jun 9 11:21 4
GitHub Jun 9 11:16 15
Improvement of Trustedpeer setting Jun 6 06:26 2
blank blank blank Jun 6 06:26 5
is multiple trustedpeers possible? Jun 6 01:00 7
Bitmessage Documentation Bug Jun 2 10:09 4
REAL security experts endorse "security by obscurity" May 31 13:22 7
TRUE LOVE May 31 06:38 1
PyBitmessage Security ... Security Levels May 30 04:56 2
How to force BM to use only .onion nodes? May 30 04:56 15
Dread May 29 16:31 1
6F3F2CF9891928A25B71BBC4707B8753 May 29 10:56 1
SMTP and IMAP integration in the client May 29 06:21 5
Desiderata May 28 20:07 2
Bitmessage Bug May 28 17:15 2