skysight-inc/HackerNews huggingface dataset:
Show HN: FoxBot – a personal robot, a simple XSS aggregator to Slack
I've been running this for a while now and decided to make it public because I find it quite handy. It runs on a Raspberry Pi Zero and enables me to not have to check the news all the time. I get these aggregated hourly bursts of notifications for things I care about. There is a bunch of other code I need to bring over from when it was a private project, such as web page scraping etc, but as it stands I think it's pretty useful.
This can be easily attacked with two scammers executing a MITM attack. One calls the bank to impersonate you and steal your money, the other calls you to get your app code.
6^16 != 16^6
Only people who don't understand stock trading fundamentally would say that. You have a completely different risk profile when you sell short vs when you take a long position. You pay market interest on borrowed shares (which can eat you alive), you may get your position recalled by the lender, you may take a margin call. Being right at the wrong time is the same thing as being wrong when you're short -- not when you're long. Intelligent traders would take a short position involving options as a hedge - or would sit on the sidelines and not bother.
Per Wikipedia:

> As of October 18, 2024, the domain has not been standardized by the Internet Engineering Task Force (IETF), though an Internet-Draft describing the TLD has been submitted.
Speaking as someone who is very critical of the general "raise infinite money and grow grow grow" approach to startups (it's a big part of why my company is bootstrapped [1]), I think there's a really important difference between making money and raising money.

Raising money is about convincing investors that you can solve someone else's problem. Or even more abstractly, about convincing investors that you can convince other investors that you can convince other investors that you can solve someone else's problem. That's enough layers of indirection that signaling games start to overtake concrete value a lot of the time, and that's what gets you your Theranoses and your FTXes and the like. You get into "the market can remain irrational longer than you can remain solvent", or its corollary, "the market can remain irrational long enough for you to exit before it wakes up".

But making money means you are solving a problem for your customer, or at least, that your customer thinks you're solving a problem with no additional layers of indirection. And if we take "making money" to mean "making a profit", it also means you're solving their problem at less cost than the amount they're willing to pay to solve it. You are actually creating net value, at least within a sphere limited to you and your customer (externalities, of course, are a whole other thing, but those are just as operative in non-profitable companies).

I think this is one of the worst things about the way business has done today. Doing business, sustainably and profitably, is an excellent way to keep yourself honest and force your theories to actually hold up in a competitive market. It's a good thing for you and for your users. But business has become so much about gathering sufficient capital to do wildly anticompetitive things and/or buy yourself preferential treatment that we're losing that regulating force of honesty.

[1] see my HN profile for more on that if you care
Maybe worth noting that it is real-analytic.
Kudos for effort but some dealbreakers here. Hope it makes more progress.

Currently about 10x slower than standard C (ranging from 3x to 20x)
Only works on Linux/X86_64
You're not wrong, but if your code is full of bespoke types that are only relevant to a couple of places where they're used, you hurt interoperability; you lock yourself in to how things are done now; and you may just be shifting the burden of making sense to someplace else in the code.

If you are able to formulate types which can be grasped without reading and re-reading their code - that's a win; and if you are able to express more of your code in terms of more generic non-trivial types and data structures, which are language-idiomatic - then that's a double win, because you're likely to be able to apply library functions directly, write less code, and have your code readers thinking "Oh, variadix is just doing FOO on the BAR structure, I know what that means".
> No amount of remote attestation and "transparency logs" and other bombastic statements like this would make up for the fact that they are fully in control of the servers and the software. There is absolutely no way for a customer to verify their claims that the data is not saved or transferred elsewhere.

You are right. Apple is fully in control of the servers and the software, and there is no way for a customer to verify Apple's claims. Nevertheless system transparency is a useful concept. It can effectively reduce the number of things you have to blindly trust to a short and explicit list. Conversely it forces the operator, in this case Apple, to explicitly lie. As others have pointed out, that is quite a business risk.

As for transparency logs, it is an amazing technology which I can highly recommend you take a look at in case you don't know what it is or how it works. Check out transparency.dev or the project I'm involved in, sigsum.org.

> they are almost guaranteed to be misusing that data

That is very unlikely because of the liability, as others have pointed out. They are making claims which the Apple PCC architecture helps make falsifiable.
An application powered by a single source file comprised of only 400 lines of code is, by my definition, trivial. My needs are more complex than that, and I’d expect that the vast majority of folks who are trying to build or maintain production quality revenue generating code have the same or similar needs.

Again, please don’t be offended; what you’re doing is great and I dearly appreciate you sharing your experience! Just be aware that the stuff you’re demonstrating isn’t (hasn’t been, for me at least) capable of producing the kind of complexity I need while using the languages and tooling required in my environment. In other words, while everything of yours I’ve seen has intellectual and perhaps even monetary value, that doesn’t mean your examples or strategies work for all use-cases.
I made a little test survey to examine the generated code. It's the only way to answer your question.

The code that's executed on the user's browser is too long to copy here, but there's nothing in it that's talking to anything surprising or concerning as near as I can see.

The survey requires a backend to process the survey responses, of course, and the application gives you a choice of using Google sheets directly or using the backend code they provide on your own server. This is that backend code:

function doPost(e) {
// uncomment this to filter domain
// if (e.parameter.origin !== 'yourdomain.com') {
// return ContentService.createTextOutput("Invalid domain");
// }

var sheet = SpreadsheetApp.openById("").getActiveSheet();
var data = JSON.parse(e.postData.contents);

sheet.appendRow([data.question0]);

return ContentService
.createTextOutput(JSON.stringify({"result": "success"}))
.setMimeType(ContentService.MimeType.JSON);
}

This code requires your server to also have access to a spreadsheet, but it's also one you can run. Nothing about this raises security concerns to me, at least insofar as it being some sort of trojan horse. I'd be very interested if someone has a different assessment.

All that said, this is a simple convenience thing to do very basic surveys. Personally, I don't really see that it's providing enough convenience or value to be interesting, but YMMV.
.. via stock valuation, it seems
Maybe SDF?

https://en.m.wikipedia.org/wiki/SDF_Public_Access_Unix_Syste...

https://sdf.org/
No that's just private equity, and public companies. Real companies, companies that sell stuff or services to others as the way they make money, have to deliver stuff to customers. The whole company has to answer to the customer.
Well-designed off-roaders protect their occupants against the kinds of accident that might occur at relatively low speeds on rough terrain, with very rigid frames to prevent the occupants being crushed when rolling over. That is the very opposite design philosophy to most road vehicles, which are protected chiefly against high-speed collisions with other vehicles. The NCAP tests only cover the second kind of accidents.

I don't know whether the off-roading safety philosophy applies to your car though, as many SUVs and crossover cars are only designed to look the part, and are in fact more similar to ordinary road cars in safety design.
Ctrl-T (or depending on your mappings, maybe Ctrl-P). Honestly, you can't blame the IDE for you not spending time working out how to do the basic stuff.

Visual Studio has come a long way (I've been using it since the .net 1.1 days). Out of the box, it gives you most of what you got from Resharper 2 years ago.

All that said, I switched to Rider a year or so ago and haven't looked back. I used to use VS for C# and VSCode for html/typescript/css, but Rider happily handles both. It's really nice to have one IDE for everything. And unsurprisingly, it seems to perform better than Resharper + VS.
Meh. They've spent a bunch of money engineering these but could have bought a microcontroller from the numerous companies for pennies. Yes, they have more than enough money to waste which is exactly what they have done here. If they have further plans for RISC-V, ie compete with ARM, AMD, Intel, Amazon, then that is something to cheer.
Why would anyone use a NIF instead of a Port then?
Japan has a hydrogen obsession more than a gasoline one.
Bill Gross wants to save media with AI
https://archive.ph/pVPKI
"Constant utilization" means "they aren't sitting idle", not "they aren't undergoing necessary maintenance ever".
> it can block, i think it's a 'donation' feature.

Oh, interesting, I didn't know.
A pity that you have to purchase it on the Play Store

> anyway, it's not the same as netguard. Pcapdroid helps to identify bad application that you can either remove, or if not possible, use netguard later on to block.

Well, almost all closed-source apps, and especially many system applications, send data out all the time; blocklisting rather than whitelisting is not a great strategy.

NetGuard allows exporting to PCAP as well, anyhow, as a paid feature
I don’t mean this to come off as offensive but maybe you should talk with someone?

you: author is a dick

Someone else: disagree, cheating is bad

You: when cheating I learnt things

Me: cheating is still bad

You: The world has bigger problems than cheating can’t you see that?

You’re diverting and changing the topic in every post. It would be very hard to professional, or even have a social dialogue, in this way. I’m not sure what you’re after. But I would encourage you to look into how to work with people instead of going against them.
> Software development is experiencing its "assembly line moment,"

I disagree, the history of software engineering is a constant series of "assembly line moments", because we're always making new machines to make the old machines. Compilers, macros, garbage-collecting memory management, and libraries upon libraries.

There's nothing new about seeking to automate oneself out of a job.
Cute! I wonder how hard it would be, rather than having the houses "bounce" up, to make some kind of CSS animation that would look a bit like they were being sketched, some kind of gradual reveal..
If anything, the analysis of skeletal remains has been criticized for the opposite reason. Here from the book "Men of Bronze: Hoplite Warfare in Ancient Greece":

> "John Lawrence Angel, who in 1945 examined skeletal remains exhumed in Attica, put the average height of the Greek male in antiquity at no more than 162.2 cm, and of the female at 153.3 cm. It should be pointed out, however, that these data accrue from a rather scanty sample material: 61 male and 43 female skeletons from Attica, as against a total of 225 datable males and 132 females in all of Greece proper.39 Similar results accrue from Angel’s 1944 analysis of all ancient Greek skeletal remains known at the time: here, the result is given as 162.19 cm for males, with a range between extremes of 148 and 175 cm. The result for females overall remains the same. Angel, whose interest was primarily “racial” analysis, lists crania from Attica, Boiotia, Corinthia, and Macedonia; but unfortunately he does not indicate the distribution of more complete skeletons, which may have formed the basis for the calculations. Nevertheless it must be assumed that the average measurements actually represent the average, geographically as well as chronologically."

> "The comparatively scanty material notwithstanding, we would be well advised to keep in mind that, in the words of Lin Foxhall and Hamish Forbes, “this sample may be biased in favour of higher socio-economic groups since it is the graves of the comparatively wealthy that are most likely to receive attention from archaeologists.” If this is accepted, it follows that the average Greek male was in fact likely less well nourished, and the skeletons examined by Angel may well belong in the absolute upper percentile."

I'm not aware of any evidence to suggest that the skeletal remains of hoplites were substantially larger than the stated average. There are a few mass graves, e.g. at Himera, but I can find no height data. Perhaps they were taller by a couple of centimeters, but it strains credulity that it would amount to any more than that. For, as a rule, hoplites were freeholders and yeomen -- military service was a matter of social class and social standing -- they were not conscripted and sorted as though they were 18th century Austrians or Prussians: "Tall men to the halberdiers, short men to the artillery, giants to the Potsdam Giants." That wasn't the way of the Hellenes, and they wouldn't stand for it. The historical record is very clear on this point.
It's not just one incident though. This was over Matt's entire Bluesky tenure and there are many more examples elsewhere like: https://x.com/jessesingal/status/1849556209956769937/photo/1

I don't think you'll find almost any post in the 50% right of US political opinion that wouldn't be viciously attacked as a way to enforce conformity rather than debate its merits. That's an echo chamber to me and most people I reckon.
Abstraction is way better, I don't really want to know how the password is validated unless I know I'm facing issues with validation (which proper logging tells you about before you even dive into the code).

I don't understand why some people prefer being swarmed with details. It's not that they want details, but that they just hate navigating files (layer 8 + tooling problem) or that they "need" to know the details because not knowing them haunts them at night somehow.
Also, not having that as a free function makes me think it's not tested at all (although there might be some integration test that hopefully catch all errors at once, but I'm sure they don't either)
Whatever Russia is doing pales in comparison with what Israel has done for the past 70 years.
Gaussian splatting using Burn has been on my side project list for a while now. I guess they beat me to it! :)
I need to try this. Thank you.
>1

This is one of my pet peeves. I had an engineer recently wrap Dapper up in a bunch of functions. Like, the whole point of dapper to me is that it gets out of your way and lets you write very simple, declarative SQL database interactions and mapping. When you start wrapping it up in a bunch of function calls, it becomes opaque.

DRY has been taken as far too much gospel.
Now I have a very evil idea: what about registering a binfmt handler for the header bytes “#include”? Sure, it doesn’t handle all C/C++ programs (notably any program that dares to start with a comment), but it would not require modifying any source code!

(For even more insanity I guess you could also trigger on // and /*, although there’s some risk of false positives then!)
I'm the reverse, I never wanted to "input" to the wrist, but really appreciated the notifications, Bluetooth disconnect warnings, "the timeline" interface, and the necessarily limiting interface of 4 buttons (specifically: music control while in the shower... play/pause, next track, pick a station from a list, etc).

Totally understand how some loved the ability to compose/respond to messages, but that never made sense to me.

Garmin, Amazfit, and BangleJS comes close, but #buttons, #battery, and #b&w (well, always on, transflective, sunlight readable)
My point in posting this is that it is extremely disturbing, and we cannot ignore it.

Immigrants aside, this is a list of "subversive Americans" who have the wrong political views. They are all listed in the nav bar as "Targets."

As a first-gen US immigrant who flew into JFK when I was 5 years old, I find this site personally, deeply disturbing. There are many immigrants, and children of immigrants on HN. We should all find this nearly unbelievable, yet, there it is.

TFA does not so much argue against illegal immigration, as it does against immigration in general. Please everyone, read that site. Look at it deeply.

My personal story is that I came from Eastern Europe in 1980, two weeks before martial law was declared in my native country, and a US agency employee made a call that was correct, because she had the power to do so. If the American US embassy women, who made "an agency decision" did not allow my mother to join me on the plane, then my siblings would not exist. Only I had the US Visa at the time, I was supposed go alone. The embassy employee looked at us, saw that my mom knew how to use computer-aided drafting, in 19 effing 80, and was like, hell yes. Let this women in. My mom went on be the lead drafter on many major highway and bridge projects in the PNW.

If that US embassy women had been a "target" listed in TFA, she would likely have not made that same call.

Regarding the comment which I removed, I did so because my quote comment here read as "political."

Instead, I beg everyone reading this, please randomly choose three women of the ten "targets" on that site, and read their entire entry. Look at the "accusations," note that their personal finances are listed. My mind nearly melted. How did we get to this point?
The touch aspect itself is really cheap. The big benefit of screens over "simpler" instruments is that regulations actually vary quite a bit across the world. Being able to use a screen that can display anything greatly reduces the sku count, simplifying supply chains and assembly lines.

It would be hard to justify not using a screen these days, IMO.
Great, another one. Recently someone else was touting something called avalonia for .net? Then there are older ones that still exist, like Kivy and QT.

These folks should be working together on just a few open-source projects :-D. Trying to support every mainstream platform is a huge undertaking and as mentioned in this thread, few succeed, and even fewer over the long term.
Could be that the wings are a later addition, like they might have been added in the 1100s-1200s in Venice or those whereabouts.
Just post your source. Benchmarks should be reproducible.
Isn't their AI plug-in already a paid additional plug-in in the store, like the others?
"I’m not sure where people got the notion they couldn’t."

I make IR devices. My phone is the only one in the warehouse that can pick up their emissions - everyone else's cameras have IR filters with what appears to be a sharp ~750nm cutoff. I'm the only one that will pick up 800-1064nm with my cheap Samsung, and so I'm the only one doing the testing on those diode assemblies.
No, because I'm not the only person writing code. If someone else chooses to use this feature, I will eventually have to interact with it and/or maintain it.
I've asked the same question and still haven't got a concrete answer as to why anyone would use devcontainers.

As I understand it, devcontainers use some base image and then instructions in json file with steps what to add for that specific app. Why not just make a docker image with everything your app needs and use it?
Sadly (for myself) the only compact-ish plug-in hybrid that exists in my part of the world (Australia) is the Cupra Leon. Neat car, we're genuinely considering it, but it's $80,000AUD, vs. the $50,000AUD that a top-end hybrid Corolla would cost. And they're still much more expensive than my partners VW Polo... worth it for us, as we have a one car shared between the two of us, but I wish there were more compact-ish hybrids available.

Honestly same goes for EVs, though the BYD stuff is starting to fill that niche quite nicely. And compact + decent range is sort of at odds with itself.
Hi I'm Mark I work on torchao which was used for the quantization aware training and ARM kernels in this blog. If you have any questions about quantization or performance more generally feel free to let me know!
It is important to note that people in 1939 often did not have experience with this either. A lot of WWII rationing and planning focused on educating people on how to do these things in the first place.
This is why slums are in such inhospitable places.

Ever wonder why people live in industrial waste sites, on steep hillsides, swamps, etc? It’s because if the locations weren’t so undesirable, they would have been cleared and replaced already.
OK,just now I tested the new version and it is still slow.

Use "npx create-expo-app@latest --template default@beta" to install new version. Start with production mode, using android device, it takes about 300ms to render 2000 Views. The same test on React web is still much faster.
I find it hard to believe that anyone reading this was within earshot of a plane in a severe emergency and heard this particular sound and since turbine engines are already quite shrill I am basically just sorta confused who your audience is for this suggestion.
Don’t US laws make it basically impossible for a company to prevent this even if, let’s say, there wasn’t visa fraud involved?
Or for those who prefer their deviations from ideal behavior in pretty curve form, the analemma [1] captures the way in which the Sun's fails to return to the same point in the sky each day:

- The north-south component comes from the Earth's axial tilt

- The asymmetry from north to south comes from the elliptical nature of Earth's orbit, which is closer/faster in northern winter + further/slower in northern summer.

- The east-west movement comes from the equation of time, which is mostly a mix of the Earth's axial tilt and the eccentricity of its orbit.

[1] https://en.wikipedia.org/wiki/Analemma
Commercial air travel in the US is incredibly safe. The last fatal crash was in 2009.
You're right. It is very hard, if not impossible, to get absolute guarantees. Having said that, FPGAs can make supply chain attacks harder. See my other comments in this thread.
Easy test - check your black levels against someone wearing a black fabric or a reflective black surface. If you get a fair bit of grey in the image, odds are very great that you don't have an IR filter installed.
Unimog Gear Levers
Really glad to see this thorough examination of the weaknesses of profiles. Safe C++ is a really important project, and I hope the committee ends up making the right call here.
The screenshot on the homepage reminds me of my Notion setup. I will look at this. Thank you.
It's particularly useful in memory bound workflows like batch size = 1 LLM inference where you're bottlenecked by how quickly you can send weights to your GPU. This is why at least in torchao we strongly recommend people try out int4 quantization.

At larger batch sizes you become compute bound so quantization matters less and you have to rely on hardware support to accelerate smaller dtypes like fp8