-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
> So what do printers have to do with any of this?
The original post was about zeroconf, and therefore the later multicast DNS-SD based discovery protocol [1]. Namely aireplay, airport, airprint, airscan based protocols that multicast their functionality and protocols via DNS to the 224.0.0.251 (or [ff02::fb]) addresses (on port 5353).
Printers these days do have primarily support for airprint + airscan so they work out of the box on MacOS with all the GUIs that the OS has to offer. Not so much for WSD or other protocols that Linux/Windows still need. CUPS or ghostscript support usually isn't complete for anything else than TIFF, because nobody seems to give a damn about implementing a PDF rasterizer on-device, let alone gutenprint or postscript/ghostscript support for their scanner devices.
Reading through the sibling comments you have to recognize that my interpretation of "what is working" is a different one than a developer's perspective. If someone without programming/linux configuration knowledge cannot print or scan via WiFi, your tool is pretty much useless and didn't replace the 100 fragmented alternatives that existed before it already.
My complaints were mostly about avahi's integrated discovery tools like avahi-browse and avahi-discover which are only tools to discover printers, but are themselves useless for printing or scanning on their own (and they're not transport-level libraries for DNS-SD IANA registered protocols either).
Literally the only scanning tool that works in the Linux world is "simple-scan" [2], which requires preinstalled "sane-airscan" and an integrated avahi-daemon in the resolv.conf/nsswitch.conf. Don't ask about parallel IPv4 + IPv6 support, because that's totally unsupported and will crash in multiple NAT scenarios the daemon in an endless loop, and is the reason why every Linux wiki will recommend to add "mdns4_minimal" to the /etc/nsswitch.conf file instead of "mdns_minimal". [3]
Coming back to my point: I mean, every developer can send a postscript file via bash to an IPP port, but I wouldn't call it a working UX or UI. When comparing the aforementioned shitshow with how everything is nicely working on MacOS, Linux is basically a bad joke when it comes to mDNS support. I mean, the technology is almost 15 years old now, and we still can't have nice printer support on Linux.
[1] http://www.dns-sd.org/
[2] https://gitlab.gnome.org/GNOME/simple-scan
[3] e.g. https://wiki.archlinux.org/title/avahi