# 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 13
# self = https://watcher.sour.is/conv/vdbrbha
I truly despise the way Apple has slowly locked up macOS
@shreyan Locked up how? Irs my primary OS and I don't see how it's too locked up tbh
@shreyan Locked up how? Irs my primary OS and I don't see how it's too locked up tbh
@shreyan Locked up how? Irs my primary OS and I don't see how it's too locked up tbh
@prologic It's also been my primary OS for a long time, and I still love it, but I don't love some of Apple's decisions. What prompted me to write this specific post was having to take extra steps to open FOSS apps on macOS because they don't have an "Apple-approved" signature 🤦‍♂️
@shreyan For the sake of security and supply-chain-attacks, I don't have a problem with that requirement per se to be honest. If you build from source, you're all good. If you download some arbitrary binary, yeah you're going to want that to be signed. As I do most things with either go or brew I don't really run into too many issues here myself.
@shreyan For the sake of security and supply-chain-attacks, I don't have a problem with that requirement per se to be honest. If you build from source, you're all good. If you download some arbitrary binary, yeah you're going to want that to be signed. As I do most things with either go or brew I don't really run into too many issues here myself.
@shreyan For the sake of security and supply-chain-attacks, I don't have a problem with that requirement per se to be honest. If you build from source, you're all good. If you download some arbitrary binary, yeah you're going to want that to be signed. As I do most things with either go or brew I don't really run into too many issues here myself.
@prologic True, brew is very helpful in that regards, and yeah, security does matter. It just bothers me when they use such logic to, for example, restrict Safari WebExtensions to only being available through the App Store even if it's signed properly
@shreyan Ahh I see. 🤔 Surely there's a way to manually add them with developer options?
@shreyan Ahh I see. 🤔 Surely there's a way to manually add them with developer options?
@shreyan Ahh I see. 🤔 Surely there's a way to manually add them with developer options?
@prologic I hope so. If there is, I haven't found it yet