Oh, do you mean the private voting issue?

If it helps, I had previously responded to some of the more controversial points that users had raised a year ago.

Honestly, you could probably lay out a dozen controversial decisions Rimu has made and I wouldn’t be able to pick which one I’m vaguely recalling.

I admit to being very wrong here - I thought, and even said publicly - that surely Rimu would reverse course and walk back that decision, as he had so very many others previously.

I thought so too.

He acts like Huffman, treating people as landed gentry on his platform. Which is… the truth!! Hence people have left it, and even more are choosing to simply go to it. Nonetheless, I truly do wish the best to the project… I just no longer have any hope that it will continue, most certainly not like it had in the past.

It’s his, but at the same time, being open source, it could very quickly not be (ex. Pylova). As long as there is a solid conversion path, Rimu could one day wake up and find .social is the only Piefed instance.

GET CREATIVE?!?

Rimu not only took away voting, and did so in a way that breaks the ActivityPub model - leaving users to scratch their heads wondering what error had occurred where the arrow turned green but the count did not change - but in response to why people were not allowed to vote anymore, he said to simply move on and do other things besides voting.

Yeah, his communication skills need significant work, which wouldn’t be so bad, if he was open-minded, but it really seems, as you’re saying, it has to be his way.

… the hidden, third option is simply to not engage with communities located on piefed instances anymore. And bam, just like that, communities such as [email protected] had their contributions drop like a rock (I skewed those stats a bit b/c I seemed to forget for a moment and submitted 6 posts before I remembered, as I tried out different 3rd-party apps to see what those experiences were like).

Absolutely. This is what I love about open source and federation. It may take time, but the ‘system’ routes around ‘damage’. Looks to me like Pylova may be the route around the Piefed/Rimu damage.

REALLY! That’s amazing! I would guess a migration over from Reddit. I hope they feel welcomed.

I guess from Reddit too. It’s been pretty consistently 100+ new users a day. Given instance “stickiness”, I’d say ~60% stick around.

I’ve seen a couple posts from newbies, the threads look really positive, there still is the allow/block triad conversation/fighting, but it was very minor from what I saw.

About downvotes, I misrecalled: Mia said that it was added to the to-do list to be added for the next release, although that was 3 months ago, and yet I have not seen it added yet.

If you haven’t seen her response, it’s appears to be a user toggle-able setting, which may turn into an instance setting.

There are a lot of “unfriendly” aspects such as this to the Fediverse. I see some people fleeing now because their instance went belly-up - off-hand I can think of mander.xyz and slrpnk.net and… at least one more that I cannot now recall the name of (their admin team simply listed a single account beginning with “The “, which at least at one point had not posted for years), all of which are having issues. Of course that is simply par for the course for the Fediverse model!

Yeah, it’s unfortunate, but I think it could also be an opportunity to figure out problems/frictions and solutions. I think for the worry instances go down, a few things would inspire confidence, for me. Off-site backup redundancy (data), a set up non-profit with financial transparency (finances), and a “succession plan” (admins: if admin people want to leave they can but there is a plan in place to hand things off and replace them).

But less necessary are those bot spam posts made ostensibly to make the place look more welcoming and active and alive - at first glance, but then those accounts (almost?) never respond to anyone’s comment, which sours people and leaves a negative impression of this place as being a ghost town.

Agreed. I think clearly labeling that this a bot post, could be good to feature. I still like seeing articles, even if I don’t want to comment on them. Maybe having them separated out as RSS feeds would be better though. I think something is happening with regards to RSS and Piefed, but I didn’t look into the specifics.

But… it is simply not worth the effort, when Reddit and FaceBook and Insta and X and Bluesky have REAL (high amounts of) content, so investing all that effort to learn and block what they do not want will yield significantly greater dividends… they seem to think, and by the mantra that “the customer is always right”, they are correct.

One thing I kept hearing from the new users this week, is how calm it is here. Like there is much less antagonism, insults, and rage bait and much more thoughtful discussion and nice interactions. So, I think, the threadiverse will hold some of the new converts until they learn how to curate their experience better.

Thereby if we want to attrack them more, we need to offer such blocking by default, making unregistered bot accounts either outright illegal or at least opt-in rather than allowing them to be opt-out.

Now I would put my hopes into the shareable blocklists to do such.

Yeah, I think “informed default” (like .zip), where the blocks are setup by default, but new users are informed about them and there is an easy way to disable them, if the new user chooses to, is a good path forward.

About your idea: I disagree. An admin that is hosting their own instance is different than someone who is simply using an existing instance. Such a person should have access to a “connectivity health” monitoring tool yes, but I don’t see why it would need to be on a per-post basis.

I mean as opposed to having every single post do this across the entire Threadiverse, at all times.

Anyway, I feel like an admin tool would be a better fit for that situation than changing the way that all posts federated all of the time - if I understood you correctly there.

It seems I may not have conveyed the idea well. So to try again, my understanding is that an instance sends to the appropriate “hosting instance” a post or comment. My thought is, if it doesn’t already happen, have the “hosting instance” send an ‘acknowledgement’ back to the sending instance. Then, if the comment has been ‘acknowledged’, the sending instance would put an indicator on the comment (check mark or something) to show “yes, my user, your activity successfully arrived at it’s destination.”

In my mind, this wouldn’t be every instance checking every other instance’s user’s activity to make sure it federated properly. This would be an instance confirming things for only its own users.

For instance if I make a post to [email protected], even as a mere user (not an instance admin) I can go over to that instance at https://lemmy.world/c/fediverse/ and look for my post there (similarly for comments). I have routinely done that many times in the past, especially from StarTrek.Website that had such horrible network connectivity at the time that I joined it, prompting me to seek out Discuss.Online that has such fantastic uptime due to spectacularly capable admins (including Jgrim the author of Sublinks).

Previously though, I would likewise post something and then getting zero up- (or down-) votes, go seek out why, and discover that my post had not federated. Worse, when it eventually did get federated, it did not appear to others as “new”, and instead looked like it had been submitted several days in the past, at which point people were not alerted to it, and it became buried amidst all the flood of prior posts that had already been engaged with, even though those had not been. It was quite sad, how bad the connectivity of the Threadiverse was 3-4 years ago:-(. These days it is a LOT better!

I’m think the feature I’m suggesting would do away with this “federation uncertainty friction”. I rarely go to check other instances to see if my comment or post has federated or not. I’m usually on mobile and this is not an easy maneuver, so I often have a question if my post/comment federated or if I’m only talking to myself. Not a great feeling and definitely reduces the urge to contribute, for me.

I just checked the post I made to the [email protected] community yesterday, did not federate (https://programming.dev/c/Servo is missing my post). Glad I spent time on that post… :(

I think the “acknowledgement” feature could also help elevate the issue entirely. I’m not sure how to ‘force’ a re-submission of my post, but if an instance didn’t get an ‘acknowledgement’ the instance could check that the '“hosting instance” is still receiving and then try resend the post/comment after a certain time interval.