lsowen

A very good YouTube video from Munroe Live (an engineering firm specializing in "design for manufacturing") explaining it: https://youtu.be/dCO633KE7RA "Axial Flux Motors Explained"

Edit: a video from them on this particular YASA tech being discussed : https://youtu.be/m507ryWhc6c

Have you tried the FUTO keyboard? I actually find I prefer it to gboard now.

https://keyboard.futo.org/

Super interesting approach to build a custom productivity suite. Anyone else done anything similar or know of projects to build something like this?

Passkeys _may_ be synced, but that isn't guaranteed. For example a "device bound passkey" isn't synced.

I use a similar model to this extensively.

1. Hotels where you have to pay a "connection fee" you only have to pay once

2. I travel with a chromecast that can connect to my private network

3. I run wireguard, so all my traffic back is automatically encrypted

4. I can position this to get a better wifi signal, "boosting" the signal (via my private network) for all my devices

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

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

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

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.

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.

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!

It might be rare, but it _can_ happen: https://www.youtube.com/watch?v=ZdIclqha014

I think they likely meant "trawling": https://en.m.wikipedia.org/wiki/Trawling. (ie casting a net and "fishing" for open ssh)

A good resource, with all the broods listed, including the two that are going to emerge this year (North Illinois Brood and Great Southern Brood) and the typical ranges of each brood: https://cicadas.uconn.edu/broods/

It is a reference to a TV show: https://en.m.wikipedia.org/wiki/American_Greed

It took THREE YEARS (August 2020 - August 2023) to fix the vulnerability? I'm not sure the size of the Harvest team, but that still seems insane.

What?! How do you do this? I love magic but haven't discovered this.

Previous submission and discussion of the game itself: https://news.ycombinator.com/item?id=35905876

Better info directly from Bitwarden: https://bitwarden.com/blog/bitwarden-passkey-management/

Same for us, with two things to add:

1. Make "living documentation" part of your culture, so that the new hire feels empowered to extend and improve the documentation as they are using it to come up to speed.

2. Have proper production access controls, so that the new hire can be comfortable poking around without being afraid they can break something.