Soni L.

sure we guess

can one use machine learning for this? I still think the warning should always be shown, regardless of autoplay settings, making it visible to ppl who wouldn't notice it otherwise.

... we don't need that. we also don't need to give ppl seizures. there's plenty of material out there that ppl have deliberately created to give ppl seizures. there's plenty...

that'd be a good separate feature request.

at least ppl would stop demanding other ppl to put things in the CW box when they can just use a filter.

it would mitigate it because you can't complain about ppl not using a feature that doesn't actually exist. so that's a whole class of racism just gone. simply by removing...

ppl who make social networks, be they developers or admins or whatever, are social engineering. if they don't recognize as such they fail to acknowledge their responsibilities, and thus cause...

indeed, that's where keywords (or tags) come in handy! they can be filtered out as needed.

systemic issues call for systemic changes. how do you propose doing that in a systemic way?

`$XDG_CONFIG_HOME/luvit_history`, or, if `$XDG_CONFIG_HOME` is unset or empty, `~/.config/luvit_history` (as described in spec). Example code (untested): ```lua local config_home = os.getenv("XDG_CONFIG_HOME") if config_home == nil or config_home == "" then...