It's 19 years since the iPhone came out, that's almost two decades. 19 years before the iPhone was 1988. Things from 1988 definitely seemed dated in 2007. In fact I think style/aesthetics change is now getting slower and slower. Anything within the last 10 years looks like it could have been made today, since the image resolution / quality doesn't significantly change in such an obvious way. Throughout the 90s and 00s, it felt like things were constantly changing year to year. Totally different mindblowing graphics in games in each release, new OS features, digital cameras, cell phones (at all), then color screens on dumbphones, PDA, smartphone etc. etc., any Internet at all, then broadband etc. It subjectively felt much more rapid than today. The only exception is AI today, but even that is a different feel.
I think the tells of AI video are becoming more subtle, similar to language. It's no longer so much that the visuals are categorically impossible, such as mangled hands or impossible geometric arrangements of objects, but you can still see style and composition that is more frequent in AI video (but could be possible in a real video as well in principle).
Such as higher production quality, too beautiful people, a kind of stock photo sheen, etc. Of course if you use special LoRAs or prompts and input images, it's possible to leave the stock footage style, but most people don't bother with it, just like most people use stock ChatGPT in its default voice with its favorite trope-filled cadence etc.
Of course not. It's actually way simpler: smartphones became taller and heavier and you no longer can use it with one hand anymore even if you are 2m tall man. So the main mode of interaction changed to a two-hand mode and one-hand is relegated for the doom scrolling, selfies and quick replies.
Hell, my Moto has a special one-handed mode!
>> Use one-handed mode
>> Want to use one thumb to navigate your phone? Turn on One-handed mode.
>> This mode is only available if you're using Gesture navigation.
Yeah in comparison OSX Mountain Lion or Windows 8 look basically the same as the modern desktop OSes, while mobile releases from that era look totally different. I suppose it had only been 5 years since the release of the iPhone so there was still a lot of experimentation
iOS 7 really changed the game on the iOS aesthetic. We probably would've had more refined skeuomorphism had that re-design not been as aggressive as it was.
?? I installed Omarchy on an old MBP simply by inserting the usb stick into a USB port and holding a key combo during boot. Didn’t have to unlock anything.
Only 3 years of security updates for a computer we use every day is criminal. It shouldn’t be shocking that Apple kept patching but rather that Google hasn’t.
7 years for hardware and 2 latest OS versions was the standard Apple support timeline, except for many iOS and iPadOS 18 devices to force use of Liquid Glass in 26.
For anyone considering this, it's not a good plan to do it this way, if you have any family members relying on these services, you have to kill them all every time you reboot your workstation. It's really not great to mix destop and server like this. (speaking from experiance and I really need to get a separate box setup for this self hosted stuff)
You are always gonna have some downtime in a homelab setup I think. Unless you go all in with k8s I think the best you can do is "system reboots at 4AM, hopefully all the users are asleep".
(Probably a lot of the services I run don't even really support HA properly in a k8s system with replicas. E.g. taking global exclusive DB locks for the lifetime of their process)
> You are always gonna have some downtime in a homelab setup I think. Unless you go all in with k8s I think the best you can do is "system reboots at 4AM, hopefully all the users are asleep".
Huh, why? I have a homelab, I don't have any downtime except when I need to restart services after changing something, or upgrading stuff, but that happens what, once every month in total, maybe once every 6 months or so per service?
I use systemd units + NixOS for 99% of the stuff, not sure why you'd need Kubernetes at all here, only serves to complicate, not make things simple, especially in order to avoid downtime, two very orthogonal things.
> I don't have any downtime except when I need to restart services
So... you have downtime then.
(Also, you should be rebooting regularly to get kernel security fixes).
> not sure why you'd need Kubernetes at all here
To get HA, which is what we are talking about.
> only serves to complicate
Yes, high-availability systems are complex. This is why I am saying it's not really feasible for a homelabber, unless we are k8s enthusiasts I think the right approach is to tolerate downtime.
I run my stuff in a local k8s cluster and you are correct, most stuff runs as replica 1. DBs actually don't because CNPG and mariadb operator make HA setups very easy.
That being said, the downtime is still lower than on a traditional server
It's also worth noting you don't need sophisticated hardware to run anything listed in the parent comment. 8GB of RAM and a Celeron would be adequate. More RAM might be nice if you use the NAS a lot.
I would love to have something better than email, but how do we get there? How do we get everyone to adopt a new system? The biggest thing I would like to see is a system with pre authorized sending. Not sure if your system does this but the ideal situation for me is that I should only ever be able to receive mail from someone I have pre approved.
But you need a simple way to do this pre approval process, perhaps it goes to a special folder in the client the first time you receive from a new sender, and then you can approve the sender for all future mail so it goes into the main inbox?
If I’m talking to my doctor on the phone and they ask for my email I need an easy way to preapprove them, it can’t be some complex system where I must give them a 64 character alphanumeric random string.
Also I think the only way a system like this will succeed is if it is somehow backwards compatible with email, there is just too much momentum with email as is, to be able to successfully migrate everyone off it and without some sort of delay email fallback system.
Just to clarify on the 64 character key concern: FLUX supports regular human-readable addresses like alice@yourdomain.com through the account system. The fx1... keypair is the underlying cryptographic identity but you never have to expose it. You'd give your doctor your normal-looking address just like you do today.
The pre-authorized sending idea and the pending folder flow are genuinely good suggestions though, that's something I want to add. And you're right that backwards compatibility is probably the make-or-break problem. A FLUX-to-SMTP gateway is on my list so you can have a flux address that also accepts regular email as a fallback, lowering the barrier to adoption without forcing anyone to abandon their existing setup.
Step 2) Have an LLM make a shitty website about your advanced military AI tech.
Step 3) ????
Step 4) Profit!
reply