The domain https://fediverse.observer/ redirects to sedo now.
On October 11th these two commits where made to the repo:
this will be my final release, glad to have contributed since 2011 to some fediverse stats, https://fedidb.com/ is a great resource with more interest
this software is no longer developed
Sad to have lost such a great resource.


Awesome! Upvoted :)
While I agree that would likely help new comers, I suspect the .zip admins have a similar thought process to Rimu (not antagonizing the Lemmy Devs, and keeping the lines of communication open in case there is an software issue).
I agree and block trolls immediately (“Don’t Feed Trolls!” is my motto online).
I thought previously a subscribe-able block list would be a great addition, at the user and/or the instance level. Users or instance admins could create a list of problematic users and/or communities and any updates automatically feed to the subscribing instances or users. Obviously issue is who gets authority to amend a list, but I think if the list was in a standard format and “forkable” it wouldn’t be too big of an issue for different groups to easily create and maintain their own lists without much issue.
This could be away to block the worst offenders/trolls without risking antagonizing the Lemmy Devs. Thoughts?
I don’t think we are “comfortable being a troll bar”, I think we are uncomfortable and taking steps, unfortunately slowly, to move past that phase of development. With ~80% of the Threadiverse on Lemmy and the Lemmy.ml admins being the Lemmy Devs, I think things have to move slowly (boil the frog slowly). There’s no way (to my knowledge) to switch instances to an alternative software (Piefed, Pylova, Mbin), so all the Lemmy instances are a little bit held hostage. I don’t currently see a way out from the hostage situation, but perhaps one will present itself in the future.
In the meantime, like you are saying, I don’t think that means things can’t improve with on-boarding or initial blocking for new users, to continue moving away from being a “troll bar”.
I love this idea. Topic Feeds are already user-customizable and shareable, so why not block lists? And while I haven’t read through it yet, see also supersquirrel’s recent post (last day or two) on the topic in the Fediverse community iirc, saying similarly for Mastodon. Admiral Patrick’s toxicity filter went behind people’s backs and did such opaquely, but when handled transparently and with full informed consent that would be an entirely different story. And then people could choose like no filter, minimal or maximal filtering, or perhaps some intermediary steps between those.
Some issues remain, like instance blocking does so without informing the recipient, who gets essentially shadow-blocked by the recipient. But that is not something fixable by PieFed alone, and would require cooperation with Lemmy to receive the signal and pass it on to the affected users in whatever way they chose.
It’s been like 3 years. I for one have lost hope, especially now that we are well past the era of Reddit enshittification. We cannot rely on future Redditors to come over anymore, and therefore where else are users likey to arrive - Instagram? Tiktok? Anyway, if anything happens, then I will believe it when I see it, but the likelihood of something happening to change things in a major way seems to me to be decreasing with each year that ticks on by. The time to do something, if we wanted to entice more Redditors, is now long past.
No actually there is - Rimu converted many Lemm.ee communities over to PieFed.social (I forget if they lost access to modify their older content, or perhaps if they messaged him before lemm.ee went fully down from their old account then he could take that as proof of ownership and grant such access), and Quokka has converted fully from Lemmy to PieFed and then from PieFed to PyLova, so aside from Rimu are the preeminent experts in such conversions. With Rimu’s community migration tools and Quokka’s experience, communities on Lemmy are not held hostage, anymore.
Otoh, Rimu himself is personally quite opinionated on certain matters, and rarely but decidedly goes against community push-back to enact his own agendas. In the second most recent event, prior to the PyLova code non-attribution one I mean, he decided fairly unilaterally to shadow-censor content even hosted on other instance platforms - restricting people’s ability to vote more than a given allotment per day, even if they use Lemmy, Mbin, Mastodon, nodeBB, etc. Which is arguably fine, except vaguely like the Admiral Patrick situation, Rimu continues to do so without telling the recipients that they are being thus censored. Like someone presses an upvote button, the color changes, but then the vote count does not change. MANY people disagreed - about the change overall, about its lack of transparency, and also in how it was effectively not communicated to the instance admins, leaving them surprised at the behavior of the code running on their own machines. Rimu lost a lot of trust in his handling of that situation.
So people are - correctly - hesitant now to put their trust into PieFed, when at any moment some similar situation could arise. Of course there is the PyLova fork, but it is extremely new, so I would wager that people are taking stock of it and seeing how it will shake out. Lemmy has a tainted reputation among the general public (for good reason), PieFed people barely know about but since it shadow-censors people’s contributions like Reddit does I can no longer see it becoming popular among the diminishing crowd that wants to flee Reddit’s overzealous censorship practices, all the more so since most 3rd-party apps only nominally support PieFed much less PyLova. The situation is not entirely untenable but it’s inordinately complex, and in those Reddit threads I shared earlier you can see people simply noping out of everything that we have going on here with all our in-fighting. The technology has to get better if we want to bring people here. Which I suppose it is, but at a pace that is exceedingly frustrating. Until it does, we remain a troll bar.
I never made that connection, but yeah, this could be much easier to implement than I was thinking.
Yeah, I could see this being a few easy setting/feature addition.
Understandable.
My understanding is that this was set up that way to prevent harassment. I’m not knowledge on the subject so could be wrong.
My understanding was that it “worked”. As in it was haphazard and a very manual effort to get what did happen to work.
Not the same thing, but [email protected] and I tried to save the past posts of [email protected] to piefed.zip after mander.xyz went down. It didn’t work, I (on piefed.zip) could see the old mander.xyz posts, but no one else on any other instances could. I also had a problem with adding mods to the new piefed.zip community (lemmy mods couldn’t be added, non-piefed.zip mods couldn’t be made owner).
So, while I expect it can be done, I don’t think it’s an easy, straightforward, or automated process to move software or even communities. I know my example was not a 1-to-1 typical move, so if you have any counter-examples please let me know (I can utilize them for the [email protected] wiki).
I am quite aware of Rimu’s nature (he and I had discussions in the past).
Agreed and I would say he’s lost a lot of trust many times at this point (I used to be one of his biggest cheerleaders).
I suspect so. I mentioned it to the piefed.zip admins, so they are at least aware of it. But I suspect there won’t be any piefed -> pylova conversions anytime soon, unless Rimu screws up big (again).
I believe their is an official Piefed app coming (https://fedidb.com/software/compare?software=lemmy%2Cmbin%2Cpiefed). Assuming it’s open source, presumably the other partially Piefed compatible apps could utilize the “Piefed Official App” 's code to improve compatibility within their own apps. I’m certainly going to suggest it to the voyager Dev when the “official app” comes out.
Agreed, but not sure we should expect more. FOSS is generally slow moving, due to it being small, part-time teams. I’m in a place where I can help support FOSS financially, but I know that is not an option for everyone, plus it’s a new consideration/viewpoint for people coming from corporate/proprietary software (where they are the product).