".@peterktodd never followed me on Twitter, but now that I'm on Bitcoin Mastodon I guess that I've become cooler." @vladcostea 😁
Though seriously, it's interesting how the lack of AI will change following patterns. On Twitter lots of people will end up in your feed due to The Algorithm, reducing incentives to actually follow.
@pete I think we're also dealing with the issue of abundance vs scarcity. When your feed is already oversaturated and you get all the views that interest you, you'll think twice before following someone new.
But when the platform is rather small and it's just taking off, it's likely that everyone will follow the newcomers just to establish the community. Soon there's going to be plenty of time for fighting and blocking 😂
@vladcostea That's a good point too.
Speaking of, I think we'll need to get some arguments going to actually get Mastodon off the ground. It's a bit of a dark pattern, but endless debate is what gets a lot of people hooked on Twitter. Also, watching others endlessly debate.
I am noticing Mastodon is decent at getting other communities visibility. At least with the client I'm using.
@pete @vladcostea Definitely something I've noticed - this place puts a lot more info feed curation power in the hands of its users compared to twitter, so people seem to be less aggro at each other because they're not constantly put in each other's faces.
@kekcoin @vladcostea of course, will that continue to work out if Mastodon gets flooded by bots? Remains to be seen.
@pete @vladcostea I vaguely remember @nvk banning shitcoinery from this instance, though those rules seem to be gone now. Not sure if that was on purpose. It did make it a lot easier to just block entire shitcoin-friendly instances and not deal with those bots.
@vladcostea @kekcoin @nvk gotta get your own man! Pretty point n click with their premade digital ocean vm.
@pete @vladcostea @nvk It can be pretty good to be on a busier instance though, especially if it aligns with your interests. Easier to discover new people and things that way, through the federated timeline. Of course you do have to filter some shit out.
@kekcoin @vladcostea @nvk From the looks of it going to public feeds on other instances works reasonably well.
Also, client seems to be able to pick up stuff from elsewhere to a limited degree. Not sure how it all works exactly on the backend.
