# 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 22
# self = https://watcher.sour.is/conv/nbqgtxq
@lyxal Yeah! It has! Many of which are active users 😀 We're also going through a rebranding... We'll still keep the same twtxt spec/format under the hood. Exciting times 🤗
@lyxal Yeah! It has! Many of which are active users 😀 We're also going through a rebranding... We'll still keep the same twtxt spec/format under the hood. Exciting times 🤗
@prologic why can't I update my email address? I recently discovered there were issues with the provider I was using (read as "difficulties with sending/receiving emails"), so I had to create a new email account. I tried changing it in settings, but when I refresh the page, it still shows my old email.
@lyxal Ooooh I _think_ you may have discovered a bug! In fact it should never show your email at all, because we don't actually store it. Do me a favor and logout and try to use a password recovery mechanisms. I want to rule out something... But yeah we only store a hash now as of some time ago.
@lyxal Ooooh I _think_ you may have discovered a bug! In fact it should never show your email at all, because we don't actually store it. Do me a favor and logout and try to use a password recovery mechanisms. I want to rule out something... But yeah we only store a hash now as of some time ago.
@prologic Okay so I requested a password reset and it asked me where to send it. I put in my new email account and that's where I found the password reset message. I then checked the old email and there was no reset message (as expected).
Could it be your browser's autofill? On my settings page, the 'change email' box has no content.
Could it be your browser's autofill? On my settings page, the 'change email' box has no content.
@lyxal Cool! So that works! I’ll go figure out the other bug! It should not store nor display shit 🤣
@lyxal Cool! So that works! I’ll go figure out the other bug! It should not store nor display shit 🤣
@mckinley I just tested it on my phone (which doesn't have autofill set up at all - I use Vivaldi on desktop and Duckduckgo on mobile). The email address is still there.
@lyxal @mckinley perhaps it's a result of having an account that's older than average. 🤔🤔🤔
@lyxal @mckinley Yeah I _think_ it's a bug or bad data left over. I'll get it fixed! It shouldn't show up at all!
@lyxal @mckinley Yeah I _think_ it's a bug or bad data left over. I'll get it fixed! It shouldn't show up at all!
@lyxal @mckinley
> perhaps it’s a result of having an account that’s older than average. 🤔🤔🤔
This ☝️ See as I to try hard not to break my production instance, I do things like "live data migrations" all the time. Most of the time no-one even notices. But clearly I screwed something up here...
@lyxal @mckinley \n\n> perhaps it’s a result of having an account that’s older than average. 🤔🤔🤔\n\nThis ☝️ See as I to try hard not to break my production instance, I do things like "live data migrations" all the time. Most of the time no-one even notices. But clearly I screwed something up here...
@lyxal @mckinley
> perhaps it’s a result of having an account that’s older than average. 🤔🤔🤔
This ☝️ See as I to try hard not to break my production instance, I do things like "live data migrations" all the time. Most of the time no-one even notices. But clearly I screwed something up here...
This is now fixed proper. Turns out the original migration job was missing a very important user.Email = "" 😳
This is now fixed proper. Turns out the original migration job was missing a very important user.Email = "" 😳
We'll drop the field entirely as it's no longer used at a later date/release.
We'll drop the field entirely as it's no longer used at a later date/release.