Hey Matticustard, Gerald @sigung,
true.
What is said in this article is true if you connect to an usual network with router etc.: It is a bad sign to get an 169.254.0.0/16 address if you have a DHCP server in your network.
But using a link-local address (169.254.0.0/16), which means using Zero-configuration networking (provided by the avahi package installed in the Onefinity controller) to get a link-local address automatically assigned works absolutely nicely if you just connect a laptop (that may have no DHCP server installed) to the Onefinity Controller, and also with zero-config name resolution so you can call it with http://onefinity.local. Most of the time, I used the ethernet connection this way. And as was tried to make it work the other day on older windows versions, the latter needed an additional software package that you pointed us to, for having Service Discovery 
The limitation is that link-local addresses always stay local, they are not forwarded to another network (as per the standard). So you can’t use a link-local address to use an internet router to browse the web.