Migrated to @bhtooefr.
Computing, transportation, energy... really anything interesting.
| Web | https://bhtooefr.org/ |
| Alts | @[email protected], @bhtooefr |
| Pronouns | he/him |
If you follow me here, I've moved to @[email protected] and will only use this account as a backup.
Please follow me over there!
If you follow me here, I've moved to @[email protected] and will only use this account as a backup.
Please follow me over there!
@diodelass don't forget the fourth kind
the kind that twitter hasn't implemented yet, so Gargron doesn't have them as a source of inspiration yet
@Gargron wait
so when someone complains about a feature being deployed to RCs or release builds, you complain they should have said something on GitHub
when people say something about a discussion on GitHub, the medium that you've directed people to for discussion of future Mastodon functionality, you complain that the post was "basically internal communications between regular contributors"
something wrong here tbh
@pea tbh that actually sounds really fuckin' good
add some tomato soup, and yeah
@adamk678 I believe keyword mutes are a client-side thing only anyway
user mutes I don't believe are timed in any Fediverse software?
idea for Fediverse software: timed mute
mute a user, but only for a certain time period, with customizable permeability (for instance, maybe allow them to directly reply to you, but not appear in your home timeline)
this way, when someone's being lewd as fuck and you're at work, you can mute them and not forget to unmute them when you're no longer at work
(yes this is a subpost)
(and the specific user I'm subposting has suggested another feature that could deal with this equally well before)