meteokr

pannenkoek2012, the legendary half an A press guy! I watch a fair bit of retro game speedrunners so he's practically required viewing in that space.

The Venn diagram of game developers, who are also interested in/good at running a business has very little overlap. You need many different kinds of people to run a business, but a game developers is only one of those. In some rare cases it works out though.

After this article I've started binge watching this whole channel. Extreme in depth analysis and code walking of NES games in assembly is so interesting. Really makes you appreciate how small and simple the platform was. "Optimizing" a game really feels like a noticeable difference. I also learned how Gameshark codes work, they're just editing addresses and OP codes directly.

Here's a link to an instance of radicle for Yuzu. It's a p2p git server implementation. I haven't looked too much into it yet, but the tech seems interesting.

Would you consider a boycott a form of protest? There are many ways to show disapproval, and marching in the streets is only one of them.

What is the difference between "religious fairness testing" and protesting? Is a protest not just an active resistance to the current legal status quo? How is a lawsuit not a protest?

My experience around any opinion where there is a default option, the vast majority will accept the default without thinking. Then when presented with an alternative by someone who has actively chosen to not chose the default, people become highly defensive as if they did do their due diligence, whether or not they actually did. Depending on where you live, the defaults change, but being that humans are tribal, differences in lifestyle naturally create friction. In parts of America, you drive an SUV, use an iPhone, and eat meat. Whether or not they actively or passively chose that lifestyle, when someone doesn't conform to what is expected there will be friction. How people react to that friction is up to them, but again, the default is to be critical of them and encourage conformity.

Yes there is precedent because in those cases you need a unique address historically. Evener commit within the project needs a unique hash for as long as the project exists. However, a unique address needs to be unique for the time it is being used.

George Washington needs to have his commit to the Linux kernel maintained, but we don't need to keep his phone number locked away forever. He can't use that phone number anymore, so someone else can have it. IPv6 is more than enough address space, so long as the dead don't need to keep their 2 billion addresses for themselves.

IPv6 has a maximum number of addresses of 2^64, or 18,446,744,073,709,551,616. Enough addresses that all 9 billion people on earth could each own 2 billion unique address. A theoretical IPv32 is wholly unnecessary for a very very long time.

So computers can share IP's then right? By your example they are sharing their public IP. From the perspective of the server you are connecting to, all the machines on your LAN have the same IP. Same way multiple physical phones can be connected to a single landline, all those phones share the same number.

I guess burden was probably the wrong term. I appreciate your work, and I just get over protective of really cool freely available services from being overwhelmed. That's an excellent suggestion.

I'm using Automatic1111's SD web UI, so their API would be the most relevant to me, but there are others out there if you prefer to use something else an an optional backend.