no you didn’t Mr. Simpson, no one can
no you didn’t Mr. Simpson, no one can
well there was probably awareness of ideas of sacrifice, punishment, right/wrong. Old ideas…
AM radio paywall? Where?
I suppose there’s positive, then there’s “totally changed how I work”. It’s a big call. Maybe a real-world example would make it sound more believable: “before ChatGPT, I would have to sift through stacks of outdated VB6 documentation on $task. This took up most of the day. Yesterday I used a LLM to get a basic implementation of $task then I tidied it up and installed it within an hour.”
For me it’s the bloody “video essay” format. Hyper narrated, spoken straight to the camera. Waste of traffic, waste of storage, waste of attention. People think the argument carries more weight, or is just more persuasive, when someone is speaking at you with some vaguely related visual in the background. But really a written piece could be pulled apart so much more quickly.
Unfortunately OpenAI’s Whisper doesn’t do written transcriptions fast enough on my workstation yet for me to use it full time.
BYD employ about 570,000 people and by some measures are the largest carmaker in the world. I’d never heard of them either until a couple years ago. They’ve definitely got the cash to put into PR like this. Past couple years Australia started importing their electric cars. https://en.wikipedia.org/wiki/BYD_Company
I use it for my very basic static site generator: https://www.olowe.co/2021/01/site-build.html
Devil’s advocate: what about the posts and comments I’ve made via Lemmy? They could be presented as files (like email). I could read, write and remove them. I could edit my comments with Microsoft Word or ed
. I could run some machine learning processing on all my comments in a Docker container using just a bind mount like you mentioned. I could back them up to Backblaze B2 or a USB drive with the same tools.
But I can’t. They’re in a PostgreSQL database (which I can’t query), accessible via a HTTP API. I’ve actually written a Lemmy API client, then used that to make a read-only file system interface to Lemmy (https://pkg.go.dev/olowe.co/lemmy). Using that file system I’ve written an app to access Lemmy from a weird text editing environment I use (developed at least 30 years before Lemmy was even written!): https://lemmy.sdf.org/post/1035382
More ideas if you’re interested at https://upspin.io
They even have a term for this — local-first software — and point to apps like Obsidian as proof that it can work.
This touches on something that I’ve been struggling to put into words. I feel like some of the ideas that led to the separation of files and applications to manipulate them have been forgotten.
There’s also a common misunderstanding that files only exist in blocks on physical devices. But files are more of an interface to data than an actual “thing”. I want to present my files - wherever they may be - to all sorts of different applications which let me interact with them in different ways.
Only some self-hosted software grants us this portability.
Good to see development effort going towards actual Firefox and not those random Mozilla products that I can’t keep track of
I wonder if their compositors would be laggy and bloated with features, too?
This was the provider I went with after self-hosting my mail for 7+ years on an OpenBSD VPS. I feel like Migadu is an honest and good-value service.
Each time your browser makes a request (such as updating the graphs), it’s submitting a new DNS query each time.
That would be surprising; most HTTP clients reuse network connections and connections are deliberately kept open to reduce the overhead of reopening a connection (including latency in doing a DNS lookup).
Then again, I’ve seen worse ;)
We can never know exactly. For me I always think about the (incidental) complexity of these huge apps like Instagram.
Somebody mentioned the phone overheating when watching Reels - those short videos. Here’s a made-up example (but I’ve written some software for video streaming services)…
Those videos are pretty short, and some people skip the clip even after less than 1 second. Instagram want that next video to be playing instantly (gotta get that dopamine hit ASAP!). A strategy you could take is have the app load the next, say, 5 possible videos in the background before you’ve even seen them. When the user swipes, that video is already playing. To make this even faster we could execute some recommendation decisions on-device rather than on some servers (over a relatively much slower 4G connection).
With all this complexity comes greater chance of some unexpected behaviour. Instead of loading 5 videos, maybe we accidentally load 100 and never clean up the old ones. Maybe after an OS update we need to change the way we mark a task as low priority.
Cool insight - thanks! All points even more to bad planning by the Instagram team as you said originally.
I guess I wouldn’t be particularly surprised. Apple put shitloads of R&D into power-efficiency. Can’t imagine the culture at Instagram/Meta is like that.
Slightly off-topic: I’m not too familiar with FreeBSD (I use OpenBSD), but others may be interested to know you may be able to configure wireguard interfaces without installing any packages.
It probably just involves running some ifconfig
commands at boot via some entries in /etc/rc.conf
. See https://docs.freebsd.org/en/books/handbook/network/
Yeah I’ve always found that AllowedIPs
name a little bit misleading. It is mentioned in the manpage:
A comma-separated list of IP (v4 or v6) addresses with CIDR masks from which incoming traffic for this peer is allowed and to which outgoing traffic for this peer is directed.
But I think it’s a little funny how setting AllowedIPs
also configures how packets are routed. I dunno.
of course!