The official Go docs say the term rune was introduced for conciseness, but there’s more to it. We dig into the thirty year intertwined history of UTF-8 and “rune,” and hear directly from Rob Pike on the origin.
Neat idea! I’d love to use my current RSS feed reader (NetNewsWire) to follow links that come across my Mastodon feed. I can already follow individual accounts or tags with the .rss pages Mastodon generates.
I run it out of my closet. The blog is a small Go program deployed to a k8s cluster across a few ESXi VMs on an HP DL380 G7, behind a pfSense router also running as a VM and using HAProxy for TLS offloading. My connection is 1gbps symmetric.
With no cache on my local network, Chrome reports the page loads fully in ~500ms, using the "slow 3G connection" performance tab preset it takes ~4s.
If you're nowhere near Little Rock, Arkansas; that might be the issue. I don't yet use a CDN and it always loads the same resolution image ("high" quality JPEG, ~200kb apiece).
It's over-engineered, but I wanted to try running k8s in my homelab to continue learning about networking; deploying a blog seemed like a perfect test case. The cluster uses Traefik, https://github.com/travisghansen/kubernetes-pfsense-controll... to sync service definitions to HAProxy, and MetalLB. The k8s service IPs are routable from my local network, as well as the MetalLB IPs, and MetalLB handles syncing them to pfSense using BGP. pfSense sends DNS for any *.k8s.home.arpa to k8s, so I can resolve e.g. blog.default.svc.k8s.home.arpa on my local network.
One interesting hiccup: I had to introduce a NAT at pfSense because MacBooks don't listen to ICMP redirects, the packet would go laptop -> router -> k8s and then k8s -> laptop. Since the MacBook ignored the ICMP redirect, it drops the reply packet.
Thanks for the advice. I found a copy of NCSA Mosaic 1.0.3 and it works on the Macintosh SE running System 7! The next version, Mosaic 2.0.1, needs 5MB of free memory. Mosaic does a better job handling larger pages like this blog post, and even chews through the inline SVG diagrams and renders just the text.
My only complaint is that Mosaic uses the serif default font we're all used to, instead of the sans-serif default used by MacWeb, which makes it a little harder to read at such a low resolution.
Added a section on it to the bottom of the article :)
This post took a while to write, and has been continuously updated since early this month. It covers my experience connecting a Macintosh SE from 1987 to the Internet, printing from a modern iPhone to a dot matrix printer from 1985, setting up AppleShare from a Linux computer, and some networking history.
This post took a while to write, and has been continuously updated since early this month. It covers connecting a Macintosh SE from 1987 to the Internet, printing from a modern iPhone to a dot matrix printer from 1985, how to set up AppleShare from a Linux computer, and some networking history.
If the printer supports IPP advertised via Bonjour (mDNS), with PDLs including PDF, then I think all that's missing is the Apple Raster (image/urf) PDL on the mDNS entry and the URF entry. The image/urf support doesn't have to be real, since it's proprietary CUPS on Linux won't support it but I haven't run into an issues yet, I think iOS uses it mostly as a marker and otherwise respects the pdl ordering. You might look at the Discovery app to see what the mDNS records its currently advertising are. The URF entry can encode a bunch of information (info here: https://wiki.debian.org/CUPSAirPrint), but I've gotten away with URF=DM3.
I believe many Bonjour printers are of the kind that you can create by plugging a USB printer into an Airport, and they require a driver on the client. Apple makes this pretty simple by automatically searching for the driver based on the usb_MFG and usb_MDL from the printer's IEEE 1284 Device ID. None of these drivers would work on iOS, given its a different OS on a different architecture. I think AirPrint was the first driverless printing standard, followed by the PWG standard, and since they used existing technologies I assume they wanted iPhone users to only see printers which would actually work.
Bonjour also supports PostScript printers, which would use a PPD file on the client to configure the UI options and generate a PostScript preamble (this also requires generating a PostScript file from a PDF on the client -- a somewhat expensive operation). I don't know much about this apart from the couple of times its mentioned in the spec: http://devimages.apple.com/opensource/BonjourPrinting.pdf.
The practical solution is to have your friend configure a print server and advertise AirPrint mDNS on their network -- besides printing from my own iPhone, having friends be able to print to my decades-old but mighty HP LaserJet just by hopping on WiFi has been great.
