Can you rephrase that?
I don't get what you try to say.
was that your opinion or did you rephrase for Taylor?
@taylorlorenz@mastodon.socia Don't let me drag you back in, but there are two federated (allowing connection to other instances) forks to the mastodon code that has search and quoting enabled
https://misskey-hub.net/en/docs/misskey.html
https://docs.akkoma.dev/stable/#what-is-akkoma
My suggestion is to look into both of these and see if they fix your issues. I really want to see newsrooms create their own fedi instances. Let us know what you think if you do look into them!
Enjoy the rest of the holidays!
@taylorlorenz @cspcypher That is the best solution, actually few clients support quoting and that patch for Mastodon too.
Here is an image example of intercomunication between an instance running calckey(that supports it) and my Mastodon: https://social.anartist.org/@4w4@animalesenfu.ga/109633054639694081
I believe the #whashingtonpost has enough budget and skills to launch its own #activitypub instance to satisfy most of their #journalist's needs.
@taylorlorenz The challenge with "followers only" is that if you have unrestricted follows, then ... the protection offered is pretty thin. A hostile actor could simply follow your profile.
I've long had mixed feelings on that setting. I'd rather it were restricted to a set of profiles I'd specifically selected myself.
@bhawthorne That's my general use.
In practice, I use it very rarely myself.
@bhawthorne I see people who seem to use it that way.
One thing that really bothers me is that the scope of replies to Followers Only is not the followers of the initial toot, but of the follow-up toot.
For people discussing personal matters and such, whom I know well enough to respond, I'll preferentially reply with a DM (which opens a whole 'nother can of worms), as what I say to them discloses both their conversation and any context visible from my own.
This is where the post/comment format of sites such as Diaspora*, Google+ (RIP), FB, etc., makes more sense: the conversational scope of the entire thread is that of the parent post itself.
I don't recommend Mastodon for anyone requiring robust tradecraft.
Personal "allow RT?" setting would completly end the argument.
Make it a per post choice even better.
@sri Not "unlisted", but "followers only".
"Unlisted" only keeps the toot off public timelines, and makes #hashtags unseachable.
That second is IMO a huge misfeature. Hashtags should be searchable by those within the posting context.
(Diaspora* works that way, and it's quite useful.)
Since I'm posting this as "unlisted", the hashtag above won't appear within a hashtag search.
@taylorlorenz What I don't understand about this Quote Toot argument is that a large fraction of toots are actually posting links to content offsite.
So what is the difference between dunking on Tucker 'Fascist boy' Carlson via a toot and using a Quote Toot?
It's one way that technology is part of the solution here in the #fediverse
Here, you can do this with, for example, Toot for IOS
@taylorlorenz@mastodon.social IMHO, this was the fundamental problem w/ QT on birdsite. Engagement maximizing algorithm selects for rage and pushes angry interactions to the top. Many of which used QT. It's different here . And we should be able to build a reblogging / quote-post capability that gives people control *and* fosters conversation.
@Nadinabbott @taylorlorenz
yes, we can quote client side like you did and I often do.
But it has problems:
* no link preview : the link to my post just sits there. No indication of what it's about
* Crossing instance boundaries. Click the link, can't interact.
* and most important, because this all happens client-side, I have no ability to control who can quote my posts. Which can lead to what @annaleen called "nonconsensual virality", the heart of a pile-on.
Let me put a phrase into your mind: nonconsensual virality. It's why quote-posts on Twitter led to harassment. People's words stolen, taken out of context, used purely to incite a mob of griefers. The answer is to give #Mastodon users control over whether someone else can quote-post them, with a simple "quote or not" setting that can be set before or after the post goes up. We should be allowed to stop people from taking our posts viral without our consent.
@koteisaev FYI, that's an inaccurate description of "unlisted".
An Unlisted toot:
An unlisted toot will NOT appear:
@taylorlorenz Before you get too attached to the view that "it can't happen here", you might want to look into the situation that emerged around Wil Wheaton in August 2018.
Wheaton was hounded off Mastodon by a group of griefers who'd followed him from Twitter. Bad handling by the moderator of WilW's instance contributed to that, but part of the problem was in fact an organised group hounding a specific individual.
Mastodon / Fediverse tools and practices have changed somewhat in the meantime, but the risk still exists, and you'll hear from many disadvantaged groups and individuals (e.g., #BlackMastodon) that the threat is real and present.