I dont like the Gemini's personality. It acts like it know it all.

Don't all LLMS act like it know it all?

Gemini, doubles down when a mistake is pointed out.

Other usually find the mistake or check new sources to fix the mistake.

Yes, that’s the reason I am holding back too.

If Apple fully supported the Asahi Linux project, I 'll switch in a heartbeat.

Looks like this is IPv6-only pricing, by the way.

$0.60 will be added for the IPv4.

his app has also Google, Apple logins and for first time I have seen, login with meta button.

https://app.wordsunite.us/

> Look at the map, all ocean travel between East Asia and India/Europe basically has to go past Singapore.

Same can be said about Sri Lanka.

Its less funneled although most straight lines will approach the southern tip of India. Singapore is one of 2 possible ways through Indonesia and its the shorter one.

This is what I experienced as well.

these are some ticks I use now.

1. Write a generic prompts about the project and software versions and keep it in the folder. (I think this getting pushed as SKIILS.md now)

2. In the prompt add instructions to add comments on changes, since our main job is to validate and fix any issues, it makes it easier.

3. Find the best model for the specific workflow. For example, these days I find that Gemini Pro is good for HTML UI stuff, while Claude Sonnet is good for python code. (This is why subagents are getting popluar)

Their CDN has a minimum $1 charge.

I was testing IPv6 origin support (they don’t support it), and they billed me $2 for a couple of test requests. I was testing at the end of the month.

With other providers, this would have cost only a few cents.

That sounds concerning but I wouldn't use other providers anyway which can decide to charge me 5-6 figures due to user error or hacked account.

Not to mention their network is over used/congested as well. there are constant IPv4 issues and IPv6 goes down for several days.

One of my client had dedicated servers in contabo and had to move to OVH because of it.

Most low-end providers will just keep using old hardware for longer.

IPv4 shortages didn’t kill it, and I don’t think this will either.

For providers like us, we have to lease IPv4. We came long after IPv4 was already depleted. IPv4 prices did go down. Despite that, the $15/year 128MB BuyVM plan is long-gone.

But for a new provider like us, we'd have to spend more than an established player like BuyVM or RackNerd who bought most of their servers pre-AI-boom.

Have you tried doing ipv6-only plans?

Vultr has one that's $2.5/month v6 only. Probably good if you just need something tiny to run some automation.

What are the issues faced by v6-only hosts and are there countries where it is a non-issue?

GitHub is the main problem currently. Some software like composer does not work due to this.

https://github.com/orgs/community/discussions/10539

For countries, if you meaning connecting to VPS, lot of countries have good IPv6 connectivity now. For me both ISPs I use have native v6. This will differ from person to person.

https://www.aelius.com/njh/google-ipv6/

It is inconcievably stupid that github, run by a massive tech company like Microsoft, has not migrated to ipv6. They're single-handedly holding back adoption.

The massivest companies are the stupidest. Do what you can to avoid all Microsoft products.

My theory: Microsoft is extremely interested in tracking you via your IPv4.

I doubt "extremely interested" is the reason.

There may indeed be some tracking that MS does via IPv4, but it's not a good way to do it.

I suspect any such tracking is essentially just some cruft that snuck in (either their own or legislative) in the early 2000s, and nobody thinks it's their problem to make go away.

That said, that IPv4 is a poor way to do tracking doesn't guarantee there's no manager demanding it: any corporation eventually gets someone with no technical knowledge demanding bad solutions.

or just offer v4 HTTPS LB bundled. Never understood why more places didn't do this.

Responsibility and controls. If the host/dc assigns a dedicated addresses the contract can be essentially "the customer assumes all liability behind traffic". With NAT/LB you need at the very least quite robust, evidence-grade monitoring mechanisms tagging all traffic and keeping historical data. In practice, some for of active abuse prevention is required, otherwise huge chunk of your address space is going to effectively linger in blacklist limbo.

That is, if being unreachable below "presentation layer" is acceptable in the first place, but I guess the question kind of presupposes this.

Yeah, most services will be behind a CDN or firewall service, anyway.

There is Asahi Linux project for Apple Silicon Macs.

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

It's not really viable