If not for political reasons then why limit first version to Google/GitHub rather than starting with generic OIDC (which should include those two anyway)?

We also took your feedback seriously and we are now implementing proper sign-in options like: Google GitHub (and more coming later)

Both can be true.

I think such character assessment and calling names is unnecessary and off-topic here though. Better engage with substance than judging by vibes and doing ad-hominem.

Called it.

https://feddit.online/post/1372107/comment/6758185

No one listen grug til chicken come to roost

I guess they now have large enough number of users that it would be wise to shift some focus to supply-chain security from growth-hacking.

This is growing pains.

USB enclosures tend to be less reliable compared to SATA in general but I think that is just FUD. It’s not like that’s particularly bad for software RAID compared to running with the enclosure without any RAID.

The main argument for not doing that is I believe mechanical: Having more moving parts mean things might, well, move, unseating cables and leading to janky connections and possibly resulting failure.

You will kill your USB controller, and/or the IO boards in the enclosures

wat.jpeg

Source: 10+ years of ZFS and mdadm RAID on USB-SATA adapters of varying dodginess in harsh environments. Of course errors happen (99% it’s either a jiggly cable, buggy firmware/driver, or your normal drive failure) but nothing close to what you speak of.

Your hardware is not going to become damaged from doing software RAID over USB.

That aside, the whole project of buying new 4TB HDDs for a laptop today just seems misguided. I know times are tight but JFC why not get either SSDs or bigger drives instead, or if nothing else at least a proper enclosure.

It’s more like busking on the street and then feeling offended about not getting any money despite people liking your music. Maybe you’re even inadvertently part of some commercial ad shoot profiting of the city vibes. Or offering free trials of a service and then being upset when nobody converts.

I don’t think things you do become “charity” just because others benefit from it and you don’t get compensated. The bar is higher than that.

No reason to expect that everyone will be in a position to do that indefinitely, especially when it comes to massive projects that turn into full time jobs.

For sure. No strings attached goes both ways.

I’m curious: What’s motivating you to do that when the memmap param can do the same without patching?

Thank you, I’m glad you like!

not having worked with memmap before, it is not immediately obvious to me which hex means what (I am guessing RANGE@START? ). Would be nice to have a link to an explanation there.

I just have the link to the kernel docs because I think they do a better job explaining it than I would 😁

But yeah, basically. Except for this use-case you want RANGE$START not @. And you can use human sizes like 128M$RANGE.

There is one part in the post mentioning how to “pad holes” in failing areas. Maybe I should expand it with some details around aligning reserved address space.

Otherwise, corruption of the RAM itself does not usually spread like mold in bread or wear out and fail in similar ways to flash memory.