Adam Snider @ink_slinger@mastodon.social

Open source maintainers should diffuse responsibility early, and often. Add new contributors, give contributors push rights, empower existing contributors to keep contributing.

It's hard, because we start open source projects usually because we like to write code for them. But once it becomes a community, our priorities need to shift from coding to helping others code. It's uncomfortable.

When you break the bloom you should see the volatile parts reacting. https://mastodon.social/media/5w41gP_5BIBagYqPtpo

Emergency alert. I need more coffee. End message.

Everyone on Pawoo seems to be very conscientious about tagging and CW usage for the sake of others. Even if it's a stereotype, it reinforces my notion that Japan is built on manners and consideration for other people.

Aside from that, the other positive outcome of the confusion of Loligate: I think I now have a much wider understanding of Japanese terminology regarding erotic sub-genres. lol

Pro-tip: To get web-UI to remember where you left off in the timeline, make sure your scroll bar is not pegged to the very top.

I can scroll all the way to the top, for example, and just click the down-arrow exactly once (or move knob down a few pixels). This is sufficient to get web-UI to not relocate your place in the timeline.

hey guys we already live in a dystopia just fyi

The increasing I'm-switching-to-node-X toots are both a sign if the fediverse working as intended (as like-minded users flock together), but also shows that key functionality is still missing (handling instance-migration silently and transparently)

12. You have to leave an unsolved problem in the hands of the users, so that their interaction with the network takes the form of exploring/looking for things, and solving the problem themselves. It's a center of identity and intrigue that will draw people in.

I don't think Mastodon needs to have a "universal" search or solve its fragmentation problem. That can be what the users do: curate, discover, explore. Letting them exist in space of unsolved problem also gives vision of possibilities.

11. Back to Mastodon: I like it for the dumb and dead simple reason that it has a solid interface and it's more or less clear what it is. It's branded well (or at least well enough.)

Can you look at Synereo's site and explain what it even is? I can't.

Diaspora just doesn't have the magic.

Twitter worked I think in part because it has too much, so you have to curate, and it feels like exploring.

I think there's a similar dynamic with mastodon and federating to different instances.

I'll say this: choosing an instance is not just about the domain name, it's about do you trust the admin and what is this instance culture and _how does this instance enact that culture_, and circumscribing a non-toxic universe is a perfectly valid way to define a culture.

Oh, hey, Mastodon makes the same UI mistake I once made in Mailpile! It updates the display while I am interacting with it.

This causes the time-lines to jump, annoying me at best, causing bogus boosts/stars at medium bad and accidental decloaking/downloading of nasty/illegal/triggering content at worst.

That explains why I've boosted the wrong things a couple of times.

Ah the inevitable "no *you're* doing it wrong" phase of FOSS projects.

My thoughts? I like instances that set tone by blocking the ones they won't work with. I like instances that show full throttle shitposting from wherever because sometimes there's a nugget in the crap.

That's why I have accounts on multiple instances.

hello friends if you really want the loli content and are angry w/ the actions of your isntance's admin, just move to another instance?

like iunno why people on unrealted instances are bashing the actions of instance admins that are trying to not go to jail for hosting content that is illegal in their country

like, to be honest, my main issue with the shared instance block lists is not that they exist, but that:

(a) they are not sourced with any of reason for why you should block them,
(b) some of these instances don't really have good reasons for why you should block *everyone* on them,
(c) some of them are nonsensical because either they're misspelled, or Mastodon can't federate with them anyway,
(d) despite these issues, people are encouraged to import them anyway For The Good Of The Users,
(e) unintended consequences could happen if every instance just adopted this list; whoever decides what gets on it controls a large part of the fediverse.

tl;dr: outsourcing this decision-making to someone else without review is a really bad idea unless you really trust them