# 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 12
# self = https://watcher.sour.is/conv/elgkv5a
hacker-news
feeds.twtxt.net
View Thread
SHUT THE FUCK UP. WE DO NOT BREAK USERSPACE!
Comments ⌘ Read more
ullarah
txt.quisquiliae.com
View Thread
Must have been having a bad day…
movq
www.uninformativ.de
View Thread
@ullarah Management by perkele. 🥴
movq
www.uninformativ.de
View Thread
@ullarah Management by perkele. 🥴
movq
www.uninformativ.de
View Thread
@ullarah Management by perkele. 🥴
prologic
twtxt.net
View Thread
da fuq?! What'd I miss here? 😅 All I saw in the context of this Yarn was:

> SHUT THE FUCK UP. WE DO NOT BREAK USERSPACE!

LOL 😂
prologic
twtxt.net
View Thread
da fuq?! What'd I miss here? 😅 All I saw in the context of this Yarn was:

> SHUT THE FUCK UP. WE DO NOT BREAK USERSPACE!

LOL 😂
prologic
twtxt.net
View Thread
Oh 🤦‍♂️

> Mauro, SHUT THE FUCK UP!
>
> It's a bug alright - in the kernel. How long have you been a
maintainer? And you *still* haven't learnt the first rule of kernel
maintenance?
>
> If a change results in user programs breaking, it's a bug in the
kernel. We never EVER blame the user programs. How hard can this be to
understand?

----

The thing is I alway agree with Linus's stance here, if you're the custodian for a thing you should not break that thing for your users, no matter what. It's just common fucking sense 😅
prologic
twtxt.net
View Thread
Oh 🤦‍♂️

> Mauro, SHUT THE FUCK UP!
>
> It's a bug alright - in the kernel. How long have you been a
maintainer? And you *still* haven't learnt the first rule of kernel
maintenance?
>
> If a change results in user programs breaking, it's a bug in the
kernel. We never EVER blame the user programs. How hard can this be to
understand?

----

The thing is I alway agree with Linus's stance here, if you're the custodian for a thing you should not break that thing for your users, no matter what. It's just common fucking sense 😅
prologic
twtxt.net
View Thread
It's not just a "Kernel" thing, this applies to any product, hardware, software, whatever. If you break shit, then blame your users and say it's "their fault" you just look stupid 😅
prologic
twtxt.net
View Thread
It's not just a "Kernel" thing, this applies to any product, hardware, software, whatever. If you break shit, then blame your users and say it's "their fault" you just look stupid 😅
eaplmx
twtxt.net
View Thread
> And you've shown yourself to not be competent in this issue, so I'll apply it directly and immediately myself.

👀 "Move away stupid, I'll do it"