I can recommend the Fairphone 6+, recently launched, they increased the RAM compared to the 6 (as opposed to many other companys decreasing it), the price is a little higher, but you get a phone that is sustainably produced, can be largely fixed by yourself, and has software update commitments until 2033.
I've tried with 5 letters. After playing some games it was too easy, as it gives you more hints than Wordle on the positioning of the letters. I've also tried 6, but settled on 7 with 5 guesses as it seemed the most balanced.
> It’s definitely a better Google for most searches
I can't agree with this. You tend to get one point of view, often without any actual resources and references so you have to go look it up yourself, on [insert search engine]. Plus, what does it say when we consider an AI the one stop for our data intakes.
One of the main (vocal) issues people seem to have with IPv6 is that the addresses are hard to remember. But having eight different three digit numbers (r.r.r.r.n.n.n.n) does not seem any easier unfortunately.
I hearby propose an IPv6.1. The only change is the written form goes from:
2001:db8::ff00:42:8329
to
128.1.13.184..255.0.0.66.131.41
By doing this, I have changed IPv6 from the strange unwanted alien thing everyone hates, to the new wonder protocol that "just adds more dots" that everyone wants.
I see this point a lot but it never really made sense to me. What exactly does IPv6 bring to the table that makes it unnecessary to remember IP addresses? Especially for anything more advanced than just looking up a hostname.
IPv6 addresses can be plenty memorable. Mine starts with 2a10:3781:xxxx, and the rest of the address is whatever I want it to be. About as recognizable as my IPv4 address.
If I wanted to memorize the addresses for some reason (maybe I broke DNS or something?), I'd just start numbering devices at 1 and keep going up.
I break my DNS very often, or at least, often enough that it'd become nuisance that I can't instantly recall IP address of every machine in any of my 5 VLANs, AND type it in manually within 3 seconds.
With IPv6, I'd have to drop whatever I'm doing and fix my DNS first.
If you use SLAAC and don't use mDNS, I suppose, maybe? But if you break DNS often enough that you need to remember IP addresses, you can just do DHCPv6 if you want IPv4-like address allocation.
It'll be even easier because you can use numbers greater than 254 for your local devices, or l33t-style hex addresses, without setting up routed subnets when you exceed your /24 like on IPv4.
I would think that we are going to see RAM prices increase even more, given, among other things, pure helium disruptions and increased electricity prices.
I haven't looked closely into TurboQuant, but perhaps it will revolutionize just as much as the 1-bit llm did...
I admire this mindset, and this is what I try and do as well with my projects.
But for larger projects, on which the giants rests, (I'm thinking cURL, ffmpeg etc.) it most likely stops becoming/feeling like charity. Especially, since a lot of people do not see it as charity, and thus tries to force the maintainer(s) to do even more unpaid work.
The onus is on the maintainer(s) to work on the project as much as they can and want to, if people are creeps who try to socially manipulate maintainers to do free work, I think we need mechanisms to help mitigate that. For example, I think maintainers should be encouraged to delete GH comments they find offensive or harassing. It's their domain, they should keep it in a way they find enjoyable.
But turning open source into a job? No thank you! Adding money to something, overwhelmingly almost always in my experience, makes it that much worse and stressful. Money is not the answer!
I think one has to go clear eyed into freely licensing one’s software. It’s hard to declare you’re giving up all rights and that the IP can be used in any way, only to later say “no not like that!”
If you want a cut of your licensee’s revenue then it’s ok to say so in your licensing terms.
reply