Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
BadBadJellyBean
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
61.
▲
by
BadBadJellyBean
4mo ago
It's for those people that can't wait a second after release. As if the game is any worse if you start playing it a few days later.
62.
▲
by
BadBadJellyBean
4mo ago
I'm rooting for the EU.
63.
▲
by
BadBadJellyBean
4mo ago
VISA has debit cards as well. I have that.
64.
▲
by
BadBadJellyBean
4mo ago
I don't know why but my bank offers a VISA debit card and an EC card. I can use the VISA card on every ATM without fees and it doesn't cost me extra. The EC card has extra fees for when I want to get cash with it. I have seen othe
65.
▲
by
BadBadJellyBean
4mo ago
True but that doesn't seem to be a thing here.
66.
▲
by
BadBadJellyBean
4mo ago
Germany is different. I don't need cash often but sometimes it's needed.
67.
▲
by
BadBadJellyBean
4mo ago
I don't know how but AFAIK VISA has a contract clause that prohibits the issuing bank from charging their customers fees for using other ATMs.
68.
▲
by
BadBadJellyBean
4mo ago
I hope that they don't fall into the same trap that a lot of EU projects fall in to: only solving one problem. My VISA card is not only a convenient payment method, it also forces ATM operators to give me cash without any extra fees. I
69.
▲
by
BadBadJellyBean
4mo ago
I think the problem of crypto for mainstream usage was that it had no real purchasing power on its own. Every time you want to buy a good with crypto you have to pay the current market value of the coin in the local currency. There is usual
70.
▲
by
BadBadJellyBean
4mo ago
This is indeed a Git server. It is not a Git Forge though. Pull Requests, Issues, CI/CD, access management, etc. are about as important as a putting my code somewhere.
71.
▲
by
BadBadJellyBean
4mo ago
Ah yes. The good old cobweb theorem. https://en.wikipedia.org/wiki/Cobweb_model
72.
▲
by
BadBadJellyBean
4mo ago
At least it's repairable so unless you break the motherboard you can probably fix it.
73.
▲
by
BadBadJellyBean
4mo ago
Yeah I think so too. It's a shame. For maybe around $300 less it would be an awesome product. At least I have a good gaming PC at the moment.
74.
▲
by
BadBadJellyBean
4mo ago
Sad about the price. Maybe it comes down some day.
75.
▲
by
BadBadJellyBean
4mo ago
I think this is getting ridiculous. My proposal: Let's get rid of the position of PM altogether. Maybe then the musical chairs will stop.
76.
▲
by
BadBadJellyBean
4mo ago
The problem with IPv6 is really not the changes it made. Support was flaky for a while but that is pretty much over. The problem is that you have to deploy it. You have to handle the bigger IP space safely, you have to assign the IPs, add D
77.
▲
by
BadBadJellyBean
4mo ago
Well in the IPv4 world /32 would be a single IP or what a residential connection usually gets. With IPv6 you have 128 bits for the whole IP and usually a residential connection get get between a /64 to /48 prefix. Going above
78.
▲
by
BadBadJellyBean
4mo ago
You are aware that packets don't magically appear at the server side when sent by a client, right? All packets have to be routed to the destination by several routers. All these have to understand the full address to route the packet.
79.
▲
by
BadBadJellyBean
4mo ago
Why would I do that?
80.
▲
by
BadBadJellyBean
4mo ago
I am more interested in the technical perspective than the deployment perspective.
81.
▲
by
BadBadJellyBean
4mo ago
I have been on a dual stack IPv4 and IPv6 connection for a while now. IPv6 is the preferred protocol. I think I'd have noticed if there were widespread IPv6 issues. It used to be worse, but that was years ago.
82.
▲
by
BadBadJellyBean
4mo ago
It isn't. But It's also not an answer to GP. The solution for them is "get a better router" because the problem is not the IPv6 protocol. Opening a port is not harder than creating a NAT forwarding and if your hardware c
83.
▲
by
BadBadJellyBean
4mo ago
I'm interested, apart from the chicken egg problem, what are things that you found bad about IPv6. What do you think is overengineered? I personally found that the features I interacted with were useful (SLAAC, address size, router adv
84.
▲
by
BadBadJellyBean
4mo ago
It's not a lot but it's better to be part of the solution than the problem even if it is an insignificant contribution.
85.
▲
by
BadBadJellyBean
4mo ago
They added 12 more octets. I mean we could have written IPv6 addresses in the old format but I don't think that 42.0.20.80.64.1.192.15.0.0.0.0.0.0.0.113 is easier to remember than 2a00:1450:4001:c0f::71 (or 2a00:1450:4001:0c0f:0000:000
86.
▲
by
BadBadJellyBean
4mo ago
I assume for aggressive blocking the only prefix size will change. What is a /32 for IPv4 might become a /64 or smaller for IPv6.
87.
▲
by
BadBadJellyBean
4mo ago
I don't think this is inherently a problem. It's good for home routers to have sensible defaults. Blocking incoming IPv6 connections is such a thing. Opening a port in the firewall shows the same kind of intent as forwarding a por
88.
▲
by
BadBadJellyBean
4mo ago
There is no space to put the additional octets. Supporting this would have needed a rewrite anyways. Nothing won there. They took that as a chance to improve the protocol overall.
89.
▲
by
BadBadJellyBean
4mo ago
It's good to support it to resolve the chicken egg problem. If no service supports it, there is no sense in deploying it to the customers and the other way around. Also you made the life better of people who have DS lite. They only get
90.
▲
by
BadBadJellyBean
4mo ago
True but not deploying any IPv4 connectivity would be a worse experience than not deploying IPv6.
More ›