Allow polling of a single address #12
Comments
jimmysong
added a commit
to jimmysong/bmwrapper
that referenced
this issue
May 29, 2014
jimmysong
added a commit
to jimmysong/bmwrapper
that referenced
this issue
May 29, 2014
jimmysong
added a commit
to jimmysong/bmwrapper
that referenced
this issue
May 29, 2014
Add "currentAddress" to the bminterface as a global variable Change handleUser to set the currentAddress if username begins with "BM-" This change is meant to allow different users to access their bitmessages Note this will not work concurrently! once USER is sent, all subsequent messages assume the same user until a different USER is defined.
jimmysong
added a commit
to jimmysong/bmwrapper
that referenced
this issue
May 29, 2014
Add "currentAddress" to the bminterface as a global variable Change handleUser to set the currentAddress if username begins with "BM-" This change is meant to allow different users to access their bitmessages Note this will not work concurrently! once USER is sent, all subsequent messages assume the same user until a different USER is defined. This closes issue Arceliar#11
jimmysong
added a commit
to jimmysong/bmwrapper
that referenced
this issue
May 29, 2014
Add "currentAddress" to the bminterface as a global variable Change handleUser to set the currentAddress if username begins with "BM-" This change is meant to allow different users to access their bitmessages Note this will not work concurrently! once USER is sent, all subsequent messages assume the same user until a different USER is defined. This closes issue Arceliar#12
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In a setup where there are multiple addresses in a Bitmessage node, I'd like to be able to download only the messages that have been sent to a single address instead of all the addresses.
Perhaps it could work that if the username passed via POP matches an address belonging to the node you only get that address's messages, and if the username doesn't match you get all messages (current behavior).
The text was updated successfully, but these errors were encountered: