skysight-inc/HackerNews huggingface dataset:
doesn't seem to work well for me. volume up and down sometimes register 1 count, sometimes 2, sometimes none. Deleted shortly after install, worried about what it's actually doing rather than counting.
Maybe we should have the government develop societal software. You know, outside of military applications.

There's basically three organizations worth talking about. Governments, Corporations, and non-profits. If Corporations and Non-profits are out, the remaining one to do something is Government.
SSN might be the least of the problems in some cases in terms of the info leaked...

What about people who have called suicide helplines, abortion clinics, loan servicing, etc...

With the numbers available, that will be possible to find out...
Why would they need to borrow when they can continue to sell commodities (which the EU and US continue to buy, btw)? Besides, there's no indication that they are running out of reserves. Wasn't one of Putins first moves to get off of foreign debt?
GitHub's notifications are the worst. Completely useless; nay, infuriating.
That's the first thing they should improve IMO.

Whilst I do get the _motivation_ behind collapsing large files in diffs, because you want to keep the number of DOM elements low, come on... you really _cannot_ hide the lion's share of changes in the PR and get away with it. At least make the collapsed files stand out more so you don't actually miss them when reviewing. Or, I guess you didn't want me to expand them, or you did all that collapsing effort for no reason. So what was the point again?

Org gists were proposed like 10 years ago, but still not in place. Seems straight forward enough...
My understanding is that regardless of funding, the US federal government has standardized pay scales that top out way below what private industry pays, so even well funded agencies can only possibly get junior developers/IT or people that are willing to take a significant (50-80%) pay reduction. The very most you can possibly make as a GS15 in 2024 is 191,900, and they have locality-adjusted pay with most localities being below that.

They might also generally still drug test? I don't even do drugs, but I'm not going to pee in a cup for someone to effectively do charity lol. Good luck recruiting a professional with decades of engineering experience when you treat them like they're a 16 year old working at Taco Bell. Even someone with 0 years doesn't have to deal with that kind of treatment in industry.
That's billions of lines of code if it's just Golang. I would imagine most of that was autogenerated code that no one was reviewing. This is not a problem with monorepos.
> Injecting spider venom isn’t dangerous as long as you get the dosage right.

Venom actively damages your cells, CO just restricts oxygen access.

> If doing this makes it possible to perform better, people are going to push the edge of the amount that’s “safe“. Right up to the limit. Tip toeing over the limit.

Not necessarily. It’s not like EPO where more is better, the benefits likely cap out long before you reach a dangerous level of CO, so going to “the limit” isn’t something that’s likely to happen.

> It’s CO. there’s a reason the government is always telling people to make sure they have carbon monoxide detectors.

Yes because your boiler might leak an uncontrolled amount of CO and, because it’s odorless, you don’t know if you’re breathing too much before you pass out and, subsequently, die. That’s a different situation than being in a controlled environment where you can set the dosage quite easily.
Over in Europe this blanket saving of phone records beyond what it is necessary to operate would have been illegal in many countries, and is in general incompatible with the European Convention for the Protection of Human Rights and Fundamental Freedoms outside of active threats to national security and temporary measures overseen by a court.[1]

There's really no reason why any service providers should save this stuff in the first place, and it isn't hard to fix with legislation. Just make it illegal to even keep.

[1] https://curia.europa.eu/juris/document/document.jsf?text=&do...
For that matter, dagger (dagger.io) provides an sdk in multiple languages and gives you the full power (and then some extra on top) of buildkit.
> It definitely involves way more magic than spring for sure!

Elixir and Phoenix really strive to keep the "magic" to a minimum. Bending your mind the functional way instead of the OOP way, and learning how Elixir macros really helps dispel the magic and realize it's less excessive cleverness as Ruby/Rails often indulges in and more just the benefits of FP.
Ideas around point-based rendering have been around for a long time. But, have not been widely used. Hollywood and games might use them for smoke, water, explosions, but rarely for solid objects.

There has been a big explosion of interest in the area since this release of https://repo-sam.inria.fr/fungraph/3d-gaussian-splatting/ which proposed a way to generate the point cloud data from photographs in a way that is procedurally a lot like photogrammetry. Hundreds of research projects have spawned off of that paper.
Well, it seems we have arrived at an impasse.
GitHub’s most important product at this point is probably the API. It’s incredibly comprehensive so it’s easy for tools to augment or replace pretty much any part of the experience.

So many teams with private repos only use GitHub for the basics (version control, access management) and then use third party compatible tools for the rest. Linear for issues, Buildkite for CI, Graphite for code review, etc.

The API allowed me to build CodeApprove (codeapprove.com), which is the code review interface I always wanted GitHub to have. And teams that share my preferences can use it a la carte without losing the rock solid foundation of GitHub.

I know it’s not great that we’re all locked into this platform that is owned by a megacorp that hasn’t always been friendly, but it’s at least a great platform.
At present this is unclear. But on the other hand, think of all the potential new prion diseases!
So for example you don't find copilot useful?
Creating multilingual step-by-step instructions can be a real pain in the neck.

But fear not! With Castofly Technologies & OpenAI, you can create guides in pretty much any language you can think of—even Klingon (probably)!

Start your free trial at: https://www.castofly.com/
Critical Exim bug bypasses security filters on 1.5M mail servers
It's funny how cancelled projects are somehow making people almost more "nostalgic" than projects that actually shipped. One of the reason may be that cancelled projects don't need to be completed, to ship with a reasonably good quality, to have an easy to use interface, to be sustainable for a long enough period of time, etc.
From my understanding, traditional photogrammetry typically generates 3d point clouds from image pixels by correlating visual features between images with known camera parameters, allowing the camera pose of each image to be estimated in a shared coordinate space. These point clouds are postprocessed to estimate closed surfaces which can then be converted into textured triangle meshes to be rendered using traditional 3d rasterization techniques.

Gaussian splatting represents a scene a cloud of 3d gaussian ellipsoids, with direction-dependent color components (usually represented using spherical harmonics) to deal with effects like reflections. The "Gaussian" part is important, because gaussian distributions are easy to differentiate, making it possible (and fast) to optimize the positions, sizes, orientations, and colors of a collection of Gaussian splats to minimize the difference between the input photos and the rendered scene. This optimization is usually done by starting with the same 3d point clouds and camera poses estimated using the same or similar tools as traditional photogrammetry (e.g. COLMAP), and using this point cloud to place and color your initial Gaussian splats. One of the key insights in the original Gaussian splatting paper was the use of some heuristics to determine when to split a splat into smaller ones to provide higher detail over a given area, and when to combine splats into larger ones to cover uniform/low detail areas.

The nature of Gaussian splats being essentially fancy point clouds means that they can't currently be easily integrated into existing 3d scene manipulation pipelines, although this is rapidly changing as they gain popularity, and tools to convert them into textured meshes and estimate material properties like albedo, reflectance, and so on do exist.
> I'd still consider going through an older book, you'll learn 90-95% of the same thing.

Seconded. I have the book, and it's pretty easy to understand where the differences are. And worth learning the pre 1.7 Phoenix because a lot of the changes thereafter make so much more sense when you know the pain points that motivated them.
> It's really nice to have reliable tools that you can learn once and continue using a decade to free your mind up to master other parts of the job.

I strongly agree, and it's weird how much hostility I encounter from folks who think the opposite. There are an endless amount of interesting and/or useful things to learn in this industry; spending time relearning how to do a mundane task in an app I've been using for a decade is a waste.
At&t customers are bound to individual arbitration so there will be no class action lawsuit for this.

> Please read this Agreement carefully. It requires you and AT&T to resolve disputes through arbitration on an individual basis rather than jury trials or class actions.

https://www.att.com/legal/terms.consumerServiceAgreement.htm...
Along these lines - the life story of Abram Petrovich Gannibal, https://en.wikipedia.org/wiki/Abram_Petrovich_Gannibal, who was Alexander Pushkin's great grandfather, is jaw-dropping incredible to me. I'm really surprised a Hollywood movie hasn't been made about him.
It's not an ad hominem. Matt Taibi was fed partial information by Musk, and decided to publish it anyway, losing all credibility in the process. And even though the data was hand-picked by Musk who had the biggest axe to grind, it ultimately proved nothing beyond the fact that Twitter was receiving numerous requests from all sides of the US government, and that they would scrutinize every request and respect only some of them. Going back to the original claims you have made, Taibi's reporting only showed what was happening before Musk took over, not after, so it doesn't back you up. Sorry if I sounded harsh, but I'm just blown away you ate this journalistic slob up without any critical thinking.
I don't think that the design is that old. I was working as a web designed ~11 years back and a lot of these design ideas were "in" back then. The subtle dark and light 1px lines that create this embedded effect, some shadows around certain elements, not a completely trivial typography. This is a 2010-2014 type of design.
> “Le Thière” is French for “the third”

Is this true? I know modern French is troisième, but I'd never seen this before, so I googled. There seems to be nothing on the internet about it, and remarkably few matches for Thière beyond misspellings of théière (teapot), which makes me think the authors of this article just made this up.
Sterile neutrinos could also be a lot heavier than regular neutrinos, those kind of sterile neutrinos are ideal candidates for explaining dark matter and the matter-antimatter asymmetry

https://arxiv.org/abs/1303.6912

Just as I am disappointed that "global warming" changed into the more ambiguous "climate change", I'm a little disappointed that the "right-handed neutrino" has turned into the "sterile neutrino". It's really strange that we only observe left handed neutrinos and either the revelation that there is a hidden right-handed neutrino or that neutrinos are fully Majorana particles without a right-handed form would be absolutely groundbreaking.

My take on it is that the neutrino mass term is not "physics beyond the standard model" but rather a "missing part of the standard model" and that one way or another, neutrinos hold an important secret, if not the important secret of the universe. (Note potentially three generations of right-handed neutrinos could exist at three mass scales and explain the gallium anomaly, cold dark matter, and the rarity of antimatter)
I would have fought the "has no function" angle instead of suggesting it was "just for fun."

In actual fact, it does have function. I have personally asked "is it Tuesday?" more than zero times in my life. This app functions perfectly in helping answer that question.

Seems no different than a weather app in terms of its function - it communicates real time information about the day.
Google is (still) a great tool for this sort of conversion. It comes up with just under 58 barrels: https://www.google.com/search?q=57+tonnes+%2F+%286.1+g%2Fcm%...
Thank you! I read your blog post and checked out your project! If I understood it correctly, you’re trying to build a software engineering team in a box. Basically from first issue, to code, to live apps. Very interesting approach adding the collaboration angle! ASTs are neat but I’d imagine it could get hard to manage with more complex code.

In our case, we regenerate the `main.py` file each time. One of the hacks we did was to start with boilerplate code, which is why you see it modifying the code as opposed to generating from scratch the first time. We also feed the model with some context/rules on app building using our web framework, so the output is more bounded.

We haven’t tested it on really big files yet, though I'd imagine it could be a problem later. At the moment, we don’t generate HTML, JS/TS, or React code from scratch so our files tend to be relatively smaller than if we did. Our UI is defined via the `properties.json` file, which abstracts much of the underlying code, therefore keeping the files small. It’s much easier for LLMs to generate json and map it to UI behavior, than generate of the client code needed to do all of it.

We don’t have issues with the LLMs changing function/method code, but it occasionally implements one of boilerplate methods we didn’t explicitly ask for. In those cases, a developer has to remove that code manually, which is why showing code diff is critical.

Many other hacks come down to lots of prompt engineering! Something along the lines of "Only implement or modify a method/function corresponding to a user's prompt. Leave all others intact"

Happy to chat more!

Also you might find this blog post we wrote interesting:
https://www.dropbase.io/post/an-internal-tools-builder-that-...
sneer. sneer. sneer.

heck, that sounds like three cheers. so i should abbreviate it to three sneers in future. :)

so, three sneers, for
yet another blindly downvoting hn hive mind bro type who can't handle even an innocuous opinion (like my "never liked that decision" comment above), just because it is different from their own opinion. in other words, homo intolerantis.

there are a lot of such jokers on this site.

who cares about that behaviour, though? not me, for sure. hn is just some site, not important in the real world, except for those people who have nothing better to do than hang around here all day or night, and snipe at and try to put down others. iow, trolls and loser types.

as amy hoy said somewhere a while ago, maybe on her site or on twitter, fuck hn.

look, uncle darwin, i discovered a new (creepy) subspecies of homo sapiens, who i hereby name homo intolerantis.

:)

keep downvoting me, bro type, even pull in your friends to do more of it, and thereby waste all your time, and get ulcers and high blood pressure because of my innocuous comment, probably you have a lot of free time because of no job because of layoffs, while i have a good laugh at your stupidity and cheap malice.
The thing that's really legacy in GitHub is the code review flow, which is likely one of the surface areas that corporate customers use the most.

Actions and Codespaces have been huge and transformative, so it's disappointing that core functionality like code reviews hasn't seen the same level of improvement.

Basic features that Phabricator had nearly a decade ago are still missing:
- highlighting copied/moved code blocks
- gutter indicators for code coverage
- stacked diffs
- not collapsing large changes by default (what a ridiculous default! "A lot of code has changed here, meaning it's likely bugs may be here - I'll hide that for you to make your review easier!")

And I don't recall how well Phabricator supported it, but handling rebases sanely by carrying over comments and showing diffs from prior PR versions across rebases would be amazing. The number of times I have to re-review an entire PR in GitHub because it can't show what changed since the last review if the author rebases their branch...
I got a check in the mail last week for 12¢ from Google hoovering up my data. Yes, that's twelve cents!

Google certainly made more off of my data than that.
I feel like ctrl/cmd f has taken a whole hit in general throughout the whole web. It used to be this really reliable tool that got you quickest where you wanted to go to.
So your solution to a problem that exists because there isn't enough capacity to go around is to compound that problem by having even less capacity?
I think it's a perfect little detail that captures this writer's persona. Their blog is powered by the (once famed, and very popular) Octopress [0]. Every developer was running their own blog off of it.

My point is, it looks like the author found something that works... for over a decade and well. They wish GitHub would 'just work'

0: http://octopress.org/
This blog seems to be one person's passion project. They can write whatever they want to in whatever manner they want to.

They're not required to weather your scrutiny or to pass your bar exam to be allowed to post whatever they want.

Aside from that, you raise good points, but you can very well ask your questions directly to the author using the comment section of their blog, you're somewhat more likely to get a satisfying answer there than here.
But, if it supports 40A charging it'll charge at 40 amps unless you back off the charging rate (which nobody does, typically). You'd always assume 40 amps for circuit purposes.
100% agree.

Absolutely amazing platform.

In fact, surprised it has remained high-quality even past acquisition and overwhelming adoption. I would expect scope creep to grow unboundedly.
CodeUpdateArena: Benchmarking Knowledge Editing on API Updates
It's not a bug, though. Like many web sites these days, they don't load the entire page upon navigation as a deliberate design choice to save bandwidth and resources of the client browser.

I've been bitten by this one before as well. Looking at the files tab of a pull request, I hit ctrl-f and started typing the name of a file I knew was part of the PR, and...nothing. No hits. Couldn't find it.

It wasn't until I scrolled down a little bit that the JS on the page loaded more of the diff and THEN the file I was looking for appeared in the list and could then be clicked to scroll to that file.

This kind of lazy loading saves system resources for both client and server, but reduces usability.
There isn't any correlation between the quality of product design and how the bits arrive at your browser.
https://app.electricitymaps.com/zone/DE?wind=false&solar=fal...
If $PROGRAMMING_LANGUAGE = go, you might be looking for https://github.com/containers/storage which can create layers, images, and so on. I think `Store` is the main entry: https://pkg.go.dev/github.com/containers/storage#Store

Buildah uses it: https://github.com/containers/buildah/blob/main/go.mod#L27C2...

Edit: buildkit seems to be the same, used by docker, but needs a daemon?
I worked at an EV charger manufacturer. This is a known issue. The issue is a 240V plug value engineered for non-continuous use for things like cooking and laundry loads (where amperage spikes but levels off at fairly low amps) versus a continuous 7-10 hour load like an EV/EVSE (where you have high amps continuously and lots of resulting heat transfer).

It's limited to home EV charging. This is one reason why given the choice between a NEMA plug source or a hard wired source (to circuit in Junction box), I would choose the wired source/circuit connection.

The plug manufacturers also know about the melted NEMA connector issue and are designing versions for continuous use at the higher price points mentioned.
Is that the only possible sterile neutrino? Because if I recall correctly, a right chiral neutrino cannot change into one of the other types, because of the chirality. (That's why it's "sterile".)

So either they aren't produced by beta decay, or they are but they can't be captured by gallium, or we're seeing a sterile neutrino in a different sense. ("Sterile" because it can't interact with gallium, but not sterile due to chirality.)

If I understand, the conversion of gallium into germanium is exactly a beta interaction. (But I may not understand, because it seems to me that gallium->germanium should emit a neutrino, not absorb one.) So I have a hard time seeing how a neutrino could be emitted by the source, but not absorbed by gallium. I could more readily see it as saying that there's a fourth type of neutrino that they cycle through, and while in that fourth state it can't convert gallium. But that wouldn't be "sterile" in the chirality sense.
You might want to read the article a bit closer: It's complaining about exactly that.
> Even if the "home-made vodka" description is accurate, it doesn't imply that they made the drink themselves.

It's explicit and spelled out in the first quote I posted. They made it themselves.
I didn't know about Whistle! Just contacted their support, asking if it would be possible to detect seizures. Thanks a lot!
Thanks! Url changed from https://gizmodo.com/very-annoyed-seagulls-are-waging-war-on-....
You're being pedantic here, but missing the point. The parent implies that they "go out of their way to keep their employer's code proprietary" because they are paid for it.

I was merely noting that they are not paid for that. They are paid to [solve problems] (which I expressed as "write code").
You could try my new LiveView course: http://phoenixliveview.com/

If you have a Rails background then I have another course specifically for you: https://phoenixonrails.com/

Or click here to buy both together: https://arrowsmithlabs.com/checkout?bundle_id=1 ;)

</selfpromo>
International Committee of the Red Cross rules of engagement for civilian hacker
You likely cannot file in small claims and would need to pursue arbitration instead.

> Please read this Agreement carefully. It requires you and AT&T to resolve disputes through arbitration on an individual basis rather than jury trials or class actions.

https://www.att.com/legal/terms.consumerServiceAgreement.htm...
It might have been necessary to stick with the NT 3.51 codebase. I think they broke the clean separation of the GUI from the rest of the OS in 4.0, which was launched that year, for performance reasons.
Bear in mind this is a prerelease app on TestFlight and that Apple would not allow this behavior on the App Store, or even on apps notarized for alternative stores in the EU:

> 2.5.9 Apps that alter or disable the functions of standard switches, such as the Volume Up/Down and Ring/Silent switches, or other native user interface elements or behaviors will be rejected.

Infamously, there was a third party camera app, Camera+, that turned the Volume Up button into a shutter release. Apple pulled it from the store—and then released the same feature for the built in Camera app.

https://forums.appleinsider.com/discussion/112111/popular-ip...
Or just use CI/CD on a build server to create release artifacts and a proper security setup (no PAT's, or use short living one)
Are there positives? Probably not.

Anything positive would require some effort to spin it that way.
Software, not private circuits

If only AT&T had some kind of way for its computers to talk to one another without going over the public internet…