Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#1468 closed enhancement (invalid)

subscriptions for Bote

Reported by: user Owned by:
Priority: minor Milestone: undecided
Component: apps/plugins Version: 0.9.17
Keywords: I2P-Bote Cc:
Parent Tickets: Sensitive: no

Description

It would be very nice to have subscriptions for Bote, so that you can subscribe to publications by other users. Those post something that can be read by all subscribed users.

Subtickets

Change History (3)

comment:1 Changed 5 years ago by str4d

Keywords: I2P-Bote added; Bote removed
Resolution: invalid
Status: newclosed

Pub/sub is not within the scope of I2P-Bote itself.

Any existing software that implements a pub/sub system over email can be used with I2P-Bote, by configuring the software to use I2P-Bote's SMTP port for sending mail (and perhaps mandating BOTEDEST@bote addresses if the software requires foo@… address formats).

If that *doesn't* work, please reopen this ticket with more details.

comment:2 Changed 5 years ago by user

Built-in would be cool. In fact I don't know how you could use an exisiting system on top of Bote as is, whithout either having to send the mail to each subscriber individually or losing authentication.

Last edited 5 years ago by user (previous) (diff)

comment:3 Changed 5 years ago by user

Subscriptions are a way of receiving messages from other users that those send to an interested public.
A user may decide to share a message with all of his friends/collegues/followers/fans.
He has three options to do so: 1) sending to various bote addresses (possible now, but manual and slow); 2) sending to a mailing list (repliable, another ticket); 3) sending a 'broadcast' to all of his subscribers (this ticket).
This ticket is about #3. (#1 is possible already now, and #2 is covered in ticket 1467)

To subscribe to a user's broadcats, the subscriber only needs to add the broadcaster's bote address to his list of subscriptions.
Broadcast packets bear a flag indicating that they are part of a broadcast.
The broadcaster sends his broadcasts into the DHT (storing directly or via relays).
Since the subscribers only know the pubkey, broadcasts are sent like normal Bote mails to the address of the broadcast. The only difference for sender and relays is the flag.
The storing nodes must not delete broadcast packets after retrieval.

For the network this is (still) the same as mailing lists.

Receivers check if all messages were sent by the owner of the broadcast's privkey. In the future there might be anti-spam measures on the storing nodes too, but this would require an additional layer.

Note: See TracTickets for help on using tickets.