Would there be any benifit to host another instance?
PriorProject @ PriorProject @lemmy.world Posts 9Comments 266Joined 2 yr. ago
PriorProject @ PriorProject @lemmy.world
Posts
9
Comments
266
Joined
2 yr. ago
This is sensible advice, but also advanced that is still dangerous if someone doesn't have a good understanding of how web-sessions are stored and gets confused about what browser is what or accidentally logs out of the wrong browser.
Unless someone has demonstrated technique acumen, I'm likely to continue to advise to wait for the feature to improve since losing access to your account is so spooky if you don't have the confidence to get it back.
Post in !moderators@lemmy.world. Don't message/mention admins as the other responder suggested, as they've said repeatedly that they get hundreds of mentions and cannot keep up with them.
Admins mod the moderators community and check it periodically, if you post there they can help you out. There's also an email address they post semi-regularly but I always forget it. Search it up if they don't respond within a day or so to a post on the mods community.
Tests go in !test@lemmy.ml
Yeah fair. This is sound advice.
I buy matched pairs to mirror, and then offset the purchase of my pair of backup drives. So I end up having 4 copies on two different models. And when my primary disks get full I "promote" my larger backup disks to primary and buy a new/larger pair of backup disks that are big enough to store many snapshots of my primaries. I knew this was too much for OP and tried to simplify... but your approach is equally simple and better.
That disk certainly isn’t healthy.
For my own future knowledge, what, exactly, in the logs, led you to that conclusion?
GPT is the partition scheme that stores the partition table. Very few pieces of software interact with that layer of your storage system. The first GPT table error tells us that, unless we've been messing with low-level tools that might break the partition table... the physical disk has probably already lost data. So we're already primed to suspect a busted disk.
Then the kernel log snippets you pasted show tons of errors in the block device layer. I know noisy application logs sometimes train us to ignore error messages, but the kernel block device layer does not log out error messages for fun. If you see any log like ERROR sdx where sdx is a block device that stores important data without a backup... you're about to be in for a rough ride.
image the whole thing with ddrescue
Since you mention "image", I'm assuming that I would need a drive at least equal to the size of the source drive to store the image? The issue is that the source drive is 2TB in size, so I would need to source another 2TB drive (at least) to store the image.
Yes, though you can pipe ddrescue into gzip or another compressor and if the drive isn't full and you're lucky enough to have some decent sized zero'd out regions they'll compress very well. In the best case, you might only need a disk big enough to hold the live data. In the worst case, yeah, you need a matched disk or bigger.
Pro tip, buy drives in pairs and automate backups to one of them. If you have a disk you can't copy to another disk, you almost might as well have no disk. This kind of thing happens, not a lot... but I lose a disk maybe every 3y-5y or so. I have a few disks around... maybe 6 online at any given time. But it's not like I'm running hundreds of them. They just conk out every now and again and you've got to be ready for them.
Did you provide an email? I've heard password reset bypasses 2fa. I don't recommend enabling 2fa in its current state though, without verifying am OTP code prior to enabling 2fa, you never know if you've just locked yourself out of your account.
Try these steps:
- Logout via Home -> Hamburger menu -> accounts are at the top, click there and sign out. Try signing in, did you win?
- If not, sign out again then long-press the app icon from your android launcher screen and select
App Info, or find another way to get to the android settings screen for Jerboa andClear CacheandClear Storage. Try to log in again, did you win? - If not, sign out again and sign back in. Did you win?
- If not, cry because I'm stumped. You could also try liftoff, which if you weren't logged in prior to yesterday shouldn't have a cached broken session. Or install the PWA from lemmy.world via Firefox mobile. Or use the brand new Voyager setup at m.lemmy.world again as a PWA via Firefox mobile. Of those, I like Jerboa and liftoff best.
It's nice to see this officially hosted for lemmy.world users. I've been curious about wefwef but there was no way I was going to enter my creds into a third-party proxy. It feels much better to do so via an instance hosted by the world admins where my Lemmy account is though.
FYIW, when you save this as a PWA via Firefox mobile, the name is just "voyager", which I assume makes it hard to distinguish from the voyager instance hosted by its devs. I don't think this can be changed as a user (unless I'm too dumb to figure it out). If the PWA app name can be changed server side, might be good to call it Voyager World or something.
The best practice when setting up 2fa would be for Lemmy to confirm a code before applying the change, to verify that OTP token generation is working as expected. It's mildly dangerous use 2fa on Lemmy in its current state due to the absence of that feature. Though as you note, password reset bypasses 2fa.
This has been reported in post/comments, but never with convincing evidence to my knowledge. Nutomic (dev and lemmy.ml.admin) is in this thread reporting that there's no blocking in place and they don't know what's up.
The customer using the feature:
Don't ask how they uncooked it, support was trying to help them get the cheese off.
Yeah, federation is being creaky globally right now. The GitHub issue list is littered with admins reporting intermittent federation issues.
I wouldn't expect it to repeatedly prevent communication though. Just maybe some intermittent issues occasionally.
Even in the absence of an explicit rule, I think Martin is largely on the right side of norms here.
- Cara is a guest of Alpha Romeo in a promotional capacity. She received the access she received BECAUSE of her celebrity status, and with the understanding (formal or informal) that her visit would be used to promote Alpha Romeo and F1 via association.
- The grid is a restricted area where multiple live media crews have announced their presence in advance, and where it is known that opportunistic interviews are conducted. Martin isn't showing up in somebody's back-yard birthday party and avoiding him is the easiest thing in the world. This would be a different story if he was lurking in the parking lot, outside hotels, or sneaking into team hospitality suites. If you don't want to talk to Martin, don't go on the grid and he won't bother you.
- The nature of live media is such that, in snubbing the media crew, you're transitively snubbing their audience as well. There's no opportunity to not publish the story if the interview request doesn't pan out, the story of the the interview request not panning out is published live as it happens. We're riding on Martin's shoulders while he gets rebuffed, and it's happening to us too. Doing this to fans makes you a lousy promotional partner.
Because of the above conditions, IMO... you know what you sign up for when you enter the grid. It's no different than a red-carpet event or any other media/press event. If you don't want to interact with the press, no one is forcing you to go. If you go, and then get huffy about media wanting access to you, you suck as a promotional partner and teams should not invite you back (and should have clarified this beforehand and not have invited you in the first place if that's how you felt).
As to Martin's sass, I'm here for it. There's one place in the world where he's justified in shit-talking anyone who snubs him and I'd be disappointed if he didn't.
... it's an explicit part of the deal now (after Miami) that if you want to be on the grid that you have to be willing to be interviewed...
Though I agree with your broader point that the grid is a restricted area that is hosting a media event and it's a bit ridiculous to get surprised-pikachu about media interacting with you there... Martin was likely stretching a bit when he said there are now rules indicating that everyone has to be available to interview. In 2021, bodyguards were forbidden from the grid after the incident with Megan Thee Stallion. This makes it easier for media to approach celebrities, but doesn't obligate them to participate. I linked to reporting on this in my top-level comment.
That said, I'd have no objection to a rule that DOES require participation. They're on the grid in a promotional capacity. Expecting participation in a 30s interview is not bizarre.
Who is to say that Brundle can demand someone interview with him?
F1 and the event organizers could do that if they chose. They haven't, and unless there is some grid access clause that hasn't been reported, Brundle appears to have been mistaken when he said that everyone has to speak... what the 2021 Brundle clause really does is restrict bodyguards from the grid, not require interview participation.
But the grid is a restricted area and F1 and the event organizers can attach conditions to its access. Celebrities get the access they get as a promotional arrangement, and I would have no problem at all with event organizers formally attaching media responsibilities to grid/paddock access and to eject and impose a future ban on anyone who fails to meet them.
Why are we owed that?
We're not, but no one is owed access to the grid either. By leaving one's private box to walk the grid you're entering a live televised media pen and should expect that you're likely to be approached by live media teams if you're a figure of note (and sometimes even if you're a nobody).
Yeah, this post/article is great at explaining the current state of things, but I would not want to engage with Lemmy this way more than like once a month.
If one is interested in Lemmy, a second account is well worth it to get the community-optimized UX it provides.
It's a reasonable feature request and with this discussion thread some of the invisible complexity is exposed a bit for consideration. I think it's sensible to leave the post up, and the dev(s) can decide what to prioritize and how they want to design something like this if they choose to work on it.
These numbers are super confusing right now.
- For a community on the same instance as your account (aka a "local" community) you'll see the global subscriber count, including all subscribers from all instances.
- For a community who's native home is on a different instance than your user account (a "remote" community), you'll see only the subscribers from your instance excluding all subscribers with accounts on other instances. I assume this happens because subscriber counts aren't federated so the only server that knows the full sub count is the canonical home of the community.
I've spoken to tons of people who attempted to subscribe to the biggest community on a topic but got it backwards because they didn't see the full subscriber count on remote communities and misjudged their size.
This is a useful feature, but worth noting how confusing the numbers are. Liftoff should either explain them better than Jerboa, or consider fetching user-counts from the community's server (though this violates the spirit of federation a bit, I don't think there's another way to get apples to apples numbers).
Sadly the formatting in this post gave me terminal cancer. As my final act, I've fixed the formatting. OP, please, only you can save the others. Fix the post formatting.
- Max VERSTAPPEN - Red Bull Racing 1:26.720
- Lando NORRIS - McLaren +0.241
- Oscar PIASTRI - McLaren +0.372
- Charles LECLERC - Ferrari +0.416
- Carlos SAINZ - Ferrari +0.428
- George RUSSELL - Mercedes +0.435
- Lewis HAMILTON - Mercedes +0.491
- Alexander ALBON - Williams +0.810
- Fernando ALONSO - Aston Martin +0.939
- Pierre GASLY - Alpine +0.969
- Nico HULKENBERG - Haas F1 Team 1:28.896
- Lance STROLL - Aston Martin 1:28.935
- Esteban OCON - Alpine 1:28.956
- Logan SARGEANT - Williams 1:29.031
Valtteri BOTTAS - Alfa Romeo no timeDQ'ed for failing to provide a sufficient fuel sample. See https://www.formula1.com/en/latest/article.bottas-disqualified-from-silverstone-qualifying-with-finn-set-to-start.5smsKl0raawLdfivHEeQgq.html- Sergio PEREZ - Red Bull Racing 1:29.968
- Yuki TSUNODA - AlphaTauri 1:30.025
- Guanyu ZHOU - Alfa Romeo 1:30.123
- Nyck DE VRIES - AlphaTauri 1:30.513
- Kevin MAGNUSSEN - Haas F1 Team 1:32.378
Of the 3 subscription bootstrappers listed in this thread, lemmony is by far the worst of them because it subscribes to EVERYTHING by default.
Lcs forces you to pick a number of communities to subscribe to, and the other one has default threshold heuristics that pick a limited number of active communities. Lemmony signs you up for the entire firehose of the threadiverse which both makes instances using it pretty bad fediverse citizens in terms of generating a 50x-100x the federation load of a "normal" single-user instance that subs maybe a hundred communities... and also exposes novice single-user instance owners to legal liability by subbing all the small under-moderated communities full of questionably illegal stuff.
I would recommend one of the better designed tools, and to review the resulting subscription list manually to ensure you're not signing up for some sketchy stuff.