xmodem

This obviously varies a lot by jurisdiction, but non-profits typically have much stricter transparency requirements than for-profit entities.

Oh my god. As someone who can't see well enough to get a license, but somehow can see bollards just fine as a passenger: If you can't see them, you shouldn't be fucking driving.

> Comparing ... might be more fair,

I don't make purchasing decisions based on what's 'fair', I look at what capabilities I have, what I lack, and what my budget is.

> Why does that seem the same to you?

Exchange rate. But you make a valid point that I should also factor in inflation.

> We’re in a ray tracing thread and for ray tracing, there’s no contest, the 4060ti wins there by a long way.

It wins in the sense that it can do ray tracing while the 1080Ti cannot, but based on my understanding, the xx60-tier cards aren't viable for raytracing at 60fps without DLSS anyway, and I'm still not convinced I want to consider DLSS performance to be the number I care about in my purchasing decisions.

> UserBench says today the 4060ti is 17% faster for 20% lower price today,

The most important question I look at is "what games can I run at what resolution" and I don't think there's a single game I can get acceptable performance at 4K on a 4060Ti or even a 4070, that I can't get acceptable 4K performance on a 1080Ti. There are probably a couple that I could run at 1080p that I have to run at 720p currently. I'm not using a variable/high refresh rate monitor and i'm not playing competitive shooters.

1080Ti vs 4060Ti. Factoring in nvidia's price creep and a worse exchange rate, the 4060Ti costs today roughly what I paid for my 1080Ti 7 years ago.

I'm comparing perf by looking at sites likes userbenchmark and reading/watching reviews of newer cards. I'm running into games I can't play at a level that I'm happy with, but based on reviews I don't think a 4060 or 4060Ti would make a meaningful difference.

See this GN review: https://youtu.be/WS0sfOb_sVM?t=666&si=Xt62b_2BfQM-fnuH

Specifically, at 4K, the 3060 outperforms the 4060 in Cyberpunk. Most of the charts do show a gain, but I'd describe it as marginal rather than modest.

Put another way, they took the gains in technology and process improvements and banked them for themselves, releasing a new generation that achieves similar performance (in some cases worse) to last gen, albeit at an improved power envelope, at the same price as last gen, but that they have higher margins on.

The fact they can do this speaks to the lack of competition in the GPU market at the midrange and up. Compare this to the CPU market, where we now have Intel and AMD giving it everything to leapfrog each other every 6-9 months.

I don't begrudge nvidia wanting to spend a generation consolidating their market position - that's their right - just as it's mine to look at a GPU that performs roughly the same as one I bought 7 years ago at almost the same price and say "no thanks".

Anyone who has browsed through one of these personal VPN services - or even a DIY VPN from a datacentre IP - for more than about 10 minutes will have experienced the increase in captcha's.

Hell, the same things were said about Shkreli, and he served 6 years 5 months of his 7 year sentence.

The biggest inequalities in the system exist before anyone ever gets charged. And when you go and blab about your crimes to anyone who'll listen, you end up negating much of the benefit that more expensive lawyers can bring you.

The linked timeline from JetBrain's side doesn't exactly shower them with glory - taking more than a week to respond to with CVE numbers is not ideal. But the linked toot states:

> it's super inappropriate to lie to researchers who disclosed this to you responsibly about what your plans are.

That would be super inappropriate, yes! But Rapid7 hasn't alleged that publicly that I've seen. All I have seen so far is researchers alluding to bad behaviour and deception, and no concrete or falsifiable accusations.

Cutting Rapid7 out of the disclosure is definitely poor form, but that's a far cry from lies and deception. As a not-totally-disinterested outside observer (using JetBrains' IDE products but not TeamCity) I definitely want to know if they are behaving badly so I can factor that into my future plans. But without a concrete falsifiable accusation it reads to me like butthurt on the part of the researchers involved.

What deception are you referring to? I don't see anything in the linked article that I would consider to be an accusation of deception.

At one role our GitHub access was mediated by a CI job that would export users and groups from Google Workspaces and apply them to GitHub. The script would helpfully print a list of actions taken, and we had a general policy of CI logs being world-readable - and this job was no exception.

It was a useful way to keep tabs on any skulduggery that was going on.

Unrelated, but Confluence has very powerful support for email alerts on changes. These include notifications of deletions, and the email includes the diff of the deleted content. One thing I do at any org that uses confluence heavily is set up notification rules on some interesting spaces and check in from time to time.

It's been a hot minute since I had to dig into the code Apple publishes for anything and since then they seem to have moved it all to Github. I don't have my mac handy to try building it, but I don't see any references to a rootless.h in the code they're publishing. I'm curious to know a bit more about what's missing.

Exactly- 20 seconds is the number I arrived at after a bit of trial and error.

https://github.com/AddictedCS/soundfingerprinting Is the library. It was the first thing I found and it seemed to do the job. I’m not a .NET guy so it’s implemented as a CLI tool that takes a wave file as input and spits out a list of timestamps.

Sharing the code would mean getting into the business of publishing an ad blocker which is not something I personally have the bandwidth for. It’s also far from my finest work, being something that I banged out in a weekend. Happy to answer other questions about it, though!

The current implementation searches only within a single episode. Searching across multiple episodes could be done but would introduce false positives if a show re-uses intro music or other assets, and personally I’d prefer to keep that stuff, so I’d need to figure out heuristics to differentiate it from ads.

On macOS you can also access related symbols by long-pressing keys. Obviously for large blocks of text you're still going to want to switch layouts but for a quick IM reply or typing a couple of characters I think it's faster.

I've written a podcast ad blocker. I'm not based in the US but listen to a few podcasts from large US-based networks. They don't have any ad inventory to sell so instead they fill the slots with ads for other shows on their network and I end up hearing 7 copies of the same ad for the same true crime sludge in each podcast episode.

It works by fetching the XML feed, downloading the file and applying an open-source audio fingerprinting library to identify timestamps of the same segment repeated multiple times, using ffmpeg to delete all instances of repeated segments, and republishing a new XML feed that I then consume with a standard podcast app. It works surprisingly well.

I dunno man, personally I try to avoid living my life by walking right up to the edge of what's legal, and I don't admire or respect that trait in others either.

Ableton comes from Germany for instance - not my cup of tea personally but by all accounts great software.

Samsung meanwhile has a significant software development presence in California.

An embellishment can often be put down to a difference of opinion, and vendors have a reputation for downplaying vulnerabilities.

In our case, the media reported the researcher's claims uncritically alongside our denials. We decided the best strategy was to say as little as possible, as saying or doing more wouldn't improve the quality of the reporting and would only risk drawing more attention to the false claims.

I think we had a good track record of handling vulnerabilities well, and we definitely had some nasty ones. But this was not one of them.

Not necessarily - see the recent bogus curl CVE's for instance. There's a lot of incentives to invent or embellish vulnerabilities for street cred or other reasons.

Many years ago, a 'researcher' made claims to the media that our product had a zero-day that looked like a deliberate backdoor. They refused to tell us anything about the bug.

I would never buy a smartphone based on whether it could receive FM radio, and if I had a smartphone that could, I would probably never use it. But the article makes the point that FM radio can work just fine in emergency situations where the mobile network is overwhelmed, and having that capability available could be life-saving.

I love hating on C as much as the next guy but I think we should wait until we see the vulnerability before jumping to conclusions.

At my last job I used a dummy iCloud account at the system level, but you can log into a separate account for the app store, which was necessary to avoid having to re-buy some apps I depend on.

Just as I was leaving they were in the process of replacing everyone's computer with new ones that were much more locked down.

I think we have a rather specific example of a Chrome bug hosing OS installs. Had SIP not existed, there's virtually zero chance that bug wouldn't have been caught before shipping.

The point of Asahi is to provide linux drivers for Apple hardware. What would be the point? You can already run Linux in a VM on arm macOS today with good performances. You don't even need to disable SIP.

The two other conditions listed in the page you link basically amount to "the buggy code has to run". Related, I think SSV [1], introduced last year, would also have blocked this bug even with SIP disabled. But none of that invalidates concern that areas of the OS we don't know about might not have the level of defence in depth that we would like - it's not like Apple has never cut corners or shipped bugs to hit a date.

1: https://support.apple.com/en-gb/guide/security/secd698747c9/...

It still has them, of course, but the concern is that after ~8 years of SIP basically ~everywhere, platform security decisions have been made assuming it is present.

This concern is definitely not totally unfounded, back in 2019 Chrome shipped an update that rendered systems with SIP disabled unbootable: https://support.google.com/chrome/thread/15235262?hl=en

> I'm in favor of duck-typing these words

Hard disagree. A subset of behaviours resembling or even "indistinguishable" from understanding should not be enough to meet the definition.

Maybe some day we will have AI systems that get there, but LLMs ain't it.

We looked at OVH's managed kubernetes offering but it is hideously expensive compared to, say, DigitalOcean/Vultr,