--- Nabídka již neplatí. --- Prodám zhruba tři až čtyři týdny používané hodinky Garmin Instinct 2 (bez solárního nabíjení). Hodinky jsem pořídil minulý rok, ale nakonec jsem došel k závěru, že si s tímto ekosystémem nesednu, tak jsem se vrátil zpátky k Huawei. Od té doby mi tady jen leží v šuplíku a nemají využití. Mám k nim stále originální nabíjecí kabel, v ceně. Cena: 2000 Kč + doprava. Pořizovací cena byla tehdy přes 5 tisíc. Vzhledem k velikosti není problém poslat poštou. Originální balení už ale nemám. Záruku by taky ještě pár měsíců měli mít. Kdo máte zájem o více info, napište.
> A prominent media analyst is proposing an unorthodox solution for Comcast to win over Donald Trump’s approval in its bid to purchase rival media giant Warner Bros. Discovery: make the widow of slain right-wing activist Charlie Kirk the top editor of the merged company’s news networks.
First, this is such a failure of an idea because you couldn't even write her name in the first paragraph: you literally referred to her as "widow of the slain..."
I just read a partial review of a cross-body bag. The (I assume male) writer wrote something like, "Turns out I'm a huge fan. It's nice to get my iPhone out of my pocket, and be able to carry sunglasses, AirPods, and other essentials." I feel like he just discovered the purse. Women have been doing this for decades. I like having things with me, too, so I'm glad bags seem to be coming into fashion for men, but this isn't exactly some amazing new invention.
Farmer Brown believed his injuries from the accident were serious enough to take the trucking company to court. But the company’s slick, high-priced lawyer was ready to tear his case apart.
“Mr. Brown,” the lawyer said, straightening his designer tie, “is it true that at the scene of the accident, you told the responding officer, ‘I’m fine’?”
Farmer Brown scratched his head. “Well now, I was just about to load my favorite mule, Bessie, into—”
“I don’t need a story,” the lawyer interrupted sharply. “Just answer yes or no—did you or did you not say, ‘I’m fine’?”
Brown frowned. “Well, like I was saying, I was loading up Bessie, and we were headed down the—”
“Objection, Your Honor!” the lawyer huffed. “The witness is being evasive.”
But the judge, now curious, leaned forward. “Actually, I’d like to hear what he has to say about Bessie.”
Farmer Brown smiled. “Thank ya, Judge. Now, as I was saying, I had just loaded Bessie into my trailer, and we were driving along when this big ol’ semi blew right through a stop sign and smashed into us. BOOM! My truck flipped, I flew one way, and poor Bessie went the other.”
He shook his head. “I was hurt bad—couldn’t even move—but I could hear Bessie moanin’ something awful. Next thing I know, a highway patrolman shows up. He walks over to Bessie, listens to her groanin’, shakes his head, pulls out his gun, and BANG! Puts her down right then and there.”
The courtroom gasped.
Farmer Brown continued, “Then, the patrolman walks over to me, still holding his gun, and says, ‘Your mule was in bad shape, so I had to put her down. Now… how are YOU feeling?’”
The jury erupted in laughter. The lawyer slumped in his seat, defeated. And Farmer Brown? Well, he walked out of that courtroom with a fat settlement—and a brand-new mule named Lucky.
Yeah, god the state of optical media is damn pathetic.
They never released a UHD BD-R.
They released BD-R XL, but according to wikipedia: "Although the 66 GB and 100 GB BD-ROM discs used for Ultra HD Blu-ray use the same linear density as BDXL, the two formats are not compatible with each other, therefore it is not possible to use a triple layer BDXL disc to burn an Ultra HD Blu-ray Disc playable in an Ultra HD Blu-ray player, although standard 50 GB BD-R dual-layer discs can be burned in the Ultra HD Blu-ray format."
My request is to do 30x fast forward over the network with decent images showing where it is at. This is apparently impossible, unless you're a PS3. Even the dune hd player I bought can't do it.
POSIX allows an implementation of getpgid (pubs.opengroup.org/onlinepubs/…) to fail when the process calling getpgid() is not in the same session as the process it wants the pgid of.
Reasonably, Linux and FreeBSD ignore that part, and simply return the pgid, no matter who asks.
But OpenBSD sees a standards-conformant opportunity to be a giant pain in the ass, so it has to jump on it. And so, when A calls getpgid(B) and B is in a different session, it returns -1 EPERM, even when A and B have the same uid and gid, and it would be perfectly legit for A to send signals to B and its whole process group.
The behaviour is the same for getsid, of course.
As a consequence, s6-supervise on OpenBSD is unable to target the process group of its supervised process, which disables one of its mitigation strategies for misbehaving daemons that leave children behind when they die. And since OpenBSD doesn't have cgroups, that doesn't leave many mitigation possibilities.
I am curious of why POSIX allows this. It seems to go against the common Unix principle that the uid is the key to which process is allowed to communicate with which.
It might make sense to forbid setpgid from the outside, but forbidding reading the pgid feels wrong. Especially since it's defeatable: since I control the parent and child, the child can getpgrp() and communicate its pgid to the parent. But that's a lot of work for something so niche that only breaks on OpenBSD.
I am starting to believe that OpenBSD's reputation for security is mostly due to the fact that no rational person bothers to port software to it.
yeah, it's old. If you can spelunk out a rationale somewhere, I'm interested - but I'm not interested enough to do the archaeological work myself. To me it's yet another OpenBSD quirk that I may write a workaround for in the future if I have nothing better to do.
Sadly I don't think I can spelunk further myself, messed up how the version numbers match (this stuff is a mess) and it actually goes back to SUSv1, so I don't even have version control going earlier.
I mean quite generally the "rationale" for anything like this is usually: some implementor already did it like this so we need to write the standard s.t. it fits. POSIX started out as XPG, so mostly just documenting preexisting common interfaces rather than defining ones for the future. If they tried the latter, that often failed (e.g., pax). So my money is on: Some UNIX did something weird in that case and that's why this clause is part of POSIX ^^'
Yeah, but effectively if that Unix is either gone or has changed since, it can help on moving things along. That's why details on rationales are useful.
absolutely! but arguing about a UNIX being "gone" is very difficult territory in a working group that's defining what UNIX™ is and mostly about cosplaying a time where this matters. I love POSIX, I really do, but I've attended one of the Austin Groups meetings as an intern. And that was enough for a lifetime.
Well a lot of UNIX systems were last released/discontinued in the 90's like Amiga Unix, Digital Unix/Tru64, A/UX, …
IRIX last got an update in 2006 but writing was on the wall in ~2001 already, SunOS (BSD) got replaced by Solaris (SysV with bits of BSD-compat), …
And in the last few years I think I've yet to see someone actually check behavior of ones like AIX or HP-UX beyond the manpages, usually it's major foss systems and a bit of Solaris + macOS.
I tried porting skalibs to AIX once. I made an honest, serious effort. I eventually had to give up because too many very reasonable things weren't working. For instance, gcc -o /dev/null failed, and it was one of the least egregious failures.
Some OSes are just beyond hope and deserve the oblivion they're sliding into.
Heh the gcc -o /dev/null thing reminds me that if you run tcc -o /dev/null as root you actually end up with an executable at /dev/null since it does an unlink+creat
With the recent rise of things like Sora and Grokapedia, I think we need to invent a new term for websites that are basically nothing but AI slop. How about slopasites? Slopsville? Something.
TBH, Grokipedia is (mostly) just a copy of Wikipedia, with an LLM running over all the sources / references.
You can click "see edits" on many articles, and it'll show you the changes between Wikipedia and Grokipedia (in a perfectly accessible pop-up, no less).
A lot of those changes are like "the article says 'in a 1971 paper' and cites the paper, but the cited page clearly says the paper was released in 1972."
Just to be clear, I don't think AI should have free reign over factual articles quite yet, but if human editors could see, fact-check and decide on these edits, I genuinely think we could have a better Wikipedia.
So, tbh, I would not change anything about having #Autism and #ADHD. Sure, if I had been diagnosed properly and had more support, some aspects of my life would have been better. But I have no regrets on having a semi-eidetic memory, being able to recognize patterns, thinking outside the box, etc. What I could have used less of? Being bullied, not knowing there were others like me out there (and the subsequent isolation), over-masking and paying the price, having meltdowns from not understanding sensory overstimulation, etc. But it's never too late to delve into self-understanding and awareness, and, most importantly, building community with like-others!
С обновлением интерфейса Youtube на 24" 1080 мониторе я могу видеть на странице только 6 видео или 3 видео и 5 шортсов. Хотя, зачем вообще показывать шортсы в рекомендациях на десктопе?
Вот бы еще в самом гугле на одном экране было видно только первые 2 результата, одним из которых был бы "обзор от ИИ", вот тогда это было бы UI consistency
Of course it is very sad that the 3 million people of Jamaica have to endure the lethal torrential floods, landslides, & ~300km/h winds of Hurricane Melissa. But surely we can all agree that is the necessary sacrifice we all must make to ensure that the murderous thugs running the world’s fossil fuel industries continue to enlarge their absurdly huge incomes they insist are their right and due. #ClimateChange #Hurricane #Mellisa #Catastrophe #FossilFuels
Random tip for comparing the performance of Rust and C programs that use stdout:
Rust stdout is line-buffered, even when redirecting to a file.
Glibc (and most C libraries I know of) are smarter than this, and will switch to a more aggressive buffering scheme if they aren't writing to a terminal.
Running the program _under hyperfine_ is enough to trigger this behavior, because hyperfine takes over the stdout stream. Glibc senses that this is not a terminal and turns on a 4096-byte buffer; Rust continues making one syscall per line.
So if a Rust program that prints stuff seems to lose a performance advantage over a C counterpart when run under hyperfine, it's worth stracing to check.
(There's continuing talk of fixing this default in Rust, but it's not fixed yet.)
Vorige keer "strategisch" op GroenLinks gestemd. Geen slechte partij, een groot en "breed acceptabel in de samenleving" links hebben is goed. Maar als de enige opties links en steeds extremer rechts is blijft "breed acceptabel" verder en verder naar rechts schuiven.
Dit keer zal ik volgens mijn hart stemmen. Om links weer terug naar links te proberen te trekken. Laten we dat allemaal overwegen. Ik wil dat links weer normaal wordt. Dat liefde weer normaal wordt in plaats van deze haat.
Dat is niet te zeggen dat ik niet blij ben met GL stemmers. Het blijft een goede stem en een sterk "breed acceptabel" links blijft goed om te hebben. Maar overweeg in plaats van enkel strategisch ook volgens je hart te stemmen. Want 1 zetel is zo veel meer voor een kleine dan een grote partij.
Mag GL lekker groot blijven, maar klein links ook gewoon eens groeien
Rust's NamedTempFile made me realize that temporary files that delete themselves when the object goes out of scope... are quite nice, actually. You have to structure your code so that they get passed around properly, but that makes the lifetime of the tempfile very clear. It's not garbage to be cleaned up afterwards (if you remember); it's just a temporary resource like any other.
Summary Zed is absolutely inaccessible for screen reader users on Windows. Tested with latest JAWS and NVDA versions. Description Steps to trigger the problem: Install Zed on Windows 11. run Zed wi...
@Jay42 don't think so. they code in Rust and use some GUI framework (I don't know which one, asked in the comments). I guess, the person that would be the most helpful is Matt @matt. But again, splendors and miseries of OpenSource: how can I urge Matt or even ask him to do something free of charge? I mean, who am I to do that? He already does lots and lots of things for the community, and it's up to the Zed team to care about accessibility. But they mildly told me to F off, basically.
@Jay42 The Zed team wrote their own Rust GUI framework, GPUI. So I don't know of anyone else who would have much motivation to make it accessible. And I can't go around implementing accessibility in every GUI toolkit out there, even with AccessKit. Working on AccessKit itself is enough.
Hubert Figuière
in reply to mcc • • •