[Edit: on the left is when viewed from lemmy.world; on the right is when viewed from sh.itjust.works.]
🙃
I think I might need to ask for some pies from PieFed (no offense to Lemmy)
[Edit: on the left is when viewed from lemmy.world; on the right is when viewed from sh.itjust.works.]
🙃
I think I might need to ask for some pies from PieFed (no offense to Lemmy)
16 Comments
gigachad@piefed.social · 22 pts · 348d
I mean instances are typically run by volunteers, the sh.itjust.works admin is a pretty nice guy as far as I know. Report it in their main community and see if they can fix it. I don't think this should be infuriating, things like these happen in the fediverse. But yes, you are always welcome to PieFed, although you might experience other issues you haven't before.
tal@lemmy.today · 13 pts · 348d
It looks like this is !main@sh.itjust.works
Most major Threadiverse instances have some sort of "instance" community to deal with issues related to that instance --- personally, I think that it should be be a default on instances, so that we have a single standardized name and it's easy to find for users.
On lemmy.today, there's !lemmytoday@lemmy.today to act as an "unregulated" instance community and !announcements@lemmy.today, where posting is restricted to the admins, so that official announcements don't get drowned out. I think that that "two community" approach isn't a bad idea.
moseschrute@lemmy.world · 2 pts · 347d
People don’t understand PieFed. It’s a fantastic project, but if you think switching to newer price of software that is still under development is going to have less hiccups…. Well you clearly don’t know how software works. This is not a knock on PieFed. On the contrary, I love what they built, but you have to have patience. This is free software build and hosted by volunteers. OPs just gonna wind up complaint that PieFed also has hiccups.
ohellidk@sh.itjust.works · 11 pts · 348d
Weird. I wonder if something is up with our instance...
lath@piefed.social · 20 pts · 348d
It's named sh.itjust.works, not sh.itjust.workswell or sh.itjust.worksontime. Maybe that has something to do with it.
Hazel@piefed.blahaj.zone · 8 pts · 348d
sh.itbarely.works
/jk of course :)
WolfmanEightySix@piefed.social · 5 pts · 348d
So it’s like catching a train or bus in the U.K.?
hanrahan@slrpnk.net · 1 pts · 347d
More like sitting in a car in endless traffic.
PhilipTheBucket@piefed.social · 9 pts · 348d
First possibility that comes to mind is a backed up federation queue on lemmy.world for some reason.
It could also be some failure on sh.itjust.works, but if I had to guess I would say it's more likely an issue on the sending end.
Sergio@piefed.social · 3 pts · 347d
see: https://grafana.lem.rocks/goto/gMske4jHR?orgId=1
I don't understand everything on this chart, but it looks like sh.itjust.works lagged a bit over the past 24 hours and is now catching up.
moseschrute@lemmy.world · 2 pts · 347d
It’s kinda mildly infuriating that this is mildly infuriating. Lemmy and PieFed are free, open source software run by dedicated volunteers. Many of those volunteers spend quite a bit of time making sure everything runs smoothly. Hiccups are gonna happen. You should donate to your instance if you wanna help things run smoother in the future.
DeathByBigSad@sh.itjust.works · 5 pts · 347d
Its frustration at a situation, not necessarily the people involved.
BlueEther@no.lastname.nz · 2 pts · 348d
no.lastname.nz seems up to date with world, so doesn't seem to be just sending
[edit] shit just works seems to be getting this thread and my comments ok...
ryper@lemmy.ca · 2 pts · 347d
lemmy.ca upgraded lemmy an hour or two before your post. Maybe one or both of the instances you're looking at also upgraded recently and the problem has something to do with that.
isaaclw@lemmy.world · 2 pts · 346d
While we're on about the fediverse, some communities I can't post to. Does anyone know what things I should look at?
Edit: I had to submit 4 times. 3 times I got "problem submitting comment"
hendrik@palaver.p3x.de · 2 pts · 348d
Seems it caught up a bit since. Now some posts from more than 2h ago are there. But "/api/v3/federated_instances" on LW still reports it's something like 10h behind.
Is thus necessarily the receivers fault? I mean if LW builds up a queue of content to federate out, that could be blamed either on lemmy.world or on sh.itjust.works ?