And also didn't know how to work thr radio? Surely autoland doesn't disable communication

seems like an unlikely rumor to be true at this time

Only the GET requests are metered. An anti-bot/anti-AI scraper measure?

Maybe some kind of anti-fraud measure too?

So much spam would go away if we just charged $1 per 5000 emails. Normal humans would be fine. Mailing lists would need charge, but it would be minimal for most useful mailing lists.

Maybe Amazon is going after some fraud?

They probably want to remove pricing transparency.

Generative pretrained transformer, I think? https://en.wikipedia.org/wiki/Generative_pre-trained_transfo...

It’s actually generally prime t-bones

I'm not sure I agree with Karpathy's "the next wave of programming languages will be natural language", but I'm even more concerned about The Big 3 consulting firms message of how businesses _must_ integrate AI into _everything_ or perish.

FYI, the FAQ link in the footer (https://grayjay.app/faq) appears to be broken (throws a 404)

Has anyone tried openobserve (https://github.com/openobserve/openobserve)? How does it compare/contrast to Quickwit as an "Elasticsearch for logs" replacement?

The purpose for internship programs generally are to grow the interns skills and establish a talent pipeline, _not_ for their immediate "code lift".

Unless you think that AI is going to completely replace developers, then there will remain value in having interns.

My former FAANG uses internships at the Ph.D. level for both recruiting and talent acquisition. Hiring committees have a way easier time assessing candidates with feedback like "this intern implemented X, Y, and Z beyond their project spec W during the summer" or "this intern goofed off all summer."

The situation is not as dire as it first appeared. While the messaging wasn't handled very well, where everything is settling out is good, with pluggable auth and an open source reference implementation: https://lakefs.io/blog/why-moving-acls-out-of-core-lakefs/

I'm also wondering the same thing. It has a bunch of very nice capabilities, but taking away such a basic piece of functionality to push people towards the paid options is very concerning.

I raised concerns about deficiencies of their RBAC on their Slack before and they immediately started pushing me to their enterprise offering. I thought it was a red flag but have not imagined they would stoop to this.

When we started using them they seemed like a genuine open source. Is there a term for open source traps like that? If not we need to come up with something. Trapware?

Could be called some kind of https://en.wikipedia.org/wiki/Bait-and-switch , or BAS = B(ullshit)A(ssisted)S(ales)?

Yep, it fits

Received an email from treeverse.io today:

>You might have noticed in our documentation that Access Control Lists (ACLs) will be deprecated in an upcoming release of lakeFS OSS, scheduled for this quarter. Future versions will support only single-user access.

> While I believe this change won't impact your current use case, I wanted to reach out proactively. If you foresee any challenges with transitioning to the single-user model, please let me know. I'm more than happy to arrange a meeting to discuss and find a solution that ensures you can continue using lakeFS without disruption.

> Simultaneously, we will be adding new features to lakeFS OSS as part of this release (stay tuned!). These features will enhance the platform, though they will not focus on user management.

> Feel free to contact me if you have any concerns or would like to discuss this further.

Super annoying that such a basic feature is being removed. But they are happy to sell you a version with the same capabilities!