# 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 10
# self = https://watcher.sour.is/conv/mkfgfeq
Thank you Mozilla, you bloody &%$&"/§%("). After removing the ability to switch the character encoding and replacing it with an always disabled "Repair text encoding" menu item, I had to install this third-party Override Text Encoding extension.
@lyse Makes you wonder why this feature was removed. Not used by people? (Then why is there a “Repair text encoding” now?) Or was it “too complicated”? Would be interesting to dig up Mozilla’s ticket for this task (assuming it exists and is public).
@lyse Makes you wonder why this feature was removed. Not used by people? (Then why is there a “Repair text encoding” now?) Or was it “too complicated”? Would be interesting to dig up Mozilla’s ticket for this task (assuming it exists and is public).
@lyse Makes you wonder why this feature was removed. Not used by people? (Then why is there a “Repair text encoding” now?) Or was it “too complicated”? Would be interesting to dig up Mozilla’s ticket for this task (assuming it exists and is public).
I had the same thought. Why remove a useful feature? We're there analytics showing no usage? 🤔
I had the same thought. Why remove a useful feature? We're there analytics showing no usage? 🤔
@movq @prologic When searching for a replacement I came across somebody telling, that nobody used it and it shouldn't be needed anyways, so they removed it and put a half^Wfully-assed implementation in place. Can't find it now. But I found this bug report that is linked in the addon's readme and also an article by the same guy opening the bug report. I haven't read any of them.
@lyse Hmm, this says:
> > Can We Replace the Text Encoding Menu with a Single Menu Item?
> Most likely yes […]
But there are a lot more factors at play than just telemetry. 🤔 Haven’t read through all of this, either …
Apparently, the autodetection was deemed “good enough” to remove the manual selection?
I still don’t understand why the menu item is disabled. It’s even disabled on plaintext files. So … ? 🤨
@lyse Hmm, this says:
> > Can We Replace the Text Encoding Menu with a Single Menu Item?
> Most likely yes […]
But there are a lot more factors at play than just telemetry. 🤔 Haven’t read through all of this, either …
Apparently, the autodetection was deemed “good enough” to remove the manual selection?
I still don’t understand why the menu item is disabled. It’s even disabled on plaintext files. So … ? 🤨
@lyse Hmm, this says:
> > Can We Replace the Text Encoding Menu with a Single Menu Item?
> Most likely yes […]
But there are a lot more factors at play than just telemetry. 🤔 Haven’t read through all of this, either …
Apparently, the autodetection was deemed “good enough” to remove the manual selection?
I still don’t understand why the menu item is disabled. It’s even disabled on plaintext files. So … ? 🤨