I recently had GCC give me the error “returning to the gate for a mechanical issue”, fun stuff as well
I recently had GCC give me the error “returning to the gate for a mechanical issue”, fun stuff as well
I’m not sure I’d classify it as a bug. Instances can temporarily go down at any moment for numerous reasons, to account for this instances will keep retrying to connect with an exponential backoff. At what point should an instance assume that another instance is permanently gone?
Perhaps a good start would be adding a status indicator to every community with something like last sync: 1 minute ago.
You can see that an instance/community is gone by visiting the instance directly. In this case at https://lemmy.fmhy.ml/c/imaginarymechas (which obviously won’t work now, as it’s gone).
Whenever you submit a post to a community, first your own instance saves the post locally, then sends it to the instance hosting the community, this instance then sends it to any other instance with users subscribed to the community. When the hosting instance is down, then that step of course fails, resulting in the post being only visible to members of your own instance.
To add on to this, if you’re using some random RAM stick picked out of the gutter, then it might be worth it to run memtest86+. Bad RAM sectors can give some weird unpredictable issues.
If it creates infinite number of people, it could solve world hunger with some good ol’ Soylent green thinking. Although you might want to figure out how to slow down the trolley at some point.
They sold a physical switch hacking device
Did you try requesting your data? I got my data within a day. They probably mention 30 days because that’s the legally defined deadline, and to give themselves some leeway in case the automated system has issues with some user.
It also makes sense for them to make it a low-priority task, as they have a really long deadline for it, and you don’t want it affecting the main site.
They’re definitely automated. I doubt it’ll do much in terms of protesting.
This is probably it, the instance they’re communicating with has only 5 instances in their allowlist (look at the bottom of this page).
As that is the instance they’re posting this from, they probably won’t see my comment.
Instance admins can limit the languages available to their users, they might not be fully aware how this setting impacts their multilingual users. I recommend you contact them to change this.
Is the remaining post you’re seeing about long covid? Check your account language settings, that’s the only post without a language assigned to it.
Why is this mildly infuriating exactly?
Considering it’s caused by a bad harvest, I wonder what the quality of the available tomatoes is.
A slice of tomato on a burger needs to look good. That doesn’t matter as much if it gets cooked into a curry or something.
They claim to reach being fully backed within 23 minutes. Yeah, no shit if you set the goal as low as £10000.
They also artificially keep the super early bird remaining stock low to pressure backers into a snap decision. When I checked there were 7 out of 2310 left. That number will probably increase once it actually runs out.
A rooted phone is definitely a bigger security risk if you don’t know what you’re doing, as anything with root access is unbounded by the usual android permission system, and can completely demolish your OS. Additionally it can serve as a big warning if someone else has tampered with your device.
A difference in timezone settings could still be relevant in what causes the bug.
Is the time on your instance and on your PC at correctly? And is there a difference in timezones configured on your instance and pc? 60 minutes seems a bit too specific to not be timezone related.
Inside the admin settings there should be an input box named “blocked instances”, just put the domain name of the instance you want to block in there.
Do you check if it’s gone by going to that community’s page? Because that’ll redownload recent posts from the community. Keep in mind that it won’t fetch anything more than that unless a local user subscribes to it.
It should also be noted that the post will only appear on that kbin instance, and no other instances.