# 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 7
# self = https://watcher.sour.is/conv/3kwlwda
@ullarah On the desktop, at least, it seems like there is very little benefit. Anyone concerned with clicking on a malicious link will hover over it and check the bottom corner before clicking. Those who aren't concerned, even though they should be, will just click the big blue button no matter what. At best, it's an annoyance. At worst, it's allowing the pod owner to play Zuckerberg with his users.
@mckinley Hmmm

@ullarah I _wonder_ if we can make this a JS-only feature and do something like "detect we're on a Mobile Device"? I mean if the primary motivation for this feature is as you say so protect users from malicious links on Mobile Devices, then we _should_ make this a Mobile-only feature? šŸ¤” And this is probably one of those cases where doing it client-side is okay I think...
@mckinley Hmmm

@ullarah I _wonder_ if we can make this a JS-only feature and do something like "detect we're on a Mobile Device"? I mean if the primary motivation for this feature is as you say so protect users from malicious links on Mobile Devices, then we _should_ make this a Mobile-only feature? šŸ¤” And this is probably one of those cases where doing it client-side is okay I think...
@mckinley Iā€™m hoping the new patch, _in the next few hours_, will literally remove linkVerify redirection for those users, and poderators, who have turned it off. šŸ‘
@prologic That's a good idea. If it's done in JavaScript, mobile devices can be detected using navigator.userAgent. Depending on how far you're willing to go with it, the entire prompt can be constructed locally, so the URL is never revealed to anyone else.
@mckinley Yup šŸ‘Œ I like this as an improvement šŸ‘Œ

@ullarah Can we add this to the backlog?
@mckinley Yup šŸ‘Œ I like this as an improvement šŸ‘Œ

@ullarah Can we add this to the backlog?