Show newer

dansup 

if someone who was anything other than a cis white man pulled any of this stuff off they would have long been cancelled and their project dumpstered

Cool that you're sharing a CIA manual about disrupting orgs, now share Riot Medicine with that same "just in case" energy you weirdos

riotmedicine.net/

@fogti@chaos.social The codebase it's used in will be open-source/published at some point, but it's a bit difficult to extract right now (because it integrates heavily with the styling in the rest of the project).

The description above should be all that's needed to replicate it, though, aside from the styling and exact positioning (you'll need a top and left margin of -1px in some cases).

I might get around to creating a simplified example at some point, but probably not tonight anymore.

Also, if this sounds like some cursed early-2000s browser compatibility hackery to you, you would be correct, because that's absolutely where I learned how to figure out tricks like these 🙃

Show thread

@Curator I would prefer the second answer given these two options, but I also think it's too narrowly defined - I consider *agency and consent* the most important thing, and safety and moderation tooling is a part of that, but so are specific features (like personal customization).

Ultimately, to me, it's about giving people the tools to control their experience and make it their own comfortable community space.

as someone who has been trying to organize for social change my entire adult life i have to say the thing that absolutely frustrates me the most is how people feel entitled to receive organizing without passing it along to the next person

if i could teach everyone a single thing about organizing, it is that it only works if you ensure a given action doesn't die with you, you have to take just a few extra minutes to ensure others pick it up and keep it going

@lily Yeah it took me a good while to figure it out as well, probably a few hours - I made a lot of attempts at 'breaking out' the content element from the details element, which went nowhere, until I eventually realized that all I needed to do was reserve the right amount of space 🙃

Own a domain. Put a blog on it. have your own e-mail address you@yourdomain, even if it is just a forwarding address. Own your digital identity. If you need help with that, call me, message me, meet me or one of thousands of others who already are doing this. It's our internet, if we act accordingly. Don't be afraid!

Show thread

"Everyone is failing! Someone must _______ immediately!"

Comrade I don't know how to tell you this in a non-asshole way, but "someone" is *you*. That's where we're at. Find people doing the work you want to see and help them.

Meta, garbage techbro quote 

'I care about user counts because a social network is only as useful as its network effect.'

>.>

Welcome this episode of "Ask Mastodon".

I'm looking for a good web based RSS reader.

1) Web based
2) Not Feedly
3) Not self-hosted
4) Not filled with AI bullshit

Please read criteria carefully before replying.

I *really* didn't want to stuff the menu full of fully-rendered forms for different operations, hence needing a popover that only asks for details when the user actually wants to take a particular action

Show thread

Good morning! On this first Tuesday in February, you are all invited to read through Wikipedia’s List of common misconceptions (en.wikipedia.org/wiki/List_of_) per ancient xkcd custom.

#xkcd #xkcd843 #misconceptions #Wikipedia

Also, the 'cloned' text in the wrapper element is in an aria-hidden element, of course; I haven't quite figured out the correct ARIA roles for the expanding button (given that it's kind of a button but also kind of a summary). Suggestions welcome!

Show thread

TIL that the reddit community "Eyebleach" is about sharing cute things to cleanse your eyes / psyche, not about posting things that require you to cleanse your eyes / psyche / take psychic damage

The trick is that the <details> is contained within a wrapper div with identical styling to the <summary> (ie. the 'button') and identical text contents, except the wrapper div is invisible and position:relative, with the <details> being position:absolute and anchored against the wrapper's top left corner.

This means that the wrapper essentially 'reserves' the space for the button, while the <details> element can freely expand without disrupting anything because its absolute positioning takes it out of the content flow

Show thread

@rtn@chaos.social The ongoing saga where they insist on digging deeper and deeper in their accusations against GtS developers, conveniently omitting the part where they were ignoring the robots.txt, while continuing to boast about how much they're personally doing for the Fediverse (which they're really not)

A lot of CSS hackery later, and I've managed to construct a popover dialog using a <details> element that doesn't disrupt the button order and also doesn't require any JS to work!

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.