# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 17
# self = https://watcher.sour.is/conv/bnkkhha
πŸ“£ FYI: Be aware that the commit 034009eb85 breaks backwards compatibility with the builtin theme.


* 034009e 2021-10-28 | Fix the name of the default database, app specific JS and CSS files (HEAD -> master, origin/master) [James Mills]


If you have already copied the builtin theme and modified it to suit, please be sure to rename the twtxt.css and twtxt.js files accordingly and update your base.html template to match.
πŸ“£ FYI: Be aware that the commit 034009eb85 breaks backwards compatibility with the builtin theme.


* 034009e 2021-10-28 | Fix the name of the default database, app specific JS and CSS files (HEAD -> master, origin/master) [James Mills]


If you have already copied the builtin theme and modified it to suit, please be sure to rename the twtxt.css and twtxt.js files accordingly and update your base.html template to match.
@prologic not only this. A fresh, brand yarn.db will be created and contents from twtxt.db will have to be copied to it for things to work normally---and by that I mean, to be able to login, and otherwise use Yarn.
@fastidious Ouch yes you’re right! πŸ€¦β€β™‚οΈ Shall I add a startup job to correct this or just document the change? πŸ€”
@fastidious Ouch yes you’re right! πŸ€¦β€β™‚οΈ Shall I add a startup job to correct this or just document the change? πŸ€”
@fastidious This commit should help alleviate this breaking change:


* cb8e066 2021-10-28 | Add automatic rename of old store path for pod owners that use defaults to smooth over change in 034009e (HEAD -> master, origin/master) [James Mills]


For example, on startup:



πŸ‘Œ can you give it a try? πŸ€—
@fastidious This commit should help alleviate this breaking change:\n\n
\n* cb8e066 2021-10-28 | Add automatic rename of old store path for pod owners that use defaults to smooth over change in 034009e (HEAD -> master, origin/master) [James Mills]\n
\n\nFor example, on startup:\n\n \n\nπŸ‘Œ can you give it a try? πŸ€—
@fastidious This commit should help alleviate this breaking change:


* cb8e066 2021-10-28 | Add automatic rename of old store path for pod owners that use defaults to smooth over change in 034009e (HEAD -> master, origin/master) [James Mills]


For example, on startup:



πŸ‘Œ can you give it a try? πŸ€—
@prologic that would work. I already manually copied files, though. Maybe have someone who hasn't done a pull test it? Or do you want me to simply pull, delete yarn.db and compile it again, to have twtxt.db renamed?
@fastidious Nope all good 🀣 I _know_ it works because I tested it myself 🀞 But if @eldersnake if you wanna git pull on one of your builds and see if it does the auto rename of twtxt.db -> yarn.db on startup? πŸ€”
@fastidious Nope all good 🀣 I _know_ it works because I tested it myself 🀞 But if @eldersnake if you wanna git pull on one of your builds and see if it does the auto rename of twtxt.db -> yarn.db on startup? πŸ€”
@prologic \n> can you give it a try?\n\nThat worked. If I want to change that yarn.db default location (I asked on IRC, but seems everyone is out right now), what should I do? Something like this?\n\n
\nyarnd -s "bitcask://../yarn.db")\n
\n\nOr something else?
@prologic Yep, went all smooth!
@fastidious Yes that is the correct store config. yarnd -s bitcask:///path/to/store
@fastidious Yes that is the correct store config. yarnd -s bitcask:///path/to/store
@eldersnake Noice! πŸ‘Œ Trying to get back in the habit of ensuring backwards and forwards compatibility no matter what breaking changes there are πŸ˜…
@eldersnake Noice! πŸ‘Œ Trying to get back in the habit of ensuring backwards and forwards compatibility no matter what breaking changes there are πŸ˜