{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}

@stpaultim @roadriverrail Whereas I think it sends a pretty good message: users have the power to push back on devs *hard* and you had better incorporate community-driven design processes instead of just coming up with stuff and doing it. Or as the brilliant mcc@mastodon.social said (don't want to spam her):

"Maybe programmer people need to figure out a clearer division in their heads on the difference between experimenting with software and experimenting on people"

2
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Darius Kazemi

@stpaultim @roadriverrail And btw I am not one to shy away from this: I will be implementing quote-posts in Hometown, my Mastodon fork, but I think crucially the way I am going to do it will involve a lot more community input and transparency than basically any fediverse feature to date.

This is why it has taken me years to implement it: the tech hasn't slowed me down, I needed to figure out the right process for introducing and getting feedback

1
2y
Jay

@darius @stpaultim @roadriverrail Regarding #search, an implementation I would LOVE to see (and ASAP, to redirect energy from other possibilities) is #optIn full-text indexing of public (and unlisted) posts via a bot that follows back anyone who follows it (which I first saw suggested in bentasker.co.uk/posts/blog/sec ). I don't want to implement it myself, but I'd use it, and I've been telling everyone I can think of about it, in the hopes that someone else will.

0
2y
Replies