

Probably would have missed it. Appreciate the tag :)
How votes are viewed is a user setting, letting anyone choose if they want combined, separate, or a percentage. Is this something you would also like settable as a global instance default choice?
Honestly, as long as I can easily enable it, it doesnāt matter to me if everyone has it by default (only viewed your instance without logging in). Might be worth a user poll, but I have no idea how wanted that feature is.
FYI I altered my [FR] on Codeburg to reflect youād already implementing the feature.
We mostly use Grafna
Link doesnāt work, but I think I know what itāll look like.
Given both your responses, it seems I didnāt conveyed the idea well to OpenStars. 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.
Hopefully that makes sense. I graphical up-time graph is probably nice to have too. I was going to say those are available on fediverse measurement sites, but with a quick look, it seems like that was a Fediverse-Observer (RIP) only feature.
Also I occasionally search for PyLova and I love reading this comment chain when I do, thanks for contributing so many ideas.
Happy to help and thanks for being so responsive, open-minded, and just all around great :)
Edit: when making my comment to OpenStars, I checked a post I made to the !servo@programming.dev community yesterday, which did not federate (https://programming.dev/c/Servo is missing my 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.
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 thought so too.
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.
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.
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.
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.
If you havenāt seen her response, itās appears to be a user toggle-able setting, which may turn into an instance setting.
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).
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.
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.
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.
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.
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 !servo@programming.dev 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.