web007

> As for "a British accent". Would an American say there's "an American accent"?

Of course, just the same as British. "American accent" for foreigners usually means "Southern Foghorn Leghorn" e.g. Daniel Craig in Knives Out, but can also mean New York, Boston, Chicago, Dakota (aka Fargo) or some other variation. To Americans it really means "unaccented" Midwestern English, aka broadcast (radio or TV) voice.

Americans know "American accent" from "British accent" by the same standard, the British "unaccented" voice is called RP and sounds posh or overly fancy to most Brits, but Americans don't distinguish RP from Cockney, Yorkie, Jordie or any of the other variants. RP is the broadcast voice.

To be clear: I used to be the same. "British" was one accent that Michael Caine, the Queen and Chris Ramsay all spoke. (For Americans: "Robert DeNiro, Harrison Ford and Dolly Parton have one accent" is equally wrong and hilarious.)

> When people claim that they are just telling the truth and can't be blamed, it is likewise nonsense. We are always responsible for the words we speak and the actions we take. We're not let off the hook just because it's true.

Please consider https://sso.tax/ before making that an "enterprise" feature.

It's absolutely delightful to see concepts come many full circles like this. I remember the Cray-2 cooling towers as the most futuristic computer in the world even in the 90s, and it inspired me to sink my old system in mineral oil in the early 00s. I did the research and found the stuff in the Cray towers (Fluorinert) was $many/gallon, and the smallest volume they sold it was something like 55gal drums. Mineral oil was $cheap enough, also inert, and so I got a 5 gallon tub of the stuff. I built a plexiglass case, sealed it with silicone caulk, overclocked the CPU, hooked up an industrial-strength aquarium circulation pump and... rapidly went nowhere with a disgusting, oily motherboard. And a ridiculously heavy case filled with, essentially, hazmat.

It was a terrible idea back then and still seems bad today. I'll be interested to see what the next cycle brings, if it's back to spot cooling or if immersion really is the way of the future.

I'll have to go and get the source and compare it to AAC. I'm really curious why that was left out of the comparison since it's the modern equivalent of MP3 (aka MP4 audio). It feels disingenuous.

Make your statement "This ain't got nothin' to do with that malarkey!" and move on, there's no need to throw a tantrum and take your ball and go home. It's like a conflict of interest statement, "yes" or "no" are both acceptable answers, just say something.

For others who view this DEI addition as positive, it gives them an explicit place to call out areas of focus. For people who are looking for DEI-impacting work it's a much simpler filter than abstracts or full papers.

Of course, but how do you solve that problem in the general case?

When everything lives next to everything else it's harder to draw the line around the blast radius of a change. If there was a repo boundary, that's a really easy hard constraint.

We actually do use bazel, where I have a love-hate relationship with that as well.

It's incredibly painful and a lot of overhead to bazel allthethings. Using bazel to define dependencies is another double-edged sword where you can get them enumerated, but EVERYTHING has to use it. You can't check out a repo and go, you have to check out the repo and bazel whatever you're trying to do. No "I know Python, let me venv && pip install -r requirements.txt or pipenv ...", now you have to incant the magic bazel incantations instead of native stuff. Same for NPM/Yarn, Rails, Go, etc. And that's assuming there's good support for your language/framework of choice; a Rails acquisition a few years ago was awful because bazel didn't have good support for it.

We have a double digit number of humans on our DevEx team dedicated to this stuff, and it's still painful. That speaks to the effort you're talking about.

On the love side, being able to query for "what does this dep trigger a rebuild for" without guessing is about as good as you can get, and having a requirements.txt-equivalent that magically packages itself into a standalone set of files with minimal effort is pretty sweet. The overhead to get from 0 to 1 is a lot (like... A _L_O_T_), but 1 to N is easy.

You get everything for free, but you also have to take EVERYTHING.

I work primarily on "cloud" stuff, so 95% of my world is Terraform and other (asynchronous) configuration-based stuff. I feel the pain more acutely because of the overhead imposed on my work that shouldn't exist, vs compiled software deployed for end-use-cases where there is an expected burden of build + test.

Because monorail, all of my changes go through the same tests and restrictions and review as executable code. We have to "pass the build" - and waste resources testing all of that executable code for every change. It's even worse being in a pseudo-regulated space (SOC2 / similar) since anything applied to any sub-part of the repo applies to everything.

You can argue that parts of the repo can use different processes, but then what's the benefit of keeping it all together vs having different repos with those different processes?

The only reason monorepos are better today is that git sucks at multi-repo (think submodules), and humans suck at separate repos. It might also be that nobody takes it far enough, where you have separate repos for everything, but that feels like the first two points both together; maybe tooling and/or a massive DevEx team could make that work. I'm pretty sure something would need to supplant git for subtree repos to work and make sense, until then the monorepo is the least bad option of all the bad options.

No single company has "the ability to exercise total control" on the internet, otherwise Kiwifarms / DailyStormer / 8chan would all be offline. This is not censorship, it's cause and effect or consequences or the free market depending on your slant.

Free speech is limited to that - the speech is free, but you have to pay someone to make it available on the internet. Cloudflare decided the cost-vs-profit equation was unbalanced, so now KF will need to pay some other entity more for the cost they will be forced to incur, or need to not have risk of reputational damage e.g. 1776 Hosting, Epik, SkySilk, foreign countries.

I'm pretty sure KF could win damages, but that's not the point. It's more expensive (reputationally) for Cloudflare to continue to provide service than for them to settle damages, even treble damages, for this one expensive customer.

ImageOptim is fantastic. You can use it via CLI, so I've added it to a few different archiving / publishing workflows in the past. One thing that some people don't realize is you can run it multiple times on the same (PNG) images and get better results. Each filter is dependent on the input from the previous filter, so running them again can give you better results even after one run. This works out because filter 3 might give you some savings or rearrange the data in a way that filter 1 can now take advantage of.

The other JPG filters are lossless, but be aware that Guetzli is lossy!

I was impressed with just how much it could losslessly compress some massive JPGs until I did a visual diff. I can't see the difference, like one-bit deltas sort of thing, but it's not 1:1 lossless as I would expect.

It's not that they can't scale, it's that you want them to HAVE to scale, to make it more expensive to attack your site than another one.

Looks like a decent implementation of HashCash - great! They should implement TOTP-based nonce generation to avoid the need for a database entirely, that would make the system much more lightweight to deploy.

Some people miss the point of this. If you and another person are running away from a cheetah (fastest land animal) then you don't have to outrun the cheetah to survive, just the other person. The same is true for sites getting away from spammers. They will go for sites that are easy to attack before yours, so as long as the effort outweighs the outcome you're safe. It doesn't matter if the solution isn't perfect, it's better than nothing, and if it's not widely adopted it's not worth the effort to bother cracking.

Sterilization is a big deal.

Doctors make a big deal out of it because of history - forced or unwanted sterilization has been a problem in the past, especially for marginalized people. The difference between men and women's experiences are infuriating and MUST be addressed, but the sentiment is correct.

A successful vasectomy ends in a 50-50 reversal-to-conception ratio, including not just pregnancy via intercourse but by any means necessary (fertility treatments, IVF, etc.). Even this minimally-invasive and "easily-reversible" action is considered permanent. Any permanent sterilization (in CA, not sure about rest of US/world) has a default 30-day waiting period, with the ability to waive down to a minimum 72-hour required delay between consent to permanent sterilization and having the procedure.

Making a permanent decision is not something to be taken lightly, it will be interesting to see what other outcomes of Roe v. Wade change behavior and expectations of large populations.

TC included RSUs this year, with a fixed-dollar conversion for the quarter after grant - $XYZ dollars, to be divided by trailing N-day stock price on $date and granted as RSUs. Roughly, grant ended up at $5 conversion rate, by the time we could sell it was $4, and now it's $2. So $100k in comp is currently selling for $40k.

I haven't heard anything about an adjustment or the possibility of additional grants. For now I'm more concerned that we're approaching break-even on my ISO valuation from 2+ years ago, after a 52-week high (during trade blackout) that would've given me Dos Commas status.

https://en.wikipedia.org/wiki/List_of_common_misconceptions should get you started.

The author is charging more for access to the feature you want. You need to pay more to get that benefit, just like you need to pay more for early access or whatever other perks are offered.

> We believe that developers do not and should not care about things like VPCs, security groups, etc.

I very strongly and fundamentally disagree with this sentiment. I know they don't, but they should!

Developers should understand how and where and why/why not their code is deployed. They should understand what their security model is AND HOW IT WORKS, because if they don't they will 100% without fail open their SG to 0.0.0.0/0 and embed hard coded passwords (usually "password", or "p@ssw0rd" at best). They should know what a VPC is, but maybe they don't need to know anything beyond "private network" and probably "NAT is involved".

Hiding these concepts is a double-edged sword. You get the simplicity of "make me a database" but don't understand why or how it works. You don't have to fiddle with security groups, until you do and then because you don't understand them you go with 0/0. You don't have to think about VPCs until you rack up a $10k bill because you never considered how you could route between instances vs round-tripping out of the VPC and back in through a LB - twice.

This project seems to wholesale ignore "terraform modules" in it's claims about reusability and modularity. Most of the problems it solves are already solved.

The description and marketing are very mixed. It generates bespoke Terraform based on... vague descriptions? "Give me a postgres DB" seems to be the level of input from what I can tell. It then goes off to create one and give you the TF it used? I was really hoping this was "automatically generate Terraform FROM AWS" to import existing resources.

This sounds like the SaaS-ified version of Gruntwork.io, where they give you best practices templates and leave it up to you to fill in the particulars.

1000 _participants_ on a call, or 1000 _viewers_?

Our org switched from Google Meet to their streaming equivalent once we hit around 250 people, nothing worked well with that many participants.

Lucky for your org, streaming has been a solved problem since the 90s! It looks like Jitsi might support streaming by itself, or you can find online tutorials on Nginx + Varnish RTMP streaming and DIY if you prefer.

To answer your literal question, there is no enterprise grade open-source zoom alternative because it's incredibly difficult and hard to make work for free. You have seen how hard just in your N=1000 sample size. Adding in self-hosted STUN or TURN or building your own proxy and video muxer is only going to be harder. There's a reason YouTube, Twitch, Facebook, Instagram, Vimeo, etc. are good at it, because they're zillion dollar companies that can afford to invest in the massive infrastructure and engineering required to make it not-terrible.

How is this possibly true? The argument that 16-bit DCT somehow gives better precision AND doesn't change the size of the encode makes no sense. If you get better precision you need to keep those extra-precise bits that are no longer zero due to truncation.

I haven't seen this argued as 16-bit DCT, but in color space conversion. The gist is that all 8-bit RGB values cannot be represented properly in 8-bit YUV420, so you're supposed to use 10-bit to get "proper" YUV values. But if you start with an 8-bit encode you've already thrown away the extra precision, so why waste the (considerable) extra compute on 10-bit just to make sure you don't truncate the already-truncated YUV?

I have a project in progress to measure all of the variations, but from quick testing with CRF encoding the same value results in much longer compute AND a larger file in 10-bit versus 8-bit. The larger file has a slightly higher VMAF score, as would be expected from spending more bits. The work is in finding a set of encoding parameters to measure the quality difference at the same output size, and to measure the relative improvement across CRF vs size vs bit depth.

Your personal dislike of cloud SSO is not the same as "their attitude towards privacy". Before you do anything "permanently" you should read their reasoning behind that decision:

https://tailscale.com/kb/1013/sso-providers/

> Tailscale works on top of the SSO/IDP/IAM identity provider you or your company already use.

> We don’t support sign-up with email addresses. By design, Tailscale is not an identity provider: there are no Tailscale passwords.

> Using an identity provider is not only more secure than email and password, but it allow us to automatically rotate connection encryption keys, follow security policies set by your team (e.g., 2FA), and more.

You can BYO SAML provider if you like, you'll just have to pay for it: https://tailscale.com/kb/1119/sso-saml-oidc

https://the-eye.eu/public/AI/ for a couple of the models shown, as well as the input training data "The Pile" used for GPT-J-6B.

They're... a bit weird. The sources are biased toward "internet content" IMO (Literotica, HN, GitHub, Stack Exchange), versus traditional sources like newspaper articles or other professional writing. Some of the other sources might balance that out in that they're as dry and complex and squeaky clean as you can get (EU proceedings, case law) but I'm skeptical it won't end up as least common denominator tweetable content that's missing the detail and style of more professional pieces. I know the OpenAI GPT series was trained partially on Reddit content, so that as a baseline isn't much better.

I'm a little confused about the cement example. Every inch of rainforest is preserved in year 0, so those factories can produce their ridiculous amounts of CO2 to compensate for the now-safe rainforest. That works IMO since the annual capture of an acre of rainforest is equal to one emission-credit worth of factory. (If that's not how the math works out then that is a fundamental problem that can be solved.)

That's all year 0.

The author forgot about year 1, 2, 3, etc. where those factories would still need to offset their production. Where are the offsets for those years?

The article also neglects some of the point of paying money for offsets, which is paying to research those alternatives that are required to get to true net-zero or negative emissions. They are VC for science that could solve the problem, funded by those causing the problem.

My phone is for me, whether or not FAANG et al gets some value out of it.

I get more utility out of my tech interactions on my phone than I give to "various spy enterprises". I use many services to their maximum, IMO negating most of the benefit they gain from loss-leader products that are their bait for me-as-a-product.

You _are_ being tracked and monetized. Your devices _are_ fingerprinted, and your demographics are tabulated and collated. The modern web doesn't have an effective opt-out (Ye Olde Web didn't either), so you may as well go all-in and extract as much value of your own as you can from the system.

Semi-Professional: https://geekportfolio.com/

Made as per it's name, a portfolio site when I was trying to get a professional gig. Haven't updated it in a long time.

Very-Unprofessional: http://www.dullsville.com/

Emo/cringe site of my youth. Think MySpace-style decor, but way way stupider. Every once in a while I'm tempted to rebuild it as-is with modern techniques, but it's just so bad that I never bother.

Newest-Thing: https://yoloprod.dev/

My version of "how things should be" - I'm working to expand it with more detail, and I even have a #yoloprod t-shirt!

I can't believe that this is the highest-resolution photo of the sun that ESA has taken. Surely earth-based telescopes have done better?

A guy in his backyard takes pictures with similar resolution: https://twitter.com/AJamesMcCarthy/status/147297870519032217... (downscaled for Twitter, approx 9Kx9K / 81Mpix on his Patreon feed)

That's not usually a problem. You can transfer a registration with N years remaining, the new company will charge a one year registration and you now have N+1 years covered.

The only time it becomes a problem is if your new registrar doesn't support N+1 year registration - your 8-year example means you need to find someplace that supports 9- or 10-year regs.

The answer for a few of those is easy: desync them by ±3.5 hours and then let them drift evermore.

If you don't use the 6pm feature it doesn't matter if the time is accurate. I have a rice cooker that's permanently blinking 12s, and two TVs that I have no idea what time they're set to because I stopped updating them for DST and there has been a power outage or two since then.

If you're unlucky and _have_ to have everything in sync then you've chosen your pain, so good luck to you. =)

I read the title and was surprised to find the article isn't about AJamesMcCarthy - he has an amazing ISS-moon transit picture from a few months back.

Turns out he (of course) saw this one, and thinks it's better than his own: https://twitter.com/AJamesMcCarthy/status/149619122880292454...