NotTheOnlyGamer

joined 1 year ago
[–] NotTheOnlyGamer@kbin.social 1 points 6 months ago (1 children)

Preventing this issue doesn't seem like a userscript issue (though that's definitely a good start).I think the auto report function is severely needed; it's happening everywhere. If the script can automatically block any user whose post it suppresses, it would be awesome.

But I think the issue is that we need to get support top-down on this.

 

Is it just Kbin, or does every fediverse service have the issue of being totally swarmed with bots advertising illegal pharmaceuticals? Is this just the result of limited moderation?

#fediverse

[–] NotTheOnlyGamer@kbin.social 3 points 9 months ago (6 children)

Maybe on your instance - it's your loss. But admins have a choice - defed from them and lose access to all those users and having actual content worth looking at, or federate with them and actually grow your network into something that has enough going on to make people interested. As it is, I use Threads right now. I strongly prefer it to Mastodon. Kbin comes close, but has less content to idly scroll through. If no Fediverse site I use supports Threads, I'll keep on using it.

[–] NotTheOnlyGamer@kbin.social 2 points 10 months ago

That's fine and all, but I have one question. Why would you want to want to revisit the biggest video game scam in recent memory?

[–] NotTheOnlyGamer@kbin.social 1 points 10 months ago

The best possibility is something like I've done. I split my social media time between here, Reddit, Facebook, Threads, and a Mastodon instance that doesn't federate (in addition to being a viewer on YouTube & PeerTube). You can't hold all the people all the time. It's just not feasible. So yes, people going back to Reddit is expected. But it's when they come back and find something they want that's important.

[–] NotTheOnlyGamer@kbin.social 2 points 10 months ago (1 children)

I'm going to present the opposite opinion to yours here. Kbin represents the best way forward for social media, to me. If we can get a working PeerTube integration after Threads federates, I'm all set. It's what Google Plus was supposed to be, it's why I first (as a user) used TweetDeck back in the day. It puts everything in one place again. I was a LiveJournal user back in the day, which was another place like this - communication & community, but individual places for your thoughts. I tried Tumblr for a while and it was close to an LJ replacement.

Everything since then has fractured and fragmented so we have very aggressive echo chambers, but no private places. This might be able to give that back to the users.

I accept that it can feel like drinking from the firehose at the start. It was to me at first too, but I was aware of Lemmy early on, and I was on two Mastodon instances that didn't cofederate. I knew what I was going in for. I stepped back from Kbin when a known tech issue degraded my experience, and it's been fixed. I think the thing is that Kbin allows you to curate your own experience, rather than be tied into doing one thing or another all the time.

I think when Kbin is ready for prime time and when the major issues are fixed, there might be a need to look at the first-timer experience, maybe even a tutorial. Because it's not a beginner focused interface. It's meant for us who want it all back in one place, and accepted the burden of experience that means.

[–] NotTheOnlyGamer@kbin.social 1 points 10 months ago

I'm not at my computer, so please excuse any mobile issues. I'm in favor of the move, because it will help to simultaneously connect and decentralize communications across the platforms. Say what you will about Facebook (you're probably right), but if they're that bad, then it seems logical to me to connect to their federated service even more aggressively.

The more we push our content (and by extension the Fediverse content that kbin aggregates), the less impact their algorithm can have. The more we go out of the way to expose their content, the harder we make it them to curate/censor/suppress any voices. And if, when comparing two Fediverse instances or softwares, we find that what's been pushed to them is different, we the users can call it out to news organizations (or make it public ourselves).

And yes, I know I'm making the arguments for supporting private companies in adopting open-source. It's about being able to audit what companies we don't trust are doing.

In addition to that, I'm currently a Threads user. Anecdotally, there's a lot of wholesome content on there that I appreciate, and what limited advertising is there is nowhere near as obtrusive as Reddit or the main Facebook platform.

[–] NotTheOnlyGamer@kbin.social 2 points 10 months ago

Pitchfork being on an alternative social platform just feels right to me. So I say, go for it.

[–] NotTheOnlyGamer@kbin.social 1 points 10 months ago

Well, if he doesn't care, then I just might bother the time and effort to pirate it. But then again, a dismissive creator who's working with Markiplier isn't someone I'm really keen on supporting in the first place. I wish him luck, and that he is approximately as successful as I am in financial terms.

[–] NotTheOnlyGamer@kbin.social 1 points 10 months ago* (last edited 10 months ago)

Because Threads presents an opportunity to grow the community on ActivityPub services, and because the Fediverse presents the opportunity to extend the community I'm involved in that's on Threads right now. My hope is that if that group respects what the Fediverse offers, they will also start sharing the podcast on PeerTube

[–] NotTheOnlyGamer@kbin.social 1 points 10 months ago (2 children)

My hand is raised.

[–] NotTheOnlyGamer@kbin.social 1 points 11 months ago

I find it interesting that they didn't suggest the possibility that came to my mind first: cannibalization. If it was small to start with, but in clearing the neighborhood, also was volcanic enough to absorb smaller planetoids, it might have absorbed them and grown.

[–] NotTheOnlyGamer@kbin.social 1 points 11 months ago

I'm getting back into Digimon World: Dawn recently.

view more: next ›