silas

im silas

queer transfag furby. 30 years old. world's #1 yeti a love story fan. @prophetesque look at my furbsona.
💕@lazer 🪄 🖤 @cerpin
🫀 @Lucille

last.fm recent played

furbycock sucking faggotyou make a terrible god luigihand painted
gilbert baker pride flagtrans flagpolyam pride flagautism acceptance now!
from the river to the sea palestine will be freethis machine kills fascistsdefund police now!better a tranny than a terf


ebu
@ebu
Oh?
Interactive posts?
On my Cohost?
With light mode support!?
With dark mode support!?
It's more likely than you think.
Thanks to @blep's prechoster...
I can keep this going.
As long as I want.
Or, at least until I hit size limits.
Though, text is quite efficient, bytes-wise.
(Even if styling all this brings a lot of overhead.)
As you might can tell...
I've had visual novels on the mind recently.
(Thanks, Echo.)
Anyway. I won't hold you for long.
Catch you later~
-ebu

@silas shared with:

You must log in to comment.

in reply to @ebu's post:

This is not to throw water on this cool thing, but just in the interest of further data: on my screen-reader, it reads this post from whichever point you've clicked through, backwards up the chain, and then moves on to comments (or the next post if on a feed) without going further down the (downpointingarrow) chain. So, to get all the text, I tap through it all and then have it read all the sentences! ...just in backwards order.

Very neat interactable effect! I've only seen the posts made with ravel, rather than this prechost tech where the previous message disappears.

i've futzed with the underlying order of elements -- hopefully they should read out in the correct order now. i had shuffled them around to get things to line up visually, but didn't fix it back for screen readers.
i've also added a tabindex for the last line, since it appears that it gets completely skipped by screen readers if it doesn't have one.
though, it is entirely possible i just don't know how to operate screen readers.