skysight-inc/HackerNews huggingface dataset:
This is an important principle. If essential systems in everyone's homes start depending on remote connections to work and/or including spyware that phones home with any kind of data about how the system is being used then that's a serious security and privacy concern. It's bad enough that we have metered supplies of various utilities and instead of the old "agent pops round to read the meter every few months" we now have smart meters phoning home with metrics every few minutes. At least the metering is there for a legitimate reason and the change to smart meters does have some real advantages including for the homeowner so the risk is more an unintended but unavoidable side effect in those cases. Almost everything else that goes under the "smart home" banner seems to be like smart TVs and connected vehicles: if it's phoning home then it's a good bet it's doing it for their benefit and not yours.
Sociopath is the wrong word to use, and that is the crux of the entire post. There's nothing so clear cut in this kind of situation. The parent isn't strictly trying to get something from the child with this apology. I think the parent is having their own internal struggle between validating the stuggles the child faced and understanding they were part of the cause. They lose sight of some things because they have an "ends justify the means" mindset. In a sense, they were okay being the "bad guy" so that their child was set up for the best future possible.
Love librivox.

Couple of tips:

1) atleast in United States you can use Libby app with a valid library card for non public domain audiobooks. However Wait times are going to be in pain.

2) I’ve created an iOS app based on librivox with additional functionalities like saving history, ease of use, sleep timers, offline , speed etc.,

https://apps.apple.com/us/app/librivox-audiobooks-zlibrary/i...
Hey that all looks great. Thank you :)
Might be better/more specific updates elsewhere

https://news.google.com/search?q=cubesats

I guess some people are used to it but to those old enough like me it seems technology is getting amazing.
> That's the point, you need an additional cable.

The humanity!
I've got to add my favorites too.

Rob Dahms 4 rotor: https://www.youtube.com/watch?v=JOmDj9iPs5o

This 240z: https://youtu.be/9PAHenR3JgQ?t=10

Le mans hybrids that sound like world destroying alien spacecraft: https://youtube.com/shorts/HXD5Gao4F5k?feature=share
and https://www.youtube.com/watch?v=FqyGJTioXnc
The stock compensation was crazily high that it was unbelievable.

Back in 2014, I told my family I earned 600k/year after joining as a new grad (with promo in a few years). My company went IPO and etc.

My family and cousins just couldn't believe it and insisted that I didn't understand the compensation and that it was for 4y. My cousin who is a lawyer in a top US law firm just couldn't believe it lolz.

I consulted a tax accountant, and they were "oh you are doing pretty well?".

I quitted the job after 4y and wanted to travel around Europe. I had to get a visa, and the German consulate just couldn't believe it too. They called and asked why I quitted my job... it didn't make sense to them.

People just didn't grasp the gravity of tech compensation.
> The argument in the complaint is that "OpenAI said they would develop software for everyone, but they gave early favoritism to YC companies, so they went back on their promise."

There are several different arguments in the complaint, but the most dangerous to OpenAI seems to be the accusation of principals using the nonprofit for commercial self-dealing which, notwithstanding that this is a pro se filing with a bunch of tangential conspiracy theories in its initial narrative seems both adequately pled and quite likely to be true from the information publicly available.

The big problem for the plaintiff is the theory of standing the complaint relies on, which while reasonably well-pled seems to be something the courts are likely to be leary of as it would grant open season on broad-claimed-benefit nonprofits.
> Maybe that’s why I like debugging so much.

I hate debugging.

Two big programming barriers I noticed as a kid were: (1) walls of complexity, and (2) debugging interruptions that took lots of time and ruined momentum.

I learned how and when to avert both barriers. And I love greenfield, partly because I can apply what I've learned about both. (And partly because I like working creatively, and with a holistic understanding of the problem domain and approach.)

It's great that there are people who dislike greenfield and love well-defined debugging tasks. I can trade them my brussels sprouts, for their chocolate cake.
Do you need to actively be connected to the internet while enabling bootloader unlocking, or does the phone merely need to have connected to the internet once at some point?

The latter seems reasonable to me in light of your point about enterprise enrollment. However, I'm confused by nelblu's post downthread[1], which describes using wifi to unlock used phones.

[1] https://news.ycombinator.com/item?id=35853135
The fact that a coordinator like a publisher exists isn’t necessarily in dispute. Sometimes it’s necessary to have a 3rd party coordinate reviewers, maintain quality standards, and settle plagiarism disputes. The issue is the price. It’s wholly unreasonable to charge $30 to read a paper, to charge a PI upwards of $2k-$7k to remove the $30 reader charge, or to charge whatever ungodly amount they charge libraries to offer free access to researchers.

Like I said, I’d value the service I get at a factor of 10-20x less than what they charge.

(Edited for formatting)
Does this have any benefit over Mnesia?
Actually your comment is a great demonstration of poor engineering leadership. You've already decided on an outcome and are shifting the narrative to adhere to this outcome.

The labelling of JVM + K8 as boring, to posture why it's automatically superior to "serverless integration crap" is exactly the sort of thing poor engineering leadership does to avoid having the sort of difficult conversations necessary. There's no metrics involved, no studies, no prototypes, no financial assessments, none of that it's purely based on emotion.

You can envision the same exact thing happening (but to the preference of serverless) on the Prime Video team.
> The developers of Lisp give you the full powers that they had to develop the language.

So someone joining the project doesn't just have to learn Lisp, they have to learn Inhouse Lisp? And the abstractions provided by modern languages are woefully incomplete?

> Lisp code written some 30 years ago will most of the time, without issue, work on a modern Common Lisp implementation

You could say the same about Java and 20 years.
This whole thing feels like "I installed Linux without reading how to do anything and it ate my hard drive and I couldn't fix my computer." just with large language models. But for some reason, ignorance is celebrated if it makes the AI stuff look bad.
I get it people. The hype is annoying, but you're not gonna fight the hype by failing to use the tool and then saying the tool just "cannot build a simple webpage"
Serverless actual pros:

"infinite" (meaning wallet level) scalability.

Integrated deployment tooling usually.

Integrated ingress usually.

Those last 2 really don't matter though as neither problem is that difficult if you know what you are doing. They both would have been a huge selling point in a world where k8s doesn't exist. Alas it does and thus mostly moot.

The first however is a big deal as managing very bursty loads on k8s can actually be a bit of a challenge. This is doubly true when you are using some sort of queue and don't have good queue scaling metrics for whatever reason. Serverless lets you cop out of managing that by using infinite concurrency.

Ok so now cons of serverless:

Turns all your code into spaghetti, this is probably the biggest one.

Cold boot performance is highly varible and generally worsens with added function complexity but this depends on tech choice.

Infinite concurrency is a bit of a curse. Want to use that MySQL DB that contains all your business critical data? Better use some MySQL Serverless proxy nonsense because unbounded connections isn't fun.

Lock-in is awful, migration story is awful.

Amount of Infrastructure as Code overhead, ala Terraform, CloudFormation, whatever else floats your boat to support serverless is insane. The sheer number of objects that need to defined, kept in sync etc is just bonkers. Not to mention if you have multiple services setup like this it's all boilerplate you either need to abstract or carry around.

Hides serious programming deficiencies like memory leaks because context is thrown away after servicing request.

Unpredictable runtime makes observability more complicated, probably forcing you into poor decisions as a result, i.e prom push gateway.

Runtime/execution time limits mean people trying to do all-serverless end up doing horrible things to accomplish long-running tasks.

All of the above leads to increasing pressure to make poor architectural decisions to work around limitations of the runtime.

I could probably go on but that is a reasonable set for you.

EDIT: Actually I forgot the worst con. The cost. The $/CPU/RAM cost of Serverless is beyond bonkers. When I was pricing up Cloud Functions vs Spot instances on GKE I think I came to the conclusion Cloud Functions are about 300x as expensive. If your code can run on serverless it can probably run on Spot instances which you can just add to your GKE deployment using another node pool and only schedule things that can handle nodes going away within 60s there and instantly reap 300x cost savings. This is because Serverless is sold at a massive premium to CPU list prices and Spot is sold at like ~30-40% of list prices depending on machine type (for those curious when I last checked T2D was the best for price/performance for highly single thread performance dependent workloads, ala Node.js)
It's not possible for consumers to signal that they would prefer an iPhone with a USB-C port instead of Lightning.
Recent Apple Watches use a tiny 60GHz very-short-range transceiver manufactured by STMicroelectronics for contactless data transfer.
Ublock Origin solves this with an option to block media elements that are larger than a configured threshold: https://github.com/gorhill/uBlock/wiki/Per-site-switches#no-...
We are thinking the exact same thing (w/ Az Functions). Keeping it simple as possible means you can forklift the whole thing in one afternoon to a different provider. It also means you could potentially even go back to an on-prem stack or whatever.

We are looking at taking our .NET6 monolith and "inverting" it so the entry point is our logical HTTP resources instead of the various DI monstrosities that emerge from main.

The reasoning for us is that we don't want ownership over all of the horrible things we could get wrong. If a <TLS1.2 connection some how gets established and something naughty happens because we forgot to update some startup.cs boilerplate, it's currently our pain today. Like legally. If we are just eating pre-approved/filtered/etc HTTP requests from inside our hermetically-sealed function environment, we get to cast a lot more blame than we otherwise would be able to.

I really don't get why you'd go to serverless and then shit it up with a lot of extra complexity. The whole point in my view is to inherit the compliance packages of your hyperscalar by way of directly using their native primitives in as standard a way as possible. This means you get to 'sail' through audits and engage up-market clients that are typically out of reach for everyone else.
In 2023, Brazilian banks continue to send half of their notifications exclusively via Push and the other half solely through email. This week, I once again endeavored to streamline the tracking process.

Here's what I did: I utilized an Android phone (which can be a secondary device) for the bank apps, and forwarded both notifications and emails to an Airtable base using Tasker+AutoNotification plugin and Zapier, respectively. This base served as the input for my automation scripts, which are also hosted on Airtable, though a self-hosted script might be more efficient. I set up the automation to run daily or weekly, sending emails and adding calendar events for my expenses.

Ideally, this functionality would be integrated into the bank's system as a simple plugin, but it seems they're not keen on helping customers save money or monitor their spending since Monday.

One advantage of using Airtable as the initial input is the ability to review items and remove (or rather, check a new column titled "ignore this") them before the automations execute. This is still a work in progress, but it's already proving useful.

(edit: rewritten with GPT4)
The unlocked bootloader warning screen isn't very different from what you described [1]. It says:

> The bootloader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device. Visit this link on another device: g.co/ABH

It's already pretty strong language (and very accurate! which is a rare combination).

[1] https://www.androidauthority.com/wp-content/uploads/2018/10/...
This is as disingenuous as OP is speculative. There are plenty of studies in non-bullshit journals demonstrating that millimeter-wavelength electromagnetic fields can affect voltage-gated calcium channels in the body. It seems highly unlikely that increased long-term exposure above natural baseline would cause autoimmune disease, but it also seems unlikely that it would have no other effect on the body.
If the audio of a phone call was pre-recorded on a good microphone it could sound awesome even over low bandwidth "voice" connections. Audio for voice calling is optimized almost entirely for latency. This means super short buffers and relatively simple encoding.

Streaming video/audio has a distinct advantage of not having the same latency sensitivity. It's not a two way conversation so if the stream is a second or two behind the wall clock as long as it's in sync you're never going to know unless you're watching a stream of an event you can see live, then you'll see the encode and transfer delay.

Besides latency, the microphone/audio input pipeline on a phone is in one of the shittiest recording environments it could be in. It's right next to the users mouth, sometimes far too close, so it needs automatic gain control to keep from being overdriven. It also needs to filter out the audio coming from the speaker lest it generates feedback. The microphone itself also needs to be very small and is attacked to the body of the phone so it's difficult to isolate from body sounds like the user's hand rubbing over the body.

The fact a cell phone can even transmit reasonable sounding voice is a minor miracle involving many thousands of engineer-hours. The extra processing power and bandwidth available today to handle wideband voice helps a little with quality but it's still very latency sensitive and still suffers vs less latency sensitive codecs or one-way streaming.
>I worked for several years

What jobs did you do during those years before going back to school?

Thx for sharing your story!
Do you mind sharing your qmk config?
I'm using homerow for modifiers and combos for symbols, barely using any layers.
Though idea of ditching homerow modifiers for layers not crazy since there is no arbitrary modifier need (cmd-c t etc can be thrown into a layer)
> connect the device to the Internet before they are allowed to install the operating system they want

Phoning home before undertaking such an activity takes away the ownership rights from the customers. They do not actually own these devices even after they have purchased them.

The reason is that an important part of their ownership rights, i.e. the freedom to use the software of their choice, has been withheld from them. With a promise that it will be given to them on request. Unless, of course, the manufacturer changes their mind.

Unfortunately, there are cases when the manufacturer did not even make such a promise and disabled bootloader unlocking permanently with no way of enabling it again. On Pixel phones.

This used to happen (and perhaps still happens) to some Pixel phones purchased in the USA from Verizon. They have been known [0] for disabling the bootloader unlocking and for giving their customers no way to enable it. Not even after phoning home.

Some people claim [1] that they paid someone from China to unlock their Pixel 1 phone remotely using some shady approach. I assume that someone with inside information from Google has leaked some software and instructions for doing so. It is unclear whether later Pixel phones sold by Verizon with locked bootloaders could be unlocked in a similar way.

As a result, it seems like the only way to have a chance at unlocking such Pixel phones, which have been made by a US company and purchased from a US carrier, is to pay someone in China and hope for the best. It has gotten that far.

[0] https://forum.xda-developers.com/t/how-to-unlock-bootloader-...
[1] https://forum.xda-developers.com/t/how-to-unlock-bootloader-...
There are currently many vacancies in the construction industry.
Well, the reason it shows "low contrast" on the page, is because the purpose of the page is to illustrate the low contrast problem. There are many sections that show the contrasting example of good contrast. What you're doing is running two virus scanners, and the second one finds the quarantine folder of the first one. You then claim the first antivirus is a virus. Nope.

This was not a website designed for mobile - that's why it doesn't look appropriate on mobile. Not every website is designed for mobile - in fact there are usually two completely different websites for mobile and desktop. This one is only for desktop. This complaint is like renting a sports car and complaining it's not doing a good job at transporting your piano.

There is one actually valid issue with the website though, which you do not bring up. It singles out websites for some reason, when the issue has zero to do with websites. Windows itself - all over the place - has ridiculous light gray on white, or light gray on dark gray (in dark theme). It's literally not readable half the time. Android has the same - now with more empty space, and page scrolling through 2 lines of tiny text and a toggle that changes description on toggle, so you don't know what it's doing. Heck, the service tag printed on the bottom of my silver dell laptop, is gray.

then we have things like expensive custom license plates with nature pictures and a tiny font. that all the drug dealers buy. and lastly - faces. the only way to tell a nose from a cheek from afar, is light-tan vs dark-tan (in the shadow). And with some people, the only way you can find them at night at all, is if they smile at your joke.
> But Lisp won’t compete in that field anyway.

I wouldn't say that. https://coalton-lang.github.io/20211010-introducing-coalton/
It soothes my nerves to see someone speak the unvarnished truth for a change.
So I’m guessing with this you’d use an alternative store like F-Droid instead of the Play Store? (Pardon my ignorance, I’m an iOS dev and have been for a decade; I don’t really know the Android landscape.)
k8s is not as hard as its advertised
> You could say the same about Java and 20 years.

Or even COBOL and 40 or 50 years. What does that even prove.

Edit: Typo
> How long until wireless charging is the default? Particularly combined with the iPhone's magsafe that allows charging to occur while the device is at any orientation?

Given how inefficient wireless charging inherently is... ideally never, by legal force if required.
The quadratic function that represents the hand waving away of k8s complexities causes a stack overflow exception.
The Protestant Ethic and the Spirit of Mastodon
Micro usb is close to being the worst of all worlds.
special word to distinguish those who drop out to work

We say those students are "on leave." Gates and Zuckerberg often
commend Harvard for its flexible leave policy. Given Harvard's
overambitious undergrads, the bureaucratic overhead of granting a hiatus
is a small price for the glory-by-association of a potential Microsoft
or Facebook. Come to Harvard. Even if you don't graduate, you'll be
rich and famous!
How else do you interpret insta-flagging any research papers that discuss vaccine injuries, other than people who got it not wanting to talk about it?
or every one time they successfully push a company to do something correct -- but ultimately trivial, like this thing -- there are going to be 10 cases where some bureaucrat makes a bad decision

This is a truism, but does it have any basis in reality? Certainly, if every manufacturer were forced to use USB-C for everything it could lead to an innovation problem, but I don't think makers of new products are forbidden from offering innovative kinds of connectivity, which the market might or might not decide to adopt. Nor is the issue trivial just because it's physically small, any more than the design of electrical wall sockets is of low importance.

They're making Apple do it because they have huge market share, a long history of foisting different physical connectors on their customers and generating a significant amount of electronic waste as older models are abandoned. Crucially, the charging devices end up being unwanted because they don't work with anything else including other iphones. Sure, they could enjoy a longer life with the use of adapters, but physical adapters are Not Great.

It's a pity, because Apple does innovate and some of their innovations are very cool, eg the magnetized charging ports on Macbooks was an Apple first iirc. But they also have a reputation for stiffing their own customers by ignoring backward compatibility , assuming that most of their customers will grumble but keep paying for the new model because they like the ecosystem.
Alan Kay once pointed out something along the line that when excitement exceeds knowledge you get fashion. For 10 years I’ve been in and around languages that were declared dead by the HN crowd because there wasn’t enough new hype around it. It’s not a perfectly inverse correlation, but honestly at this point when I see HN is excited about something new it raises red flags for me.
It's not emotion. I make money from porting people off of poor technical choices onto solid ones. It comes from experience working with all these various systems.

I have used (at large scale) GAE, Google Cloud Functions and Lambda, before that I also used all the previous "serverless-like" things including Beanstalk (anyone else even remember that?), Heroku and bunch of other PaaS things for various stuff.

It's all come and gone. To me serverless is just the latest in a long line of things that I get paid to replace with things that actually solve the problem and doesn't turn into a ball of spaghetti that no one is able to modify anymore.
I would be very interested, I'm afraid you won't be able to put it very deep in this thread though!
> IANAL too, but if there is indeed a legal case for material misrepresentation, it would make more sense to be brought by OpenAI shareholders

The case is for material misrepesentation to benefit OpenAI shareholders at the expense of the identified intended beneficiaries of (and donors to) the OpenAI nonprofit. Why would the beneficiaries of the fraud challenge it?

> or the FTC, not some random dude from Texas.

The law often creates multiple different parties with a legitimate and enforceable interewt in the same requirement; while the plaintiff here doesn’t have the strongest standing claim in the world, it is not diminished for thr fact that some of the allegations create much stronger claims for, say, the IRS and state tax authorities or donors to the nonprofit (particularly the accusations of the nonprofit being fraudulently organized and operated for self-dealing for the commercial benefit of certain of its organizers.)