| Follow requests | May well accept if you look vaguely human, am mainly filtering out bots/spam |
| Corollary | (Hence: won't participate in sensitive followers-only conversations) |
| Boosts? | Fine by me |
| Follow requests | May well accept if you look vaguely human, am mainly filtering out bots/spam |
| Corollary | (Hence: won't participate in sensitive followers-only conversations) |
| Boosts? | Fine by me |
@bocs I kinda wonder whether it could somehow be related to VFAT long filename records from previous files with these names, possibly manipulated by some other LFN-aware system?
I don't know enough about the design of the LFN bodge to know if this is plausible, but I do remember some other embedded implementation (Xilinx?) choking if you had ever used actual-Windows to create a non-8.3-all-uppercase filename on its storage (and I presumed the cause was LFN records).
https://en.wikipedia.org/wiki/Design_of_the_FAT_file_system#VFAT
We want to hear from all workers who can speak to changes your employer has made to their policies or practices related to trans inclusion following the Supreme Court judgment. We must show the government the real-world impact on trans workers if they do not act quickly to fix the outdated regulations that mandate trans exclusion.