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

@stpaultim @roadriverrail I specifically was an informal advisor on Searchtodon (having been internet friends with its creator for about a decade), and I thought it was an interesting project, and I think it was misunderstood, *and* I think it would have been better as something hosted by instance admins where people could fully defederate from servers that use it.

2
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Tim Erickson, @stpaultim

@darius @roadriverrail

I agree. I was not involved and do not know the people directly involved.

I also think it was misunderstood and an opportunity was missed.

I appreicated the developers attempt and his documentation of what went wrong and how it might be improved in future atttempts.

Sure, there is a lot developers can do in the Fediverse that would be welcomed.

But, I think that the #Searchtodon incident also sent an unfortunate message to developers.

2
2y
Laurence Gonsalves

@darius @stpaultim @roadriverrail

Requiring that features be 1-to-1 with instances seems pretty far from ideal, though. Instance selection is ostensibly about finding a community of people with similar interests — why would that be correlated with whether one wants the ability to search their timeline or see quote boosts (for example)?

And on the flip side, are people really going to keep track of the full feature-set of every instance of their followers so they can block/defederate instances with features they object to — especially features that are only visible to users of said instance?

0
2y
Replies