Thanks! The Mobile apps would operate much like a Sublinks instance, choosing which identity services and indexes to show. I would imagine they’d just allow all of them. An alternative approach would be for the Mobile App developer to create a web service to manage those decisions and build their own API for their app to integrate with.
This microservice plan allows more people to hold different parts and reduces the risk of duplication and total loss when one instance goes down.
“Mine” was a poor choice of words. I didn’t install a UV light, but I did install an air Ionizer. My point wasn’t clear: asking your HVAC tech for advice, since they service your system, I presume, and may have additional details like install pointers or potential impacts on warranties, etc.
I’m no expert, but I am handy.
I called my HVAC technician before, and he told me to install mine in the chamber after that one. I have one before it splits.
Call your HVAC technician and ask them for over the phone advice. My tech offered to install mine for free on my next service.
I still did mine, and he checked my work and okayed it as “a gold star install.”
Here is a picture after I installed it and before wiring it.
Edit: I don’t have a finished photo, but I will post one on request. I’m too lazy to take a photo and explain why if my wife asks.
In the 70s the cars won but not the people. Modern vehicles let the people survive instead of themselves.
Yes, exactly. The Sublinks Service (which I considered calling Interact Service) allows for multiple indexes to be used. A single Index Service isn’t as powerful. Plus, the Index Service doesn’t have a UI for users. I see how combining them could simplify it, but I think having them separate gives more power. I want to build the Sublinks Service as more of a front-end framework, so that new UIs are built on it rather than everyone reinventing the wheel each time they want a new look. This will allow people to create their own view of the Fediverse.