jolmg
What's em? I thought it was developed from ed.
The non-QR/textual panics can be restored with a kernel/module parameter as described here:
https://wiki.archlinux.org/title/Kernel#QR_code_on_a_blue_sc...
The QR code can be made to provide the text itself (non-URL-encoded) by rebuilding the kernel with CONFIG_DRM_PANIC_SCREEN_QR_CODE_URL unset.
Distro developers and user are separate people. Also, a person viewing the QR code is not necessarily the owner of the panicked system.
https://jexposit.fedorapeople.org/drm-panic/#?a=x86_64&v=6.17.0-rc2+&z=640167080454085846813051618361759010657877897271730610040416716330885911862863637865629876538143479424501684305108526815246884351579112416213658591538197326904066495250432477741109137529913891705603204551637814390799863373567102735011646456675550848214802373263012070738317101764828501215130799514552173100464226323283035104742647807880303016111647745731220181725103046725626673798313499244415603609976795733414017504856193883754936010234315170039423982724526624590659186737336223463702[... many many more digits]
That's from the QR code image at:https://discussion.fedoraproject.org/t/f45-change-proposal-d...
This script is to decode such kernel panics without needing to provide it to an external service.
https://www.merriam-webster.com/dictionary/or%20else
> [He said to do this, or I'll regret it.]
> [He said to do this, else I'll regret it.]
I imagine people couldn't decide on which conjunction to use since they both work, used both incorrectly, stopped using plain "else", then started thinking they needed to prefix "or" before "else". Dictionaries then adjusted.
> Make sure to buy flour, and we'll be able to bake the cake.
> Make sure to buy flour, so we'll be able to bake the cake.
> Make sure to buy flour, and so we'll be able to bake the cake.
Regarding parentheses/brackets, I said "separate fingers", not "separate hands". I do use separate fingers for parentheses/brackets.
The numpad is a weird thing. When I've (rarely) needed it for sustained number capturing, I do typically stick to one finger because it's easy to get lost with multiple. Not sure why. It could just be lack of practice with the numpad.
> When you go shopping make sure to buy flour, or we won't be able to bake the cake.
> When you go shopping make sure to buy flour, else we won't be able to bake the cake.
EDIT: TIL: Dictionaries don't commonly define "else" as a conjunction, except for Wiktionary. Still sounds natural to my ears, so this is a surprise.
It's the "elephant in the room" sort of thing that doesn't need to be said because it's apparent and viewers know what they want in that regard. It does get acknowledged when reviewers that don't normally review toughbooks, review toughbooks, but it's an acknowledgement rather than a complaint. Why would someone even view a review of a toughbook if they cared so much about thickness?
> On October 17, 2026, browser root programs received a report that the private keys of eight eMudhra intermediate certificates had been compromised. The private keys were 4, 56, 66, 115, 155, 156, 230, and 237. A P-384 elliptic-curve private key normally has about 384 bits of entropy, but these keys had between 3 and 8 bits.
It's probably better for the user to search the original URL themselves on the Wayback Machine. If you cite with a Wayback Machine link when the original link still works, you're just creating needless work for a non-profit. An archive isn't a CDN.
> or at least creating
I agree on creating.
You don't need to. They probably mean how rounded objects tend roll or slide, and spiky objects tend to scrape at most or dig into a crevice and so abruptly stop with a shorter sound.
Wonder if registrars will refund to people's cards.
tab * 4 + space * 7 + tab * 2
tab * 2 + space * 1 + tab * 1
tab * 1 + space * 4 + tab * 2
space * 16 + tab * 3 + space * 4
tab * 4 + space * 2 + tab * 2 + space * 2
tab * 3 + space * 3 + tab * 1 + space * 6
The code ends up looking janked unless you use the particular tab-width of the space/tab-indenter[1], which isn't always 8. It completely defeats the whole purpose of the tab indentation.[1] On those first 2, given the odd (not even) number of spaces, it's likely that use of spaces was for alignment, but then a tab-indenter added tabs to that...
From bash(1):
> If the redirection operator is <<-, then the shell strips all leading tab characters from input lines and the line containing delimiter.
That's also how it works with zsh.
This is why my here-doc delimiters are always un-indented despite surrounding indentation.
Wish bash had something like ruby's `<<~`, which accepts either space or tab indentation of the delimiter and additionally removes the indentation of the block (likely based on the least indented line).
You should really try to have a copy of your own records. Different sorts of clinics may sometimes make it difficult to get a copy of studies, reports, etc. but it's something you should really insist in, to the point of avoiding places that don't give them to you. It lets you have greater selectivity of your healthcare providers by not depending on a provider for access to your own medical data. Resist the lock-in.
Also, providers may not archive your data forever. I've had one that realized my records from a visit some years earlier had been discarded/lost. They would have been really useful to make a comparison.
Having your records yourself, you won't have the need to tell them so they can ask for your records to the other provider on your behalf.
It's a good idea to tell them you came to them for a second opinion after they've already given it, so they can also give their opinion on the first opinion. However, that's different from telling them so they can get your records when you should already have them yourself.
> For example you can't even see 4chan's homepage.
That's likely the same thing, the 4chan admins asking IA to omit them.
> I was contesting the claim that archive.org wants to preserve material. It's hard to trust that an archive will preserve the page you archived if the owner can come along at any time and wipe it.
Being able to preserve material depends on their surviving.
Alternatively, though I don't know if it works on Mac, on X11 Linux you can middle click with touchpads by tapping with 2 fingers. Tapping with 3 fingers right clicks. That's going to work anywhere clicking does, because it's handled by the touchpad driver rather than by app convention. If it doesn't work by default, it can be configured with `synclient`.
They take them down when their respective author / copyright holder wants them down. That wouldn't apply in this case where the author wants them up, but a DNS infrastructure might cause the links to fail.
> and block legal sites from being archived.
Not sure what this refers to.
> Going to post it here in case someone several years from now comes to this thread and wants to read the original blog post.
I wouldn't count on short-links living long. Generally, the point of link-shortening is that they're temporary. "zi6qn" might later get reused for some other page.
This quote is pretty old:
> Those who would give up essential liberty, to purchase a little temporary safety, deserve neither liberty nor safety.
> its almost better to be safe than to have to explain to someone's loved ones you had to chance to prevent this and did nothing.
An authoritarian government isn't safe. That's why safety is also not deserved when you go chasing for a little of it at the cost of essential freedoms.
Bit curious what the pronunciation difference would've been in French.
On another note, looking at the Wikipedia article:
> When the franchise was released internationally, the short form of the title was used, with an acute accent (´) over the e to aid in pronunciation.
I'm realizing that didn't do anything for English since the syllable stressed in English is "Po".