tredre3

That line was authored by Claude. There you go: https://github.com/leonickson1/Swiftlet/commit/3ac64020eadcb...

The question is how many new bugs were introduced through those AI fixes.

Is it less than a human would have? Is it more? Is it the same type of bugs?

I could be convinced either way and it's an interesting thing to ponder in my opinion.

I personally would never give a mastodon community to a random individual if I had to step away. This is problematic on a privacy and operation level, not to mention the time it would take to interview people. Which means that if I didn't already have a second-in-command, the community would be shut down.

If it were a forum, then asking long-term contributors and moderators if they're interested in taking over is certainly an option. But it's not, there's likely no natural "hierarchy" that develops on a mastodon instance.

They could conceivably ask another established instance if they'd like to take over the old domain, though.

> Reddit is just full of the worst behavior. People think nothing of just being incredibly, incredibly rude to strangers and ther insights are often banal.

Reddit grew up as a community of edgelords. Trying to be funny by exaggeratedly insulting others is just how it was. Think a community of Ben Shapiros. Coming to the site as an outsider could be brutal until you got used to ignoring it (or engaging, if you're into it).

Eventually normal-adjacent people took over the site, which caused a boon of interesting topics and diverse opinions for a long while. The rude-to-be-funny thing never quite stopped, but when it went too far it was moderated or downvoted away.

I'd agree that things have been going downhill for many years now. The peak of genuine and quality engagement is long behind us. LLM-assisted comments are certainly not helping (I'm not talking about bots, I mean people who direct LLMs to write their comments).

This is good advice however it should be noted that many of espressif's other purely software components depend on esp-hal, so you still want it to compile if you use any of espressif's provided components.

ALTER TABLE is very limited in sqlite3, though they've been improving it (search the page for " 3." to find the version-specific changes). Any significant schema change is usually simpler to create a new table and copy the data.

I think this is deliberate to make a point. Even an AI doesn't use that many em dashes. GP wants you to question it as a "haha see? I'm human yet you called me an AI just like I thought!"

It depends how you define dangerous, I suppose.

- Before everything was IP-based you could occupy a large number of lines and making it impossible for more calls to go through (i.e. 911). It's called TDoS and could be achieved through phreaking.

- You can spoof your caller ID to make your scam more convincing.

- You know how when you call your voicemail from your phone you're not asked for your PIN? The voicemail system only checks your caller ID to know it's you and skip the PIN. So, again by spoofing your caller ID and calling the voicemail number you can access listen to anyone's voicemail. This doesn't work on all providers, many have now reluctantly fixed the problem.

And 365 days probably aligns with 100% of scenarios. It doesn't mean it's a good idea, because the longer the delay is the more downsides you also get.

Blocking a maintainer from pushing updates for a full month after changing their e-mail would be obviously absurd. So Github would have to add a way of enabling maintainers to super-uper-duper confirm the change and cut the delay short. Which is likely not currently possible, hence starting with a shorter delay.

> just some random feeling the user has in the moment

That is the risk you take when you spam the user with popups begging for a review after a specific action. If the user isn't satisfied with the result or the popup disrupt their flow, they will (rightfully) be in a bad mood when they review your app.

I'm curious how your project compares to plain mmap!

Because llama.cpp will already run 26B in 2GB of RAM if you really want to (mmap enabled, repacking disabled).

It seems like the main difference is that your project synchronizes the SSD reads with inference activity, which you've presumably tuned to cause the least latency possible? Whereas the OS wouldn't care about any of that.

And 1.125lbs is easier to write than 1 pound 2 ounces, yet Americans will look at you with a blank stare if you don't use ounces.

When it comes to units, you can't please everybody. Especially if it's tangentially related to the old colonies.

> Not to mention, that I really don't understand how IPs are supposed to be provisioned to devices on IPv6.

SLAAC is the only way that works across all IPV6 devices. In that mode, the router advertises the prefix and the device assigns its own address (prefix + its mac address).

DHCPv6 exists but is poorly supported. It sucks for people who like assigning IPs individually from an authoritative place (through static dhcp entries on the router). But people like us are "doing it wrong", you see? We must accept that in this brave new worlds an IP means nothing.

Namecheap's privacy WHOIS still shows a unique email address so that the owner is reachable. Sending mails to it would have been forwarded to OP.

> Namecheap has been owned by a private equity firm for several months now.

Namecheap's cavalier attitude long predate private equity, let's stop blaming the evil financiers for everything. I'm sure it's going even further downhill from here because of it, but what happened to OP happened to others before as well and is par for the course when being a namecheap customer.

But what does bun bring to the table in that scenario? Why not interface with javascriptcore directly and skip the (unmaintained) middle man?

Bun provides the node standard library, I suppose, but you likely don't want it in a plugin system. Because the bulk of it is to deal with web requests, or to allow system-wide file/network/process access. So you're going to re-implement your own safe library anyway.

No, he is saying that if they were to replace natural gas with electricity, it would use 2.2 gigawatts of electricity.

I don't think the conversion is as straightforward as they claimed. But they're also not claiming that they currently pull gigawatts of electricity.

- People don't need cloud backups

- People's files aren't valuable

You're making a lot of claims that are so blatantly false from what I see on my side that I don't know what to make of it. Are you projecting your own needs onto "people"? Or am I the one who's disconnected, and people truly don't care about losing all their photos?

I disagree with your blanket statement. The vast majority of (commercial) PC games were never that small, even in the 3.5" heydays. Most games required 2-10 disks.

To me the spirit seems to be that it should run on your average Windows machine without any external dependencies and without a web browser.

Your average PC has half a dozen .net runtimes installed but likely not the correct .net version you want (yay), so to me it seems like it would be out. Same for the various C++ redistributables, better not rely on that unless you ship the DLLs you need with it (which I don't think you're allowed to do per Microsoft).

https://2pgarcade.com/contest-144mb.html isn't much more elaborate than the article unfortunately.

If the best someone can do within that 1.44MB constraint is a pico-8 game, then so be it. But I bet we're going to see much more impressive stuff!

Competitions for 16KB games exist. as well as 64KB. And likely everything between 0KB and 1440KB. It doesn't reduce the fun to have multiple tiers, in my opinion.

> Make -> ninja

I would disagree on that one. Ninja config might not be turing complete, but they're generated by turing-complete tools (usually cmake). Nobody writes ninja by hand, thus I would argue it's irrelevant!

> PHP doesn't suffer from that because there are barely any libraries for it.

You don't need many libraries in a typical project, because PHP is batteries-included and if you use a framework it does all the rest for you, that is true. But there are still hundreds of thousands of packages with billions of installs:

https://packagist.org/statistics

PHP offers that safe API, though, and always has (prepared statements). The same one as all other languages.

PHP might seem worse than other languages due to a combination of factors:

- It's the most used one by far, even though few of us like to admit it.

- Old tutorials still come up during web searches, so "SELECT * FROM `table` WHERE id = $id" will still be written today.

I suspect you missed the joke: A web shell is a script to execute arbitrary commands, i.e. Remote Code Execution.

Surely a PWM of 10,000Hz wouldn't allow for night sky photography. With full exposure it can already take minutes of hours to take a night sky a photo.

And it's usually recognized that 1,000hz is the bare minimum to spare sensitive individuals from symptoms, with 2,500 usually used for safety margin. Then you have to account for some jitter in the synchronized network so you're looking at at best a 1/5,000 exposure.

Is that sufficient to be worth the trouble?

> The night will still feel odd and "soulless" even with 2700k LED street lamps so long as they're still the absolute worst CRI.

What makes you say that the CRI causes the lack of soul? I'm not saying that you're wrong, but given that CRI is objectively better than it ever was now, why?

The sodium lamps we used previously had a CRI of 25-35. The absolute worst white LEDs we have have a CRI of at least 60.

Most fruit crops need 8-12 hours of darkness but it changes depending on which point they're at in their life cycle. 20 hours of light is usually fine during the initial stages, then they require 8-10 hours of darkness to bloom, then back to 18-20 hours of light during the fruit growth.

(I'm not a botanist or a farmer but I grow greenhouse veggies for fun)

So far accessing old storage media from 50+ years ago hasn't really been a problem. Reading old tapes and punch cards/tapes or even early hard drives is something that a single motivated hobbyist can achieve in a few weeks or months with a microcontroller and patience.

But it's more difficult to imagine that 1000 years from now someone will be able to read from a PCI-E NVME drive if the specs get lost along the way (ignoring for a moment that flash storage most likely won't retain data that long).

Property lines disputes happen every single day in America, too. It's a universal thing.