mlhpdx

Your email confirmation link’s domain is in common adblock lists.

Good, they used UDP for a one off request /response (maybe) exchange. Bad, they included precise location information.

I can see how rough location information is helpful for support and business information. Maybe country, maybe even zip code. But precise GPS was a bit overkill. Maybe it was easy, maybe it was nefarious, but not encrypting it over the wow was just plain dumb. I guess there is a razor for that.

How would this exfiltration happen though? Aren’t these cameras going to be behind a firewall? Without a request originating internally no external packet will make it past, right? Does the firmware make the first request? If so, I missed it.

I’m more mystified by the fleet wide certs. Old manufacturing tech that makes per-device firmware difficult, perhaps?

No prescription is required, but as the other comments say, you’re unlikely to learn anything significant.

Blood sugar in non-diabetics is boring, rarely moving in any significant way.

One impact could be dispelling misconceptions if you have them. Another could be discovering pre-diabetes.

Have you studied control systems? Adding a second storage mechanism with different dynamics changes control, and may complicate it. Those muscles may increase hypoglycemic events as well as soften spikes.

I try to be open minded about research choices because I have no special knowledge of what will or won’t be important. Left-field discoveries have made profound and positive impacts on many occasions.

I’m having trouble with this one, and am tempted to write it off as playing with mice in a lab. The extrapolation to human conditions is hyperbolic, maybe worse.

Given the number of people with continuous glucose monitors and activity tracking watches in the world, why not study that data directly? Causation by activity would be more apparent, more relevant and more significant (if present) wouldn’t it?

I know the guidelines make this a faux pas but I’m just here to say that was a great read. Very informative, well structured and compelling story of how we have networks and how they work.

To those saying it’s the work of an LLM: if it is I don’t care. It’s good.

Fundamentally aren’t they concluding that tasks assigned to software developers (human or otherwise) are often incomplete, self contradictory or worse? This is the world in which their tool must play. I’m unsympathetic.

People have been people since there have been people.

What companies can expand if the income of consumers is shrinking. This is the scary bit to me — AI crashes and takes the economy with it, or; AI succeeds as promised and people go unemployed and crash the economy.

The only path that isn’t disastrous is threading the needle of “just right” productivity gains. The people in charge aren’t smart enough to give me warm fuzzy feelings on that.

Gas is priced in $/gal, not dollars per mile or hour of lawn mowing or whatever. The resource and the use are completely different concepts and the resource owner/producer cares not of the buyers purpose for it.

Sailing.

This concept makes a lot of sense for first time car buyers. Having never owned a car, maybe being fresh out of college, a car can be a big leap. What will it need, what will it do? Commute? Car pool? Camping? Moving? Boating?

If the customization can be done after the fact it lowers the risk of buying.

Makes sense to me.

The article does, agreed. But I don’t think it was written by actual realtors. It’s the product of an organization that is representing them poorly, or so it appears.

Yes, many.

The realtors I’ve met understand economics and markets very well. Not as academics but as practitioners.

it's no surprise by and large they are not known for having a nuanced and academic understanding of economic theory

The folks I’ve worked with have been as dedicated to their career path as anyone, and while their expertise and skill varies that isn’t different than any job. I understand your point, but your (mis?)characterization hits me as a little biased and shallow.

It’s not “theory”; it’s literally what they do.

of course they are. what else could they possibly do? pressure you into selling for a little less? get sued for not getting the seller the best price?

also, they don’t get paid if something doesn’t sell for being overpriced.

it’s a market system.

Supply and demand, supply and demand. It’s not that complicated.

I’m not sure how or why this article got published by an organization that should, given its very nature, understand economics. The article doesn’t paint them or their members as people I’d trust in either side of a major financial transaction.

Wow, it still isn’t a standard? I’ve been building with the QUERY method for years now.

I’ve enjoyed the combination with Range headers for paging, despite this tidbit:

It is expected that these built-in features will be used instead of HTTP Range Requests

Using the QUERY request as the definition of a set, and Range to retrieve subsets seems very natural.

For the next level unlock try to make a HTTP/3 request over /dev/udp.

It’s possible that the nut of the problem here isn’t exploits, but the fixes themselves. If the model is capable of identifying and fixing things it “shouldn’t” like back doors. That would throw a wrench in things hard enough to freak out the wrong people, perhaps?

What occurred to me reading this was the wage. Initially, and famously, the hours put into building a startup result in sub-par wages. But the amount of work by an individual never increases as it is limited by human capacity. In a successful startup with continuous growth the wage is ever increasing, to the point of absurdity.

That’s weird. I grew up around farming and farmers. A group also very proud of the work they do, in a profession where the wage is also indirect — sometimes negative, sometimes a fortune, always based directly on the work they’ve done. Year after year, the work.

That’s different.

I’ve always identified two sets in the realm of entrepreneurs: those that want to “be rich”, and; those that want to “become rich”. The latter group is perhaps more admirable as they acknowledge the process and the value creation whereas the former seek only the status. But neither are often interested in the work of it.

on the other hand, when I see a long post here I assume it’s yet another ego-driven tirade and skip past it.

After having used it a while I tend to agree — the snappy send time is such a nice change.

Maybe at some point S3 will have a native implementation of something like this.

I don’t understand what Flux hoped to gain in this situation. It seems counterproductive to building a platform for engineers while attacking folks respected by engineers.

Seems like we’re barking up the same tree:

https://github.com/proxylity/raptor

If you leave your door wide open folks on the sidewalk can take pictures and write about what they see all day long.

The wisdom from my Mom was “it’s better to be paid for what you know than what you do”. I’ve found it’s a bit more subtle than that, and enjoyed and learned a lot from piece work labor. But the sweet spot seems to be getting paid for what you do that uses what you know.

AI notwithstanding, of course.

Traveling without a quick acting pen and a long acting pen would never occur to me. Even if I’m traveling for a weekend I do (and take finger prick strips and tester). It means not having to worry about pump or sensor failures, which for me generally happen during exactly the fun activities I go on vacation to enjoy.

I’d love to see CoAP/wg play a part here. It’s similar enough to HTTP to be familiar, but not supported in any browser. It supports content types and server sent events. It can be implemented in far less memory and uses far less CPU than TLS. It seems like the perfect protocol for this kind of thing.

Oof. And how much more expensive will the models be to get that 80%?