@nicksellen oh, it is a shame that crossposting is this frowned upon. I've been enjoying using moa.party, and I think that it adds value to the ecosystem as it boosts the visibility of the fediverse elsewhere.
I try to be responsive here of course; I basically alternate between tusky/pinafore and Twitter when I check out social media. My 2c is that crossposting, done responsibly, is likely a net win for the fediverse. Wdyt?
@nicksellen the way I think about it with good crossposting Twitter converges to yet another fediverse client and brings the fediverse into full view of a greater audience, potentially siphoning users away from Twitter at some rate.
@flancian I'm not opposing crossposting in general, just sharing my request that those accounts be marked as such, and that I can get a better idea if it's worth replying to a toot (it's not clear if replying to a crossposted tweet will engage the author).
Having crossposting accounts seperated means I can then choose to mute them, but the person can still interact directly on the fediverse too. Right now I have to choose, either mute their crossposting activity AND direct activity or neither.
@flancian I'm also not very interested in connecting to the great masses on twitter. My personal preference would be allowlist-only federation actually. A smaller more curated fediverse.
@flancian I wonder if allowlist federation for all of the fediverse would be a better default. The length of the blocklists that go around seems to get unmanageable at some point.
I, and many others, aren't here to have conversations with the entire world. The burden of moderation is crazily high in that case, it doesn't seem to scale.
I'd be quite happy to interact with a small set of curated instances/people (like in physical life). Dunbars number perhaps.
@nicksellen right -- that makes sense. I, on the other hand, am here to make as many acquaintances as possible, and tend to post in fully open/broadcast mode :)
I think the network should support both use cases; but I wonder if your profile and mine actually would fit better in two separate instances.
Is there a default @social.coop position in this spectrum?
@nicksellen @flancian yes, the possibility of auto-server discovery (admins get notifications "this server exist") coupled to whitelisting ("do you want to federate with it?") has been mentioned a couple of times as a possible alternative to current situation.
I'm rather in favor of it, especially if coupled to an additional feature that would let local users see those notifications and vote on whether they'd like to federate.
I'd like to comply with your request in spirit as I think it'd be the maximally respectful thing to do, but I see two issues with the proposed alternatives:
1. marking my account as a bot is just not correct in this case as I'm not a bot -- at least half the time :)
2. having a second account would fragment my online identity and impose an awkward burden on me and others.
@flancian I already muted you :) ... but kept the notifications on, so if you mention me I still see it.
We have a gridlocked set of needs here, well muting is fine for me. I try and not read too much stuff online anyway.
@nicksellen oh, a shame! I think we probably left some cooperation/compromise opportunities on the table here; happy to revisit anytime.
I'll run a poll to see if this is a common concern that others have and revisit myself if so.
Have a nice day!
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!