New OEIS entry: numbers used in names of startups followed by “labs”

Aren't OEIS entries immutable?

> when a carrier does an ENUM lookup for one of these numbers, they're essentially asking "where do I route this call?", and I could answer with whatever I wanted. I could point it at my own SIP server, accept the incoming call, and then place an outgoing call to the real destination with a spoofed number

How would the “outgoing call to the real destination” avoid this same lookup? Directives to route around the ENUM system?

At some point (soon), the massive inefficiency of this system will stop being subsidized. Also, it’s nondeterministic and unreliable.

> The “Follow” button is visible when I take the screenshot mid-switch.

Does this indicate that the privacy feature has a gap, where you could reveal the length of your password if you take a screenshot mid app switch?

No because per default the input is not cleared when screenshotting. If you‘d implement this yourself for security reasons you'd most likely blur / overlay the whole screen when the app enters background state.

Probably, but to the extent that was at all a problem to begin with, multiply it by another 0.0001 or whatever for the threat of the screenshot being taken mid switch away!

I would love an agentic tool that simply finds code locations and opens them in my editor, so that I can write the implementation. I find this to be the most tedious and disorienting part, especially in languages without strong typing, that de-emphasize navigable references between classes. For example, wouldn’t necessarily need this tool for Java. Would like it for Ruby.

Is it like self driving cars, where 100% non-human code would be arguably safer?

But then it always comes down to having some human who is accountable for verifying the behavior. I think ultimately we just need a better set of languages and frameworks to minimally encode the types of applications we want to build today, so that human comprehension and verification of the source code becomes easier.

I've noticed that when only AI writes the code, there are cases where it ends up being unusable by humans. For small code snippets or function-level units, AI is often much better than me. But when I look at the whole picture, AI tends to perform poorly.

How would 100% non-human code possibly be safer?

well if driving is supposedly safer when automated, why not code

The qualities of computation that make autopilots safer than human drivers aren’t the same qualities that produce better designed software products.

to err is human

It’s supposedly safer than the average driver, not safer than professional drivers.

the average american spends 60 minutes a day driving, that's thousands of hours by the time you reach 25... at what point is that not a professional level of experience?

Is it actually safer? If you can't understand the code you can't verify it's safety, and AI code often has bugs in it. You can't trust implicitly.

You don't need to understand code to verify its safety if you have a good QA framework.

Same applies to driving cars

Category error. Self-driving cars are still meticulously coded by humans.

They use trained models in the system though, so I don't know if you can really claim that.

It’s probably not too important to choose a service that you think you can trust fully, because that trust might be broken at some point. But having an identifier that can be swapped to different backends, so people can find you again when the host inevitability changes, is a stronger strategy. I think the importance of owning domain names will increase, and using those as the canonical identifier of a project will give it more permanence. The procedures for seizure and censorship with domain names are better established and understood.

Last week the USA censored the domain name of a Dutch porn site.

But consider how, in just a short few years, tools will have changed so much that even achieving this specific look will not even be possible (everything is in the cloud and normal users can’t even run them locally)

We’ll inevitably end up feeling nostalgic for these mid-2020s AI slop menus, much like how graphic design of the 90s and 2000s is revered (see other comments on this post) even while during its making was regarded as garish

No we won't.

Never say never. People are paying through the nose for a pair of JNCOs these days.

That's a good operating assumption, and I usually think this way too.

It turns out Slack actually requires legal process or consent of parties to provide private messages to admins: https://slack.com/help/articles/204897248-Guide-to-Slack-imp...

But of course yes, another party could simply take a screenshot

They certainly can on Business and Enterprise plans. There’s some lip service to following employee policy and applicable laws, but if the policy allows (most do), and you’re in the US, the admins can do it.

Ah yes you are right. The policy I am referencing is for the Free or Pro tiers, Business is different

I find myself holding onto and preserving general ephemera and just happened to scan a moist towelette package over the weekend. My collection mostly consists of business cards and dry cleaning type carbon copy receipts. I need to better catalogue these and share online. A few business cards: https://ivan.sh/biz-cards/