skysight-inc/HackerNews huggingface dataset:
Or very young. Young people never experienced what the Internet was like before the corporations destroyed it.
Thats a good point. I checked using the "better" tool (pkg-size.dev) they show on your link and it seems they are actually comparable for the "default" export (but im not sure what that gives me with tanstack query - its effectively everything with SWR).
They really helped their cause with their execution on workflow. It was trivial for both me and for my 77 yo mother-in-law to migrate her profile to a side account.
I actually used their cases for year until the iPhone 13, when the back glass cracked on day one in their case. Now I just rely on the Apple plastic case for grip and AppleCare for protection.
Lol you don’t need blockchain, you need a host that doesn’t take down malware payloads. A floppy disk is sufficient technology if cached behind a CDN
Good point. Maybe it only exists to avoid antitrust claims (sadly I think Firefox falls in this category too).

letsencrypt is similarly vulnerable.
I hadn't advertised in several years.

I noticed the ban, and then didn't do anything about it for one year.
Extra! Extra! Read all about it! Old man shakes fist at clouds!

Seriously though, the problem is that the Cathedral is a Utopian fantasy that has never once materialized in our timeline and the people who attempt to instantiate it invariably create something much, much worse than the Bazaar.

It may look like it's made of stone, but those arches are made of painted poo.

Sure, the Bazaar is ugly and even offensive to the refined eye of the great priesthood, but these things are almost always far more useful because they come from necessity, closer to the person with real needs.
Man, I haven't seen David's site in forever... I remember the old Yomi posts about street fighter and the whole Hectóre Blivand design fiasco.
Latest glass screen I've broken I did it while sleeping... fell asleep while reading reddit, woke up with the sound of the phone hitting ground.
And that's one of the best outcomes I've had while falling asleep while using the phone. Worst ones have been sharing a link of whatever I was reading/watching to random people, liking random whatsapp statuses of people I didn't talk to since years and other similarly embarassing stuff.
Maybe I should stop using a phone before bed.
VB blows everything else today out of the water. Most kids would lose interest when you mention the word environment or toolchain. Being able to visually draw a control and then click the control to add code to its events was the best motivator because the results were instant. I can not believe how bad kids have it these days trying to learn to make an iOS app for instance, about 100 lines of code for what would be 5-10 in VB.
Took a quick look at the code, and it looks great!

- Nice to see that you've split the frontend and API/Backend.
- Backend is written in Python using fastapi.
- Frontend is Typescript.
- State is stored in MongoDB
- Good documentation to bring up local env, with docker instructions (would be nice if the frontend code was easy to put in a docker image as well).
> and focus on the power disparities of today's society

That's basically what this is about. Aboriginal people have much less power and much worse outcomes. This referendum was proposing to give them a little bit more, in a pretty gentle, non-binding way. That was rejected.

In general, I've found that many many arguments about systemic inequality basically boil down to a fairly simple question: is it better to solve a problem slow and steady, or fast and (maybe) risky. Generally the people with more to lose, the people with more power, tend to say 'slow and steady is good enough for me'. The disadvantaged however would prefer a faster solution. Those with power often argue for slow and steady by saying 'the fast way is also risky'. That's basically what happened with this referendum. People voted for doing nothing over a measure which may have not done what it set out to do, but also may have helped.
I hate the Moodle way of learning!
Franz (not Apache) Kafka's The Trial also fits the situation:

"[..] the story of a man arrested and prosecuted by a remote, inaccessible authority, with the nature of his crime revealed neither to him nor to the reader."

https://en.m.wikipedia.org/wiki/Franz_Kafka
This reminds me of Instagram which I rarely use but one time when I did it indicated that I had been blocked for some reason.

You have to take a picture of yourself yes a selfie (yuck) and send it to Instagram. The funny thing is I have no selfies on Instagram so what are they using or comparing my selfie to? I was unblocked and that was that no idea what happened.
Finally an chance for the good old "lp0 on fire" error message to be true:

https://en.wikipedia.org/wiki/Lp0_on_fire

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux...
From the author's perspective the latter is better (possible word of mouth sales and authoes generally like the idea of people reading and enjoying their writing), so not sure how that works out ethically.
Going Solo: An Author Chooses – and Celebrates – Life Without a Partner or Kids
Does the author pay every person they got all their ideas from ? We are talking about very complex one to many relationships that are practically unaccountable.
Willingly moving into apartheid is a terrible idea.
Not every account sets a public email, so this ensures that the app gets a reachable email address for every user.
Webassembly will get us there
There are devtools for SWR, but im not sure how react query ones compare. I will have to try it out i guess :)
> When you're at a point where you're relying on a display name to make security-critical decisions, you've already lost.

This obscures how dramatically worse the situation is if you can't even trust display names. Does the ubuntu.com link on wikipedia lead to an ubuntu.com, or something entirely unrelated? Does a script you're reviewing actually pull images from debian.org, or somewhere else?

At some point you have no choice but to trust what they pixels on your screen are telling you.
Haven't heard about gun4ir. I just looked at it, and while it looks very interesting, 250 euros per gun is out of my budget.
At Niantic we use Strong Network: https://strong.network/

It's a swiss based company that provide a secure environment based on container.

We like the many security features they offer, like proxying outgoing connections, organization wide controls, importing automatically source code ACLs and many possibilities for custom images. Onboarding new people is also very easy once we got our custom base images working.

We have a very good contact with Strong network and they are very responsive to our requests and comments.

Compared with other integrated Web IDEs, we feel that security was at the core of the design, which is not always the case, and this transpires in the way the product is structured.
Maybe combine plastice and silicone layers in a "case". You could give it a military grade rating. Hmmmm.
I go through several cases and screen protectors during the lifetime of a phone. If the phone was made of the same materials as the cases, I'd either be looking at a new phone each of those times, or putting a case on it anyway.
It's not Apple that worries me. They already have god powers over the phone. It's the NSA and other supply-chain attackers who now have a channel to implant devices, at high-speed, en-masse and potentially at low cost.
We used to tell on the internal shows for products to be announced, that Linux based devices like the N700 that the biggest missing feature was a radio antena, however the feedback was always that they didn't want to step into Symbian business unit.

Back on those days UNIX versus Symbian culture didn't get much along, when the board brough Elop, and what was essencially a UNIX shop working across HP-UX, Solaris, Red-Hat Linux and Symbian, most employees and developer community weren't pleased with "we go Windows now".

I was in Espoo the week following the burning platforms memo, and didn't meet anyone that agreed with it.
Then they shouldn't use a DRM publisher.
In the 90s, I filed by phone once.
https://archive.ph/jVFD3
I would love to see a writeup that made bluetooth usable in a couple days. I suspect the aspects that make Bluetooth useful also make it too complicated.
DRM on ebooks really shouldn't be a thing. It's easy enough to remove (fortunately), defeating the point of of it entirely. At the same time it's super annoying for legitimate customers, so much that I often ignore ebooks that use any kind of DRM.
Reminds me of building a bittorrent client in go: https://blog.jse.li/posts/torrent/
That worked great for iPods, but wireless charging doesn't work with all-metal cases. Brain fart: Let's put the coil behind the screen!
I know you joke, but I've been in situations where my local environment was so slow that I'd rather program in vim at 200ms latency, because that still would have been better for my sanity.
On Firefox Beta, for me it shows the punycode by default even though network.IDN_show_punycode is set to false by default
This gets you most of the advantages of a microfrontend:

1) Monorepo with multiple workspaces

2) With several separate independently deployed applications, each maintained by a separate team

3) That share a set of common packages for common stuff (auth, etc) with full typescript definitions

4) Add CI to typecheck if any shared package changes types you get errors

5) Preferably with the packages being able to be independently run for development (something like storybook, although I don't recommend it)

6) Preferably with the packages being kept small, lean, with limited number of external dependencies (ie, settle on the cross-team deps to use, so framework, routing, data-fetching, etc)

7) Some kind of pre-commit git hook or CI script to validate a set of core shared dependencies used by packages are kept in sync (ie, everyone is running the EXACT SAME React version). I use this one:
https://gist.github.com/DanielHoffmann/a456aadb2f27880d59241...

8) Shared build configuration and tools, all apps are validated, built and bundled by the same code.

9) NO PACKAGE PUBLISHING/VERSIONING, all dependencies are workspace:*

For example:

folder-structure:
/apps/{team1-app-name}/
/apps/{team2-app-name}/
/packages/auth/
/packages/some-util-lib/

/package.json
"scripts": (test, lint, format, typecheck all done at the top level package.json)
"workspaces": [
"apps/*",
"packages/*",
],

/packages/auth/package.json
"scripts": (dev to run in development mode)
"devDependencies": { "some-util-lib": "workspace:*", "react": "^18.0.0" }
"peerDependencies": { "some-util-lib": "*", "react": "*" }

/apps/{team1-app-name}/package.json
"scripts": (dev to run in development mode, build for production builds)
"dependencies": {
"auth": "workspace:*"
"some-util-lib": "workspace:*"
}

This doesn't give you 100% of the independence of microfrontends, but it does give you quite a lot of bang for your buck. Depending how much independence or reuse you want you might want more or less shared external dependencies (for example your shared packages could be framework agnostic and just use raw JS)

The build/bundling configuration can set up separate chunks for the core set of shared dependencies (react, router, etc) to improve build times, load speeds and caching*
Do what Chrome has done and continually improve plugin security. Plugins should ask for permissions. Would require an overhaul of WP though.
>Not much was being asked for here except the requirement for parliament to listen to aboriginal take on issues impacting aboriginal people.

Idk I heard there was a multi-page addition to the constitution that used Aboriginal people to 'empathy-wash' increased powers for the government to infringe on the rights of citizens. Pretty big ask. Also heard that part of the failure was Aboriginal people saying 'hey yo, this doesn't actually represent us.'

But what do I know? Maybe Aussies are just mean nazis who want to keep brown people down forever.
Seems no one's worried by the possibility of fast, low-cost, mass device compromise then.
Having used many phones, my impression is that texture matters a great deal more than material. Polished phones feel slippery and greasy. Brushed or otherwise matte phones feel really good.
Great video.

I wasn't very familiar with NuttX and LVGL, but this is very cool!
Then you can send as SVG or PDF via email.
Receipt printers are thermal and they print all day long.

Thermal printers use a thin wire that heats up in certain sections. The paper is heat sensitive. Funny though I discovered you can erase a thermal image using a highlighter pen (at old job where clerks had to highlight a section. Ooops!)

The paper is probably more of a danger since thermal paper supposedly is loaded with BPA.
A transparent TPU case costs $1 on aliexpress, with many phones it's included for free.
You got my point. That's why I was thinking about being backed by a lawyer 'cos at some point the discussion between "deceiving" and "acting" could be raised :-)
My point exactly. They had a grift going with crypto and when that went bust they suddenly pivot to AI and pretend it never happened. Which to me says is the same pattern being run over again.
Preventing Type Confusion with CastGuard
Tastes change. This isn't some engineering or logistics constraint; if plastic phones have a real advantage, adoption is simply a matter of marketing.
If you have your DRM Keys from earlier from an older Kindle or PC-Installation - the keys can still be used to strip DRM from any new downloads from Amazon.

The only exception is a few new KFX files, which are still unsupported by deDRM.
I think it's great to engage with your muse. See what happens and learn something along the way. You don't need to "release" this software on the world.

With that being said, it's your personal site and anything goes. If it's complete enough to be useful/educational/usable then by all means release it.

I hesitate to release anything too early because the internet is full of half-complete projects (devblogs for X game that never make it past episode 2, yet another todo app, a create react app with one commit, "template projects").
every time someone mentions Kafka here i get reminded of his works and every time the comment is about Apache Kafka :)
Although they don't make mobile phones (themselves) now, they're deeply involved in everything to do with mobile/wireless hardware and services that the phones connect to. As well as their own products probably just about every other phone manufacturer also pays to use their IP - I think Apple still pay Nokia $8 for every iPhone sold.

https://nokiamob.net/2023/07/01/apple-inc-renews-patent-lice...

> Nokia’s patent portfolio is built on more than €140 billion invested in R&D since 2000. It is composed of around 20,000 patent families, including over 5,500 patent families declared essential to 5G.
Nokia Siemens Networks didn't had anything from Ericson as far I can remember.

I was there from the Nokia Networks days, through the whole NSN merge process, and finally closing down most of the German locations, moving them to Indian and Eastern Europe locations.
Not only does glass feel premium, it's also relatively scratch-resistant, which means our devices look new for longer — as long as we don't drop them.

I’m firmly on the glass side, but I’m willing to listen if there was a material as scratch resistant as glass and had better shock resistance. The word “scratch” was only used once in the article so I guess there isn’t a material improvement to polymer over amorphous silica.
You're comparing the tax system, but the main topic is simply the act of filing your taxes.

Which is indeed extremely easy here in Sweden comparatively.
Also the , may be somewhat obscured by link underlining, which additions atop a letter would not be.
At dayjob we run ArgoCD, at home I prefer to run Flux which is much lighter for my home lab.

No GUI, redis, dex, and the various controllers and servers. Flux is very simple and is able to suite my needs.
I actually like my current phone (Zenfone 9) due to this reason and the fact that it's pretty small compared to all the flagships.

The back is some variant of plastic but it feels like paper. Dropped it a couple of times without a case and no scratches at all.
Personally I never use a case on my iPhone precisely because I want to enjoy the premium feel. I don't know if I'm luckier than the average person, but I've never broken or seriously damaged a phone by dropping it (and I have dropped my phone on various occasions). Especially with modern iPhones, they really seem pretty robust. The most fragile part is the screen, and that's not covered anyway.
First: Realize that React Query isn't a library for fetching data, but a library for caching the fetched data. So think about how you will be invalidating that cache. For us, the rule of thumb was that each fetch to the API should have it's own cache key in React Query.

Second: The data in cached in React Query is effectively globally available, so it comes with all the benefits and pitfalls that globals have. We use Storybook and do not use React Query in the components that have stories, so React Query is only used in the root components of the app.
I mean by remotely, what the article means by remotely:

"Consisting of a "pad-like device," store employees place unopened iPhone boxes onto it to trigger an update. The pad wirelessly turns on the iPhone, runs the software update, then turns it off again."

As in without contact with the device.
Hi, I'm a Redux maintainer. Yeah, Redux Toolkit includes our RTK Query data fetching and caching layer [0] [1], which is roughly equivalent in features and use case to React Query.

In fact, the React Query and Redux maintainers cross-recommend each other's libraries. If you're _not_ using Redux in an app, use React Query for your data fetching. If you _are_ using Redux in an app, use RTK Query for your data fetching.

(There are some differences in features and API design that might be a reason to use RTK Query even if you're not using Redux for client-side state management, such as the OpenAPI/GraphQL codegens, auto-generated React hooks, etc [1] )

[0] https://redux-toolkit.js.org/rtk-query/overview

[1] https://redux.js.org/tutorials/essentials/part-7-rtk-query-b...

[2] https://redux-toolkit.js.org/rtk-query/comparison
> The paper is probably more of a danger since thermal paper supposedly is loaded with BPA.

Apparently not the case any more.
This is generally speaking not a problem. It's technically possible, but generally in at-will states in the US, for exactly that reason, there is a strong incentive to not "randomly" lay people off b/c the company gets a reputation for being unpredictable and people don't feel secure in their jobs. They start to view their jobs are more transitory and it erodes company loyalty

Most companies will intentionally avoid doing layoffs and only do them in these large batches when there are financial necessary (like the tech sector layoffs we saw recently). Only "shitty" companies lay off people randomly to balance/adjust the books
ecosystem of packages, libraries, gems, crates or what the fuck people calling this things these days.

community of programmers within different technology stacks.

challenges to make software simpler, smaller and faster, to maintain software and prevent modern bloat from eating up gigahz of cycles on many cores.
I spent a couple of years on a project that used React Query with Axios. The massive advantage over plain fetch was the middleware API. If you want to do things like injecting an auth header or clientside token refresh it's really useful. That was more Axios than React Query though.
>It doesn't have to be that way, and plenty of places do it better - and have healitier, more equal societies as a result.

Where?
Or, just dealing with FAANG
Stremio is a pretty decent Netflix competitor. Runs on Windows, Mac, Linux, Android, Android TV. 5$ a month for a VPN and you're golden.
Make Your Sublime Text Elegant
Have a new video for you today, and it's a special one. It's about the coding editor that I've been using since the very beginning of my career. Enjoy!
HTTP3 is your friend here
One option I've seen work for a similar requirement is email verification on any corporate address. All you want to know is that they're legitimately connected to a legitimate prospective customer, just make them answer an e-mail on the company's domain.
Only 450 in Finland apparently

https://yle.fi/a/74-20055950
Apparently GDPR doesn't cover this case specifically but several enforcement authorities have issued some guidance. The only reasonable approach that I've seen is to maintain a log of deletion requests and ensure that if a backup is used to restore operational data that the deletion request is applied against the restored system.

Ironically, I've responded to deletion requests made by email in which the person did not have any records in our systems, until receiving the deletion request containing their name and email address.

https://verasafe.com/blog/do-i-need-to-erase-personal-data-f...
iPhone 7 placed the antenna on the rim, the area where there is a bit of plastic. For years iPhone wireless & wifi connections are somewhat weaker than other phones, I suspect it's because the metal back.

Wireless charging is also RF btw.
> what are they using or comparing my selfie to?

A graph database that is more you to them than you are you to them. You know meta things.
Reminds me of 20th century web! Nice. Not working on iOS :-(
At first glance I thought this was a new bleeding edge/carbon plate/superlight foam running shoe.

https://www.dogonews.com/2023/9/25/adidas-super-shoes-help-t...
The underlying TanStack Query library is UI-agnostic, and has adapters for React and other frameworks.

(There's also our RTK Query API that's part of Redux Toolkit, which is UI-agnostic but also has a React adapter.)
This is the main reason I haven't switched to IPhone. Being able to drop my phone whenever I want without worrying about damage is too big a pro.

Being able to blindly fumble for it in the dark is essential.

And the point of a phone is to be a mobile computer. A bulky phone case kind of defeats that point.
I went to a reshooting sone number of years ago and was quite afraid this would happen. Doubly so as the theater was next to MIT. All in all it wasn’t too bad. Mostly just laughing.

But it sounds like you’re hoping for it to happen . In which case my anecdote says maybe it won’t.
It could absolutely be done as you describe for most people. Most will need around 1-2 hours of tedious work per year versus 1-2 minutes as it should be.

All I'm saying is that the current system isn't that difficult for most scenarios, simply annoying busy work and form filling that should be done automatically by the government. When people talk about the US system, it sounds like most people would need a tax professional for doing taxes when that's not really the case.
Requiem for hacks upon hacks all the way down the stack to make historic brain farts work.

A sensible way forward would be to deprecate APIs for direct UTF-16 code unit access, but implement them for backward compatibility on top of an internal UTF-8 representation. On both sides.

We've lived with JS bloat for two decades, you think a few string copies/conversions are gonna kill us? Any non-toy uses of WebAssembly are gonna be new developments. Old shit that nobody is gonna run on WebAssembly other than to go "yeah, huh, it runs on WebAssembly" and then never use it again, doesn't need to run great.
Thank you for pointing this out. I only got to catch the tail end, but it was really cool to watch.
There seem to be no search filters. And I had to go to the docs to find that changing to a light theme requires ?theme=light URL parameter which doesn't appear to persist to a new session.
Also, I'm in full control of what I downloaded ("pirated" in disneyspeak). That Peppa.pig.2003.eng.subs.m0tiv8.mkv is mine, won't disappear from my catalog, and I can push it to children's iPad before flight or share with a friend.