1. I just checked Epstein's Wikipedia entry-- it lists the very recent Drop Site News allegation of his and Wexner's ties to the Iran-Contra drug smuggling operation. And that in a whole section on the topic of intelligence ties going back years.
The links covered in that Drop Site story were left out of a recent NYT article that covered a lot of the same period of Epstein's life. (I also haven't seen that Drop Site News story picked up by any of the other mainstream news sites or shows.)
NYT is prominently listed as a reliable source, Drop Site News isn't. Yet I can still read a nice summary of that Drop Site Story on Wikipedia.
2. Also checked the entry on Bin Laden killing. It not only includes a substantial summary of Hersh's account that was widely criticized by both other journalists and the Obama White House, but that Hersh story also has its own entry.
> You can only trust wikipedia as much as you can trust the news media.
I'd reword this to say if you can trust that at least one reputable journalist has covered a given subject, a Wikipedian has most likely already included a summary in the relevant article for you.
Most, because Debian is the only distro which strictly enforces their manpages and filesystem standards. And most source packages don't care much, resp. have other ideas
Lots. Because many upstream projects don't have their build system set up to work within a distribution (to get dependencies form the system and to install to standard places). All distros must patch things to get them to work.
Well, there are big differences in how aggressively things are patched. Arch Linux makes a point to strictly minimize patches and avoid them entirely whenever possible. That's a good thing, because otherwise, nonsense like the Xscreensaver situation ensues, where the original developers aggressively reject distro packages for mutilating their work and/or forcing old and buggy versions on unsuspecting users.
There seems to be a serious issue with Debian (and by extension, the tens of distros based on it) having no respect whatsoever for the developers of the software their OS is based on, which ends up hurting users the most. Not sure why they cannot just be respectful, but I am afraid they are shoveling Debian's grave, as people are abandoning stale and broken Debian-based distros in droves.
Needless to say, Zawinski was more than a little frustrated with how the Debian maintainers do things.
But honestly, this took 30 seconds to Google and was highly publicized at the time. This whole "I never heard of this, link??" approach to defend a lost argument when the point made is easily verifiable serves to do nothing but detract from discussion. Which, you know, is what this place is for.
I wasn't defending anything; searching for xscreensaver debian debacle yielded links that might or might not have been what you were referring to, They did not, however, yield a link to the JWZ site.
A fair few I expect, amongst actively developed apps/utils/libs. Away from sid (unstable) Debian packages are often a bit behind upstream but still supported, so security fixes are often back-ported if the upstream project isn't also maintaining older releases that happen to match the version(s) in testing/stable/oldstable.
I'm curious what you make of quotemastr's point about a race causing a mismatch between the pointer's capability and its index. First off, in your estimation can this realistically be exploited to wreak havoc on extant C programs compiled using Fil-C? Second, is such a mismatch able to happen in safe Rust? Third, is such a mismatch able to happen in unsafe Rust?
Edit: clarification to narrow the question even further
"Wreak havoc" is a very vague claim. Instinctively the tearing feels like something very difficult to usefully exploit, but, we know historically that the only people who can reliably tell you whether it was difficult are the attackers actually trying to do it. Don't believe the defenders.
AIUI this capability versus value distinction is a Fil-C thing. So, that's not a thing in Rust at all. In Safe Rust the pointer types, which is what we care about here, aren't very interesting because safe Rust can't dereference them, safe Rust is fine with you making a pointer from the word "LAUGHING" (not a pointer to the string, just the literal bytes in ASCII, but treated as a pointer) or from just some random bytes you found in a data file, because it's not allowed to dereference them so, cool, whatever, no harm no foul.
In unsafe Rust we're allowed to dereference valid pointers, but it's our job to ensure we obey that rule about validity, it being our job to obey rules is what "unsafe" means. So, that silly "LAUGHING" pointer isn't valid, it's just pointer-shaped toxic material. Even if, by coincidence, a pointer you have happened to have the same address as that pointer, in both C and Rust it's not OK to just go around dereferencing invalid pointers, they are not offsets into an imaginary huge array of all memory even though some C programmers act like they are.
Ignoring the Fil-C specific capabilities, in Rust the tearing issue is a matter of synchronization, which is something Rust cares about as part of delivering "fearless concurrency". Rust's marker traits Send and Sync are good place to start learning about that. Yes, we could unsafely implement these marker traits in unsafe Rust when we shouldn't, and thus enable what I imagine you'd call havoc.
So, mostly the problem is that your question is (unintentionally) too vague to answer well but I hope I was at least somewhat helpful.
I mean, it is true that a lot of his solos get busier and bangier until he's hammering out polyrhythms at the end. I just take it as part of the ride when listening to Brubeck.
But I really don't want to listen to other jazz artists emulate that, especially knowing how little chance there is that they'll have the same creativity and sense of rhythm that Brubeck had. (Edit: based on the experience of hearing the banging without the creativity/rhythm-- it's not fun.)
Brubeck suffered a serious spinal injury swimming in Hawaii which resulted in chronic hand pain, depriving him of some dexterity. He may have been a fluent and swinging improviser before that, I don't know. It all worked out, his quartet had a unique style and Desmond was such a great player and improviser.
> Every time something new happens in the world, my younger kids ask me about what they saw on Tik-Tok and their initial understanding is shaped by a well funded actor, and is often completely a false narrative.
As someone who remembers the near lack of anti-war voices on network/cable news in the lead-up to the Iraq War (Donahue on MSNBC being the lone example), I'd like to get more details on your strongest example here.
There wasn’t much but the mostly fabricated WMD narrative was questioned a lot. Now the current administration makes an endless stream of fantasies and lies which go almost entirely unchallenged.
> There wasn’t much but the mostly fabricated WMD narrative was questioned a lot.
Cable and network news did not question that narrative, aside from the exception I mentioned. Read David Barstow's Pulitzer-winning stories in NYT-- cable news shows even had retired generals pushing for war without disclosing all kinds of conflicts of interest.
Edit: I should add that in reality there were protests with record numbers of people during the buildup to the Iraq War, and there were many articulate arguments against the war by all kinds of people. However, that was not the narrative presented in Network/Cable News.
So what are the top 10 (or top 100) videos in terms of being actively replicated across the largest number of Peertube peers? I can't find this anywhere.
Prisoner's Dilemma Bonus: I'll upvote all responses if no responses attempt to explain Peertube's philosophy to me.
> But she also was frantic and obsessive and short tempered which was off putting.
My audio subsystem behaves exactly the same way!
Sometimes I'll send it a simple email politely asking to grab the block of samples it just sent to the soundcard and replace them with different samples that I've included as an attachment. It always makes this rude clicking noise at me which I do not appreciate at all.
I guess it's too much to ask to just take a little time to fashion a polite response while also hitting soft realtime deadlines. ¯\_(ツ)_/¯
