Users? Or multiple secrets & associate bookmarks to them? about audioserve HOT 4 CLOSED

Actually bookmarks are not kept on server - so they cannot get jumbled.
If you are speaking about bookmarks in Android client - they are kept locally in device - stupid but simple.

Having server to maintain bookmarks would be useful indeed - but not priority now. (Priority is #23 )

from audioserve.

Ahh! I hadn't realized bookmarks were clientside. So, that means switching from the android client to the web client would cause the user to lose their place. Yeah, I definitely vote for server side bookmarks then. =]

Thanks for the response!

from audioserve.

Actually there is kind of experimental playback continuation on different device- see in readme. There you define so called devices group - so it can work for multiple users. It somehow works, but it's not totally reliable.

from audioserve.

After updating to new collection cache we still using group concept, which enables to share last position for any folder within given group. I hope it solves main use case. There are plans to have multi user system, you always share collections, just can define groups that share playback positions.

from audioserve.