pink-after-hours

Pink After Hours

gooffin' around & shitpostin'


frieze
@frieze

So I know of
dividend ÷ divisor = quotient
and also
multiplicand × multiplier = product
but I came across the word augend and was like wtf. turns out there's also
augend + addend = sum
and
minuend - subtrahend = difference
blew my mind. firefox is even telling me augend isn't a word




sirocyl
@sirocyl

my thought, is to include a flag on the post, alongside CW/18+ post-hiding, for third-party media. See the UI example in the image above.

This is set by the server-side HTML analysis/sanitizer engine whenever any URL is serving content (e.g., image links in CSS, SVG or <img> tags) that doesn't originate from cohost's servers by DNS match.

If there were a way to show/list which third-party servers were in the post content before opening the post, perhaps through a button in the warning header, that'd be even better.

When a post contains third-party content, it is:

  • hidden by default, doesn't render, doesn't preload assets
  • gives the same "show post" UI as a CW/18+ post, but with succinct privacy prose about third-party content and the user connecting directly to a third-party server, addresses or whatever
  • has an option in user settings to expand these automatically; default disabled.

Just to be clear, I'm against the suggestions to disable third-party content outright, including:

  • completely disable inline content embedding, let alone 3p content (this has been used in the past for extremely cool stuff, and is a big part of what keeps cohost unique)
  • download and cache or re-serve images from cohost's CDN (this is, for reasons, unsustainable, and also breaks cool things done with off-server images)
  • require embedded content only source from cohost's CDN - uploading to it is janky and this also breaks "cool stuff"

however, I am positively for an easier way to upload normal images to Cohost to be used, embedded or referenced inline, that doesn't involve writing a dummy draft post.


pink-after-hours
@pink-after-hours

If you want to acutally make this properly secure' then client side sanitization is a must. Bowsers all vary' and it just takes one bowser to have a unexpected way of parsing the content.



slimelia
@slimelia

people are hating on @predstrogen for "bringing tumblr attitudes to cohost" and it's just fucking dawned on me that was the exact thing people said when i was The Discourse Of The Week on here. and that was over a fucking Twitter-themed CSS post generator.

didn't even cross my mind once at the time but now i cannot fucking help but reevaluate the backlash i got. how much of the issue was me "bringing Twitter vibes to Cohost" and how much of it was a style of posting you didn't like from a gobby tranny who didn't match the vibes but still gained traction??

either:

  1. people on cohost fucking hate trans women
  2. people on here are so concerned with maintaining the "Vibes" of Cohost that they're willing to repeatedly make trans women feel alienated

and i'd honestly rather it was point number 1. at least then it's just straight-up transmisogyny. but it's looking more like point number 2: a lot of people on here value ~Vibes~ over, y'know, actual real people. Vibes are more important than *checks smudged note* Tranned Womens