OCTAGRAM | 3 months ago | on: Users brutually reject Microsoft's "Copilot for work" in Edge and Windows 11
OCTAGRAM's comments
OCTAGRAM | 4 months ago | on: ISPs more likely to throttle netizens who connect through CG-NAT: Cloudflare
I have MultiWAN on OPNsense. My PC IP is always 192.168.0.12. My router decides which upstream it should go. If I go full IPv6, router should derive double IPv6 from both WANs and if main upstream goes down, stop advertising IPv6 from main upstream. Or stop advertising gateway. I don't know what is the right IPv6 way of doing MultiWAN.
Not only PC may change IP, but also servers. Legacy IPv4 DNS can be extended to IPv6, but that mechanical action is not flexible enough. With IPv6 we need to be able to mass replace IPv6 /64 prefix leaving all suffixes intact. We probably need /64 prefix alias system. Software is not prepared for this. In IPv4 SNAT and DNAT were being these "aliases". If NAT is not an option anymore, then DNS must step in.
For many server software it just not possible to listen on multiple IPv6 address. Last time I tried MySQL, it just could not listen on multiple addresses. I could not make it listen on IPv4 and IPv6, specifying two addresses. MySQL server wanted just one address. This address could be [::], which means all interfaces and all protocols. And Linux implements some stupid hack to accept IPv4 connections to IPv6 socket. And Windows Vista also adopted this brainrot. But this is all wrong. Servers have to learn to listen to multiple IPs. This is normal. And for good IPv6 servers should learn to not only listen on multiple IPs, most wanted multiple IPv6, but also rebind listeners on the fly. If I got disconnected from ISP, reconnected by DHCPv6, and ISP assigned another IPv6 prefix, then DynDNS should update all my zones to new /64 prefix, and all servers in my network should rebind listeners.
Or else we may abandon all that TRUE IPv6 philosophy and do SNAT in DNAT in IPv6 just like in IPv4, but with wider address space. But then again, software (another software) is not quite ready for this. Software is expecting public IPv6 address to be just reachable. And private IPv6 address to be just unreachable.
OCTAGRAM | 4 months ago | on: Git 3.0 will use main as the default branch
OCTAGRAM | 4 months ago | on: Git 3.0 will use main as the default branch
OCTAGRAM | 4 months ago | on: Git 3.0 will use main as the default branch
TTH is universal for p2p, and yet developers choose another hashes, making their tools not ready for p2p.
My lovely Mercurial is unfortunately also not ready for p2p
OCTAGRAM | 4 months ago | on: Git 3.0 will use main as the default branch
Because Mercurial is using default as default, and if we have to resort to worse SCMs, let them behave like Mercurial anyway
OCTAGRAM | 4 months ago | on: Git 3.0 will use main as the default branch
OCTAGRAM | 4 months ago | on: Run Docker containers natively in Proxmox 9.1 (OCI images)
atdr.meo.ws/archiveteam/reddit-grab
I cannot install this one to Proxmox VE, for instance
UPD. Query tag fails, but fetch is successful if I write "latest" tag
OCTAGRAM | 4 months ago | on: Why do we need dithering?
OCTAGRAM | 4 months ago | on: Amazon Demands Perplexity Stop AI Agent from Making Purchases
OCTAGRAM | 4 months ago | on: App Store web has exposed all its source code
OCTAGRAM | 4 months ago | on: Update and shut down no longer restarts PC, 25H2 patch addresses decades-old bug
OCTAGRAM | 4 months ago | on: Ask HN: Anyone else use FreePascal as their low level language?
OCTAGRAM | 4 months ago | on: Ask HN: Anyone else use FreePascal as their low level language?
OCTAGRAM | 4 months ago | on: Ask HN: Anyone else use FreePascal as their low level language?
OCTAGRAM | 4 months ago | on: Ask HN: Anyone else use FreePascal as their low level language?
OCTAGRAM | 4 months ago | on: The x86 Interrupt List, aka “Ralf Brown's Interrupt List” (2018)
20 years later it is an excercize to find a device where loved EGA programming tricks work. Only unloved informatics remained
OCTAGRAM | 5 months ago | on: IDEs we had 30 years ago and lost (2023)
OCTAGRAM | 5 months ago | on: IDEs we had 30 years ago and lost (2023)
Acronis OS Selector 5 features not much UI. There is FDISK, advanced enough for its time. It can resize FAT partitions, and there is UI for adjusting size and other stuff. There is HTML-based help system with hyperlinks. And there is some editor for AUTOEXEC.BAT and CONFIG.SYS. Acronis OS Selector 5 is about switching OSes, and specific DOS or Windows 9x boot configurations are also "OSes", so editing of boot files is helpful. But apart from that there is almost nothing to do in this OS Selector.
I wish something more daily would be coded in such UI, but nope. And Acronis dropped that style. I don't know what happened with Selector 6 and 7, but it's like 8 is coming right after 5, and 8 UI is not grid-aligned anymore.
OCTAGRAM | 5 months ago | on: When you opened a screen shot of a video in Paint, the video was playing in it
Not only we don't share PC anymore, but PCs started to share us. We possess several PCs per single person, and we needed Dropbox to manage files on multiple PCs. Dropbox can be perceived as second turning point in time, and it was more than decade ago. Now it's one goal = one device era. We buy device and we sincerely don't intend to install anything else on it. We don't risk our data using NTFS shrinking tools to make spare room for another filesystem. We don't dual boot losing access to programs in another partition. There are ways to mount NTFS in other OS and vice versa, so documents may stay accessible, but programs are not runnable. This is now ridiculous. We just buy two, three, whatever devices and have all programs runnable simultaneously.
If we need something from another OS, we'll precisely buy compatible hardware without locked bootloaders or any other possible obstacle which are numerous. To name a few.
For DOS retrogaming we need DOS ISA DMA sound, and we pick PC with ISA slot and making sure motherboard chipset has DMA on ISA, which is not true on latest chipsets. For another DOS retrogaming option we consider VDMSound, but last OS to support it was Windows XP, and we choose hardware that is Windows XP compatible. Most likely UEFI-only boot will be a problem for Windows XP. For Mavericks Forever we are not going to look for random incompatible Mac. That is going to be either real compatible Mac selected from known list, or else compatible Hackintosh. On Hackintosh there was a big problem with software upgrade, but there will be no upgrades for Mavericks Forever. Tim Cook drives company away in direction we don't appreciate, and Mavericks Forever stays forever the same version.
Nowadays people are not using OS anyway. Nowadays people are using browser. I wish I could drag and drop documents in Mavericks Forever like I did in 2007. But document is now likely to be draw io, rectangular embedding for browser that cannot support drag and drop outside its rectange. And so messenger is also rectangular embedding for browser, not respecting Mac OS X multi-window paradigm, not supporting previously established gestures. In 2007 I thought that Qt programs on Mac were ugly. Those happy days I have not seen Electron yet.
People I know often report that they got rid from "dust collector", the PC. They are now all-Android. As time goes by, it is harder and harder to find someone with PC. So whatever Microsoft preinstalls or bootlocks on PCs, it goes to people less and less.