I think that might be a "you" thing, there certainly are comments.
And here's a link to APNews' comment guideline page, showing they have comment sections on lots of places in their website
Home Control is a solid app and was actually one of the first in this space. The main differences are: Itsyhome is open source (MIT), has a built-in webhook server with SSE event streaming so you can integrate it into scripts and dashboards, supports deeplinks for Shortcuts/Raycast/Alfred, has a Stream Deck plugin, and a CLI tool. The base app is also completely free. Basically I built it for people who want to go beyond just toggling devices from the menu bar.
I'm probably going to stick with Home Control but I will download and pay for yours as well, mainly to show some support and possibly to switch!
I do use Home Control via my Stream Deck, weirdly with Keyboard Maestro in the middle to receive the Stream Deck keypress and call the URI for Home Control, but there's a lot to like from what you've built.
Thanks! Give a try to Itsyhome Stream Deck plugin, it's in their markletplace, quite straightforward, just make sure to enable web server in Itsyhome settings.
You can create and install a profile to (re)-enable it.
Just by default unless a profile (or MDM) solution allows "User Linked" activation lock (via Find My), the default is only to allow "Org Linked" activation.
Please don’t make such personal attacks, it doesn’t add to the conversation.
If you want to have a wallet app that is not backed by a company with a banking license, then could you not side load it?
We have basic minimum standards in our food safety, why not have them in our financial services?
You, as an expert in the field still can download any application you wish, but others that may not be an expert, are given some protection from potentially AI Slop apps that they wouldn’t understand are dangerous.
>If you want to have a wallet app that is not backed by a company with a banking license, then could you not side load it?
If you haven't noticed, there's a concerted push to make side-loading harder and harder. Sure it's an option for now, but it's quite possible we're only a few years away from Google going the Apple route and the vast majority of mobile devices not supporting installing unapproved software.
Turn Power Nap on or off for a Mac desktop computer
On your Mac, choose Apple menu > System Settings, then click Energy in the sidebar. (You may need to scroll down.)
Turn on Enable Power Nap.
Note: This option is only available on Intel-based Mac computers.
You can see (and change) the settings via Terminal, 'pmset -g' will show the current options.
After you set up iCloud for Windows, you can use iCloud Passwords to access your passwords in Google Chrome or Microsoft Edge using a browser extension. You can also manage your passwords in the iCloud Passwords app.
The risk is that Apple code sign's all the executables they ship and that someone could try to use GPLv3 to force Apple to either give them their signing keys to run their own version (the anti-tivo clauses) or that it would restrict Apple from suing someone for patent infringement because they've shipped GPLv3 software.
Valid or not in anyone else's opinion, it doesn't really matter, the risk that someone will attempt to use a court to enforce one of these tends to mean companies don't want to even go near it.
Working in a Bank we won't touch anything GPL3, even to build our software/services or mobile app, because we don't want to even open that Pandora's box.
We don't have to find out if a court would try to force us to release our signing keys if we don't use or ship any code that contains language that could in some ways be phrased to do that.
For the same reason we spent £1.8m "licensing" iText PDF for Java..... And removing it with extreme prejudice immediately afterwards.
We had very keen developer upgrade all the libraries in our codebase as a "reducing technical debt" task that they decided to undertake themselves.
They couldn't get something working and posted a stack-trace to ask for help..... Some enterprising sales person in iText saw it and emailed them offering to help and asked a question about what they were running and the developer effectively told them they were running version 5 which they didn't even check (or possibly understand) is relicensed under AGPL or commercial license.
The legal threats from iText and the resulting fallout means we now do not allow developers access to the internet from their machines, even via a proxy, they have a separate RDP machine for that.
And they can only pull in libraries that are scanned via jFrog xRay and ensure the license of said library is "acceptable".
On the plus side, means we're doing something about supply-chain vulnerabilities.
There's a risk that someone uses such a library the wrong way. A big part of the goal of legal compliance and security at large enterprises is to protect staff from doing dumb things that could have bad consequences, and one of the easiest ways to do that is to ban things that are particularly prone to that. It's a blunt weapon, but a more targeted one requires much more work and care.
https://apnews.com/community-guidelines
Unsure why you jump to "is this a bot" conclusion, seems a little odd.