brk

This equates to about 20 cents per day per person, or about $73/year. It is a move in the right direction for sure, but I'm not sure I'd call this a significant statistic.

Could be nostalgia for sure, but the issues you are describing were not anticipated or immediately obvious on initial launch (at least as far as I recall).

From what I have seen of folding screens today, they come with some significant trade offs (creases, wear, etc). Over time, I expect these to be solved, but I don't think folding screens are a luxury item today as much as they are a tech novelty. But, the cell phone market has kind of stagnated in terms of hardware, and it looks like folding screens might be the thing to drive some upgrade purchases. During the peak iphone growth phase I believe Apple would have labelled these screens as not ready yet, but today I think they risk losing market share and are potentially somewhat forced to build a folding iphone.

15 years ago, I would agree that Apple might not have been willing to accept those kinds of issues. I'm not sure about the Apple of today. That is not a slight against any Apple leadership, but I do feel that, for a variety of reasons, the level of minimum QC has notched back a bit in the pursuit of marketshare.

That would be pretty hard to do with any level of accuracy or external calibration/input.

Of course there is more to life than money, but people still need some base amount of money to live safely, especially if you have a family. If you are working in SV then your "big" salary does not go very far, I know lots of developers making $350K and have very little savings cushion, and these are not people just blowing money.

Most big enterprises get really good at paying you just enough to live comfortably, but not enough to give you financial autonomy. This makes the "why do you still work there" question land as naive most of the time.

Post some links to companies hiring at similar compensation levels. Or, are you suggesting that every Meta employee is in a position to just like off of any random job they can find, or even no income at all while they go off "on their own"?

There are too many technical inaccuracies in this to take it serious (or to try and address them all here). Directionally it is fairly accurate, but the author clearly has very little knowledge of surveillance cameras, their capabilities, or even broadly how to identify ALPR vs. traffic control cameras (and similar nuances).

Not only was it built around AC, the technology at the time only allowed for roughly 1/2 the AC cycles rate. People think there was some great reasoning behind 30fps. It was just what was available, essentially.

These calculations often fail to account for present vs future value of money.

If you’re financing the system you have no big cash outlay, but returns are further out, possibly never when accounting for the useful like of the system.

With cash up front all the returns are yours, but they are much lower than what that cash would net you in an average investment.

The financial math on small solar systems can be complex. If the system is sufficient to provide power to major appliances in a power outage (assuming you have a power outage risk in your area), it can make more sense to tie money up in these systems.

The issue is that these mesh protocols quickly break down under any real loads.

Setting up a few mesh nodes, running some tests, and thinking you have a kit that is usable in an emergency is like so many other "disaster recovery" drills we've been through that assume ideal conditions. The excellent daily tape backups that you realize too late you can't utilize in a bare metal recovery situation because nobody kept an OS install media handy, or they forgot to keep the installer and license keys for the backup software in the datacenter.

The challenge with these mesh systems is that few, if any, areas have even gotten to a point that they could run a realistic simulation of relying on this system for communications.

I ran some Meshtastic nodes for a while, same overall experience.

Rarely saw nearby nodes, never communicated anything more than a basic "HELLO"/"ACK" kind of thing.

It's a neat idea for things like a distributed sensor network on your own property, or other IoT kinds of comms. It's not a practical platform for human to human comms, especially in a disaster scenario.

We clearly have differing opinions on what constitutes a decent jet. Are you buying your jets used??

The meshcore software, and the common hardware being used, are both comically weak for anything that approaches usage at scale, especially in an emergency situation.

The range is extremely limited, and the throughput gets really bad if your packets have to travel more than a few hops. These two factors alone combine to write this off as nothing more than a toy pretty much from the start.

There are already unlicensed radios with longer range that would be a better starting point if people were trying to position mesh* as a scalable and reliable transport of any kind.

>Second, the author also misses an important piece of functionality of meshcore: If I lose power, the mesh still works.

This point isn't unique to meshcore, and it is not a guarantee. Any solar powered and battery-backed device can function without utility power (in theory). Meshcore nodes are not solar powered by default, and the same solar power concept can be utilized for any other kind of radio transceiver/protocol.

That is why I just filter ND emails to spam. Those patterns just reaffirm I don’t want the kind of content they offer.

That is clearly not the mistake, there are images of it in blue, red, and yellow. I've also seen a couple of different styles of wheels. The design looks bad (for a Ferrari) in every iteration. The overwhelming feedback on public discussions is that it looks [cheap|terrible|boring|notFerrari].

Skimming through his posts he was also “back” to writing in 2023. Looks like he wrote 2 things then. Maybe he’ll do a longer run this time, maybe a good half dozen posts before another 3 year break?

I repaired some of the early 700’s at IBM when they were still mostly in the hands of upper execs and no official repair manuals had been released. I’d get random unit showing up at our Madison Heights, MI repair depot addressed to me from names I only vaguely recognized.

This isn't really just an Apple mentality though. I have all kinds of old electronics and devices from Google, Samsung, Intel, WD, etc. that all fit this exact same description.

If you've ever tried to run a hardware business (or really any business), you know that it is not financially sound to continue to support old devices that have been superceded (sometimes more than once) by newer products that consumers are currently spending money on.

We can debate if this is the way things should be, the aspect of whether you truly "own" things, software escrow, and on and on. But the phenomenon itself is in no way unique to Apple. If anything, I have found that the usable lifespan of Apple hardware is, on average, longer than the usable lifespan of other name-brand electronics in similar categories.

This is such a stupidly needed thing. Nice work!

Thanks for clearing that up. Hopefully you can come back and post when you really do die so that we have an authoritative source.

There is no real use case, IMO. I setup a few nodes a couple of months ago. It's mostly no activity, punctuated by some random "can you read me" type messages, and for some unknown reason people who think there is something impressive about them having a node on a commercial flight.

The entire thing would fall over in any kind of scenario where you needed to rely on this janky mesh network as a primary means of communications.

It can be fun/useful for very out of the way things where you have a handful of people out camping, or other off-grid situations. But frankly even in those cases there are far better/established ways to keep in sync if you need to (eg: FRS).

This stuff is mostly a solution looking for a problem.

Many upper level managers seem to be blind to the fact that the kind of person who can actually excel as a "do it all" is most likely not the kind of person that wants to work in that kind of environment. Those people will do a year or two pulling down a salary while they are also spinning up a side project, and then they'll bolt as soon as they can. It sounds like a recipe for constant employee churn, leaving behind a wake of fragile code.

Most sensors can be implemented in a way that enables self-calibration.

I'm oversimplifying it here, but the macro process is taking some known attributes and mapping them to what you are observing. For example, if you can detect people, and you know the average height of a person, you can compute where your horizon is, and where you should (or shouldn't) expect to see people in the FOV. You can do this with cameras, lidar, etc. When you have multiple sensors you can do a lot more to have them all sample an object in their own ways and converge on agreement of where they are relative to each other and the object.

14 Inch 2021 MBPro / M1 Pro chip / Sonoma 14.5

WhatCable says "No USB-C Ports Detected".

System info clearly shows my iPhone attached to USB 3.1 Bus.

That has been a global problem, lots of it in the US as well. I tend to only buy honey from known local producers, either at specialty stores or street markets.

Cuecat? Though I'm not sure if that ever really got big enough to warrant a spot, but it was a thing for a hot minute.

HomeRF - The wifi contender that was supposed to unify wireless networks across multiple device types.

Tivo - technically still around, but pretty much a zombie version of their former selves. (Maybe make an "I'm not dead yet!" section).

Gateway 2000 PCs -Their support line had a DJ, and they were everywhere until all of a sudden they were nowhere.

Optical Drives

Zip Drives - 100MB on a floppy! OMFG!!!11

Slashdot - Digg and Reddit's funky uncle.

I play on full size Ipad, FWIW. You might be able to check viewport size and scale accordingly?

I usually solve the across words with the clues and then try to do the down words without the clues.

It would be nice if the board were a little bigger to give you more room to try and organize the wordlets (not sure what to call the letter groups?) and try different arrangements.

Shit Hits The Fan.

I've played with MeshCore and Meshtastic a bit, and while they are fun, the general hype seems overblown. The "SHTF" types that get involved with this tend to just taint the whole concept for me. I was/am interested in the use cases for building sensor networks, but most of the chatter seems to be around people who just want to send Hello World type texts back and forth, without realizing how poorly a network like this would perform in a real SHTF scenario.