I know you're well within your rights to post this, but would you consider replacing your comment with something like "It's easy to find working keys on github if you search the appropriate terms"?
Think of it this way: although you're not to blame, HN drives a lot of traffic to your preconfigured github search. There are also bad actors who browse HN; I had a Firebase charge of $1k from someone who set up an automated script to hammer my endpoint as hard as possible, just to drive the price up. Point being, HN readers are motivated to exploit things like what you posted.
It's true that the github search is a "wall of shame", and perhaps the users deserve to learn the hard way why it's a good idea to secure API keys. But there's also no benefit in doing that. The world before and after your comment will be exactly the same, except some random Gemini users are harmed. (It's very unlikely that Google or Github would see your comment and go "Oh, it's time we do something about this right now".)
EDIT: I went through the search results and confirmed that the first several dozen keys don't work. They report as error code 403 "Your API key was reported as leaked. Please use another API key." or "Permission denied: Consumer 'api_key:xxx' has been suspended." So at least HN readers will need to work hard(er) to find a valid key.
I'm not opposed to even removing the comment outright.
That being said, GitHub does not even offer a time sorted search. Meaning that most of the results are going to be quite old and useless.
Second, API keys being shared on GitHub is quite an old problem. People setup automated scans for this sort of stuff. Me removing my comment isn't going to help anyone who already posted their API key online.
How do you honestly benchmark a framework that only has a documentation of a hello world against laravel which has about everything you can think of...
There are millions of Macbooks out there that will be out of MacOS support one day. If this project diverts just a fraction of them from becoming e-waste for a little, it will be a win.
And then beyond that, there is simply no laptop manufacturer that meets the quality of Apple's hardware design. I like Macs for their hardware, the software is a compromise. A linux macbook would be my ideal laptop.
Maybe so, but 15-20 year old laptops are definitely starting to show their age.
An M2 MacBook Pro, on the other hand, is only 4 years old, has a fairly OK keyboard, and is still in striking distance of current high-end ultrabooks when it comes to performance.
The only thing my X230 struggles to do is run LLMs locally. My needs are simple, and I think normal people (i.e. probably not most people on this site) don't have needs that are any more demanding than mine.
Granted, this is running GNU/Linux rather than Windows. If you're running Windows then yeah, they show their age.
I think an X230 would be performant enough for 95% of the things I do, but a 14 year old CPU is going to have pretty terrible battery life for anything more than very light usage. And things that would be light usage on a recent PC, like watching video encoded with a modern codec, would be fairly taxing on an old CPU with no hardware decode.
True. By the time I upgraded from my X200 (fantastic machine, noticeably outdated), the lack of software support for hardware decoding H264 was noticeable. Also being stuck with OpenGL 2.1 isn't the best either.
I don't know what I'll do if and when my X230 stops being sufficient. If I could buy an Apple motherboard in an X200 chassis I'd do it in a heartbeat.
Congrats, but I think you may be in a small minority when it comes to developers shopping for laptops.
Personally, I had to upgrade from a late-model i9 MacBook Pro to this M2 MacBook Pro, because the npm + docker setup at work was taking upwards of 20 minutes for a production build...
>The only thing my X230 struggles to do is run LLMs locally. My needs are simple, and I think normal people (i.e. probably not most people on this site) don't have needs that are any more demanding than mine.
People who edit video or make music and other such tasks are totally normal too, and there are hundreds of millions of them
I think maybe you don't understand what the needs are of normal people. It's only partially about what software they run.
I recommend Mac's to the people in my life because when they have a problem they can take the machine to the Apple Store in the mall. Or if they want to understand iPhoto or Pages better, they can go to the Apple Store and take a class. They like Apple laptops because they look nice, they feel great, sound amazing (for a laptop) and have excellent battery life.
Like you, I have a ThinkPad (a P-something) and, frankly, it kind of sucks. It's all plasticy, it flexes, battery life is a joke, the trackpad is meh, and the fans are almost always running. I do like the keyboard though (I'm a fan of backspace).
> The only silver lining is that newer devices will have to scale down memory, so developers will have to ditch memory-sucking frameworks and start to optimize things again.
No. Prices will just go up, less innovation in general.
Aren't all DLLs on the Windows platform compiled with an unusual instruction at the start of each function? This makes it possible to somehow hot patch the DLL after it is already in memory
Sorry to say but how you are framing things is simply not true anymore.
You are not required to buy their "Glasfaser Modem 2" you can buy any ONT Modem.
You are not required to use any of their equipment, they give you the data to connect via PPPOE directly.
I bought a house with FTTH in 2023 and never used any Telekom hardware. Nobody forces you to use the peer DNS. The telekom DNS isn't complying to https://cuii.info/anordnungen/ because they want to but to avoid being sued everytime some company wants to block an illegal streaming site.
For practical purposes there's the problem (at least a few years ago?) though that Akamai in particular uses DNS to steer you to the correct portion of its CDN and the default IPs returned by independent DNS resolvers tended to have relatively abysmal peering with the Telekom network that was getting completely overloaded at peak times.
Unfortunately "use <insert favourite DNS provider here> everywhere except for Akamai CDN, for which use the Telekom DNS" isn't something that consumer routers support, so you'd have to start running your own custom DNS resolver to work around that problem…
Comparing Redis to SQL is kinda off topic. Sure you can replace the one with the other but then we are talking about completely different concepts aren't we?
When all we are talking about is "good enough" the bar is set at a whole different level.
I wrote this article about migrating from Redis to SQLite for a particular scenario and the tradeoffs involved.
To be clear, I think the most important thing is understanding the performance characteristics of each technology enough that you can make good choices for your particular scenario.
We're talking about business challenges/features which can be solved by using either of the solutions and analyzing pros/cons. It's not like Redis is bad, but sometimes it's an over-engineered solution and too costly
I wish you'd have expanded on that. I almost always learn about some interesting lower-level tech through people trying to avoid a full-featured heavy-for-their-use-case tool or system.
That is truly honorable perseverance