skysight-inc/HackerNews huggingface dataset:
Thank you for this awesome feedback! Manual entry of location is high on our list of follow up features. The other ones weren't on our radar yet but I'll start brainstorming right away.
I know that iPhones with SIM+eSIM can have both active at the same time, and iPhones with just eSIM can have two eSIMs active.
The original green bubbles used a different shade but more importantly they used black text. iOS 7 switched to white text and a shade of green that means the contrast for SMS failed Apple's own guidelines. Even for people with decent eye sight it can cause additional eye strain and be perceived as ugly even if the green on its own would be fine.

To be fair the blue they choose is also not ideal, but it is a lot better than the green.

https://medium.com/@krvoller/how-iphone-violates-apples-acce...
Didn't know it was paywalled, since I use "Bypass Paywalls Clean"[0].

[0] https://gitlab.com/magnolia1234/bypass-paywalls-chrome-clean
What do you mean it wasn't the carriers?

SMS revenues to hit $67B - 2007

https://www.fiercewireless.com/wireless/metric-sms-revenues-...

They used to love using SMS to take as much money as possible from their customers. Imagine texting "Hey" to a friend and getting charged $0.20 for it.
I imagine if the engine bursts into flames they are probably going to want to land the plane anyways.
Because blue means iMessage and iMessage means E2EE.

Grey and Green means not encrypted. Simple.
Why should Wikipedia do new stuff? Or rather, why is it okay for Wikipedia to lie to people to get funding for their new pet projects?
Gotcha. I had not come across that.
I don't buy this. Customers needed no convincing from Apple. Even where iOS isn't dominant they saw their dropped and expensive SMS/RCS messages and picked up whatsapp.
Binary Keyboardinator [video]
This was the nudge I needed - super easy to donate $5 a month via the app using Apple Pay.
Not an attorney, but as someone with a startup incorporated in DE—it's just the default. Delaware has very good and well-understood corporate law and a judicial system that is able to handle complex corporate cases.

If you're fundraising as a Delaware C Corp you will face no questions about that, but if you've done something else you will need to explain why to your potential investors (and they will probably push you to reincorporate).
I broke down and bought a prepaid SIM and a small dumb phone which I use solely for 2FA. Its about the size as old-school 2FA systems like crypto cards. My original motivation in getting it was my wife was always taking my real phone to get security codes for some shared accounts (on sites that don't have an option for linked accounts). But I also like that it provides small OPSEC improvements over using my real telephone number.
> Ever-growing state: for CRDTs to work well they need to keep a record of both what exists, and what has been deleted (so that the deletes aren’t accidentally added back in later). This means that CRDT state will continually expand.

I guess a couple things:

It depends on the CRDT. Some CRDTs grow with the number of replicas and others with the number of events.

State-based CRDTs don't need to keep history and don't need causal ordering of messages, but internal bookkeeping grows with the number of replicas. And for large states (like sets and maps), it can be prohibitive to send the state all over the wire for an idempotent merge.

That's why in practice, people implement Op-based CRDTs, which makes the trade: in order to send small ops over the wire, we now need causal ordering of messages. To make sure we can sync with replicas long offline, we keep as much history so that they can catch up.

There are other variations, such as delta-state based CRDTs that send diffs, and merkle CRDTs, which use merkle data structures to calculate diffs and detect concurrency, which have different growth characteristics.

---

As for a growing state: Is this actually a concern for devs that aren't using CRDTs for collaborative text? I can see that being an issue with the amount of changes that can happen.

But outside of that, lots of data don't grow that fast. We all regularly use Git and it keeps a history of everything. Our disks are huge, and having an immutable record is great for lots of things (providing you can access it).

> Opaque state: ...you’re generally left with an opaque blob of binary encoded data.

Most CRDT libraries take a document-orientated angle. It assumes that you can contain the entire "unit of work", like a document, inside of a CRDT. However, if your data is more relational, it doesn't quite fit. And while there's immutable data in a CRDT, I do wish it was more accessible and queryable. In addition, being a binary blob, it's not exactly composable. I think CRDT libraries should be composable with each other.
> Does this sort of "status symbol" thing really matter to the average restaurant goer though?

Psychological studies reliably show that people actually care about things they think they don't care about.
I think "Reaction Control System" is from more than just a simulator.
The lede is quite cleverly buried here. Key sentence is "We will be adding support for RCS Universal Profile, the standard as currently published by the GSM Association"

So no end to end encryption and the bubbles will most still likely be green.

Even with the mutterings about improving security etc it's unlikely that the GSM Association will ever sign off on any encryption scheme that isn't weak or backdoored.
This is why I don't buy Google's bad faith shaming of Apple for not adopting RCS. The current version of it that people are using on Android isn't even a "standard" by any normal usage of the term, it's just another Google messaging service. No one can make their own app, and there's barely any carrier adoption, so Google is basically running the whole network.

Does this mean that now if you send a message to someone from an iPhone that doesn't go through iMessage, it will instead go through Google's servers? Sure the service will hopefully be better than SMS but at the cost of giving Google the keys to pretending they're a "standard."
White on green is one of the hardest color pairings to read due to how cone cells are distributed in the retina (this image isn't completely representative, in the fovea green gets even higher as a proportion):

https://en.wikipedia.org/wiki/Photoreceptor_cell#/media/File...

That's RGB lit up contrasted with just G lit up. One of the only worse pairings would be white on yellow, which would be RGB vs RG lit up, with the only distinguishing signal coming through blue, which we have the lowest resolution of.

White on blue is RGB vs B, all the visual difference in RG which we have the highest resolution of.

This is why you generally want different color schemes for light vs dark terminals, if the color saturation is high (saturated blue text on black is bad, saturated blue text on white is fine and vice versa for green and yellow).
RCS the “universal protocol” is not end to end encrypted.

Google has made some proprietary extensions to RCS to support end to end encryption but this is not the same thing.
Was that really a concern in the US? WhatsApp and iMessage require data plans, and as far as I can remember these have largely included unlimited SMS as well.

It was definitely a factor in the EU, though: SMS still aren't free on many prepaid plans there. WhatsApp was the first popular application supporting unlimited messaging on mobile phones for many.
Removing essential features like voice/video calling for non-paying users would be a terrible choice IMHO. This is a communication app, which means it is only useful if others use it too.

And how are you going to convince others to pay for Signal when there are many free alternatives, including WhatsApp, which most people already have and while not as privacy focused as Signal, does have end-to-end encryption. If Signal makes people pay for voice calls, they will simply use WhatsApp, regular phone calls, or whatever is free and popular at the moment.

The success of Signal came from being very low friction, privacy is the "nice to have" feature, at least for most users. But add friction and they will look elsewhere, Signal is not WhatsApp, it doesn't have enough of a critical mass to keep users on its network.

All that will remain will be a small core of cypherpunks and people who really have something to hide. This is bad because one strength of Signal is that it is a mainstream app, making it hard to single out "interesting" people compared to those who just use it because their geek friend told them to and they like the shade of blue.
They did link an hour long conference talk (which I haven't watched), that I assume explains in more detail the kind of logging system that they're working with: https://www.youtube.com/watch?v=Dt0vx-7e_B0

I think that basically they want a class template magic_functor that can be invoked as below

magic_functor<std::source_location::file_name()>::type

And then they could get a compile-time number corresponding to the file_name by doing:

using T = magic_functor<std::source_location::file_name()>::type;
int x = my_logging_lib_string_to_number<T>();

But unfortunately it simply doesn't work, because magic_functor is unwritable, because a `const char *` doesn't remember its size like a `const char[]` does.
...this was sarcasm, just in case it wasn't already painfully obvious to the downvoters.
Hmm, is there a way to force particular string constants to be written to particular ELF sections?

Because if so, you could just ... not dereference the pointer, and do object-file magic to make the section not actually mapped.
UK Law Enforcement Continues to Expand Use of Facial Recognition Tech
The PBS Newshour does a pretty good job of that, but it’s not sensationalistic, so most people won’t watch it. It’s dry and kind of boring.
Tim and Eric are going to go crazy with Gen AI. They won't need Adult Swim to toss them shoestring budgets.
That actually sounds about right.
That's literally the only leverage a union has. If a union can't strike, then it means nothing for them to have a voice.
I just laugh because Signal is way better than all of this and—wouldn't ya know—the default is "blue bubbles". They are the ultimate blue bubble to me because its almost all yours and gives you way more control than anything else like iMessage and its all audited and open for examination (theoretically)
So, does this still cripple ad blocking? It's pretty hard to parse from the post.

I don't really care anyway. Chrome is not the internet. Just use Firefox.
FWIW, a power chord is a _very_ different thing than a power cord.
Elon Musk's X defends US university student in trouble over posts
I would be very surprised if they integrated E2EE with Android phones. Being able to say "green bubbles aren't encrypted so everyone can read them" is a big competitive advantage and reason to justify why people need an iPhone. Plus there might be calls for doing away with stigmatized bubble colors if there aren't good reasons. Apple will want to maintain the bubble colors as long as they can, so it's win-win for them to not implement encryption.
"Realtime... Control.. System?" was my 2nd guess.
Same. I'd donated here and there in the past, but I easily get $7CAD/month of usage and would be sad if it didn't exist.
I once spent a week as an intern building a really clean and well done java swing UI options panel for a portion of our team's app. I was so proud of myself and thought it was so clear and concise and great. I told my manager it was all finished.

Well, no one else on the team was that familiar with java swing so they couldn't work with it, so one of my coworkers had to spend an hour rebuilding the panel in the UI builder that the rest of the app worked in. It produced a perfectly functional UI that had all the features requested and could be maintained by anyone on the team. Sure, the raw java file was twice as long, but who cares? It gets compiled.

I was enlightened on that day. "Elegant" is worthless in most cases. Five years later that entire app was rebuilt as a web app and nobody gave a shit whether one of it's option panels was artisanally hand crafted with care and love or spit out by an actually really good and regularized UI builder.

We are data plumbers. Nobody cares if the pipes you laid out are arranged to look like the mona lisa, and it's probably worse for the customer and maintenance that way anyway.
> I feel like that’s unit confusion. Converting from year to day should require you to specify what calendar year you’re in to resolve the ambiguity.

A year has two meanings - a calendar year, with all the leap days and seconds and timezones, or a duration of time. The latter is still useful, e.g. when someone states that Proxima Centauri is 4.2 light-years away, they don't want to deal with leap-days.

Decent time libraries have separate ways to deal with durations and dates.
I have worked as a light guy on well above 20 film sets, this is wrong.

All lamps that have a fixture which would be capable of emitting UV lights (mostly HMI lamps) must have UV filters in front of them. Typically they are part of the fresnel lense. For LED this is a non-issue.

If you got a sunburn in a studio, that means they either used shit lamps (non-industry standard), or the filters have been removed. Either way this is a work safety violation and any study worth their salt wouldn't stand for it.

The lamps are of course still something that you need to treat carefully. First because it is a ton of power and heat, but also because they are heavy. But if you use them in the way intended by the manufacturer they are not more dangerous than anything else.

A typical Arri HMI will even have a diagram with safe distances for heat radiation engraved somewhere on the body of the lamp. So you don't even need a manual to know you are doing it wrong.

I once had a HMI with a broken lense through which UV radiation would leak on a outdoor set. We noticed this because a fist-sized pile of insects started to accumulate right at the spot where the leak was. The smoke from that was quickly noticed.
I'm 39 and SMS not being unlimited was a huge thing. I never thought it would be unlimited, when that happened (Suncom? I forget who started it) it was huge. This was a LONG time ago though, long before WhatsApp. Probably 15-18 for me.

I remember a lot of conversations in high school going "My plans maxed out can you text $friend?" IIRC you had to specifically turn off receiving texts or they'd charge you for each one and we were broke HS kids.

edit: Oh that article posted above is 2007. I guess it lasted way longer than I thought.
This has been a concern for me too. But the agent is just a statsd receiver with some extra magic, so this seems like a thing that could be solved with the collector sending traffic to an agent rather than the HTTP APIs?

I looked at the OTel DD stuff and did not see any support for this, fwiw, maybe it doesn't work b/c the agent expects more context from the pod (e.g. app and label?)
Looking at the links on that page, the only links for 9.0 or 10.0 look to be for the network edition (non oss)

I'm not familiar with the situation, but reading through https://blog.zimbra.com/2020/05/is-zimbra-open-source-yes-fa... suggests that they do still provide source for at least some portions of 9.x, but they no longer provide binaries or packages.

It looks like some components may be missing ("Modern UI"), but I don't know if it's usable without them.
> more resistant to heat considering the distance they have from the engines, in case something went wrong

For the engine to melt a window, something has gone wrong enough that this tolerance isn't material. (You'd need a lot of heat. Plus enough turbulence to blow it laterally inward, but not so much that it's allowed to cool. That combination suggests a loss of power and a low-speed, i.e. low-altitude, stall.)
I forgot to say NO macros, those evil things need to go
I think he edited that line out when it got big on HN lol. And clarified that she was named for Westworld, not... "She was Dolores on the dotted line"
I think we can. Following all the implications down the rabbit hole, you end up with a system architecture where there's no front-end, and there's no back-end.

Since CRDTs are still kinda new for most people, the discussion hasn't really gotten there yet.
Apple announced today they are going to support RCS https://9to5mac.com/2023/11/16/apple-rcs-coming-to-iphone/

RCS is better than SMS no doubt but lets not pretend it is on the same level as iMessage. Lack of end to end encryption alone makes RCS a dated standard
Without federation, Signal is still working with the advantage of network effects. So an open source server is not enough of a way out.

Element can do it for their Matrix servers. Process.one can do it for ejabberd. Prosody as well. Why can't Signal?
I can picture teens or younger acting snobby about phone choice. Not really clear why, if it’s a financial thing, as it’s been years since iPhones were priced at a premium relative to competitors. But well, they’re kids. However, I’ve experienced critical attitudes from adults well into their 40s when I had an Android phone. Personally I prefer iOS, but to judge someone based on their phone choice seems fairly ridiculous for an adult.
The U.S. has special rules for satellites over one country: Israel
Where is the option for group chats please?
Functions are hard barriers for optimization and I don't see that changing any time soon.

Which goes even so far that EXPLAIN doesn't work on them and you just get a black box of "Function call to ..." in the execution plan.

Using auto_explain is the only workaround known to me for that.
The paywall workaround doesn't work, I get stuck in an infinite captcha loop. I'll now be told to inspect my DNS settings, which is a step too far in terms of bypass. IMO the article ought to be flagged.
> Bans on state subsidies are a core principle that enables the EU single market. Otherwise the market could easily be distorted by state aid.

It seems impossible to avoid this. If one state spends money on something that benefits businesses and another spends it on something else, those businesses will prefer the first one. But this isn't actually that much of a problem because each state has finite resources and its people get to decide how to use them. If one wants to have a UBI (which might increase entrepreneurship and the number of small businesses engaged in taxable activity) and another wants to lower unemployment by attracting large employers with subsidies and a third just wants to have lower taxes, what's the problem? That one might actually work better than another?
Failures, particularly fires, around the engines and wings are either dealt with in minutes[1] or the state of the window becomes no longer relevant.

[1] The complete list of options are typically starvation, suppression, evacuation. Apply in that order and do so quickly.
> This is why I don't buy Google's bad faith shaming of Apple for not adopting RCS.

Google is literally operating an RCS SaaS company for marketers and telcos, so I'd take any of their statements in support for RCS with a grain of salt: https://jibe.google.com/
KEXP Has Winning Bid for Dark San Francisco FM Station
That's a prose description, not code.
I use Google Fi for my iPhone. What am I missing out on? (asides from using more than 1 carrier's network simultanously)
QNX had this right decades ago. The microkernel has upper bounds on everything it does. There are only a few tens of thousands of lines of microkernel code.
All the microkernel does is allocate memory, dispatch the CPU, and pass messages between processes. Everything else, including drivers and loggers, is in user space and can be preempted by higher priority threads.

The QNX kernel doesn't do anything with strings. No parsing, no formatting, no messages.

Linux suffers from being too bloated for real time. Millions of lines of kernel, all of which have to be made preemptable. It's the wrong architecture for real time. So it took two decades to try to fix this.
> >LLMs do not use logic at all. The logic of invalidation is missing.

> This is a fascinating idea that i see that just doesn't square with reality. In fact, this is all they do. What do you imagine training to be ?

I could have been more clear, but I didn't want to write a novel. The ambiguity here is what they invalidate: memory reconstructions, not logical assertions.

An LLM can't tell the difference between fact and fiction, because it can't apply logic.

Better memory will never suddenly spawn itself the feature to think objectively about that memory. LLMs improve, yes, but they didn't start as a poor-quality equivalent to human thought. They started out as a poor quality equivalent to human memory.

> There is a projection of the world in text. Text is the world and the language model is very much interacting with it.

The language model becomes that world. It does not inhabit it. It does not explore. It does not think, it only knows.
I wonder if you could create an AI assist to help you hold on to an existing relationship, though?
Anything can be addictive. If anything, broader use of the term would serve to disarm it, not strengthen it, and that's a good thing given how poorly the law handles addiction and addictive substances.

I understand dependence as requiring something to feel "normal" for whatever definition of "normal" an individual has. By this definition, I am addicted to and dependent on food, sleep, caffeine, medication, socializing, novelty, and reading. I find that I have a hard time doing less of these things, and sometimes these things get in the way of my ability to do other, healthier, more productive things. For some of these things, doing less of them would directly harm my physical health.

With this in mind, I have met many for whom sugar is an addictive substance far more deleterious to their health than even cocaine is, for example, to others I know. They've struggled with problems like diabetes and obesity, and they've even lost jobs because of their relationship with sugar. Moreover, some of them respond aggressively and defensively, much like any other addict, when friends and family try to raise the issue with them, and some of them have tried and failed to give up sugar countless times, again like anyone else struggling with addiction.

Earlier this year, I lost my mom to diabetic coma, in part, because she couldn't stop herself from eating candy and cookies all the time. She tried to stop, but she couldn't kick the habit of having a "dessert" before bed followed by the insulin necessary to control her blood sugar. It was her way of calming herself down enough to fall asleep at night. Eventually, she accidentally took too much, and no one found her until morning, long after hypoglycemia had destroyed most of her brain. She died of overdose like any other addict, although the thing she overdosed on, exogenous insulin, was a sort of secondary dependency caused by her primary dependency on sugar. The medical staff at the hospital insisted on steering me away from this terminology when discussing what happened, but their reasons were politics and marketing, not anything truly descriptive or scientific. Their fear was similar to yours in that they worried that patients might refuse insulin treatment if it was at all associated with the labels of "addiction" and "dependence." I can't help but think that she might still be around if her physician had treated her relationship with sugar more seriously or if they had more thoroughly warned her about the dangers of exogenous insulin in the context of addiction and dependence. After all, the use of exogenous insulin leads to the downregulation of insulin receptors causing "true" physiological dependence by way of a mechanism very similar to that of benzodiazepines, opioids, and alcohol. The same could be said for sugar in its role as a causal factor of diabetes itself.