Credit who provided the info in the first place, not the ‘ai’ that spat it out.

nibbler
Replying to @xilophor@lemmy.world
But you still will not be notified when this changes?
Admittedly the dev maintaining the aur sounds better than random person…
Replying to a post on startrek.website
By your definition not even twitter or Facebook is a walled garden.
Your definition sucks
Replying to @curbstickle@anarchist.nexus
Take a photo on mobile, ai will guesstell you the answer
Replying to @starblursd@lemmy.zip
‘Bring maintained by their dev’ sounds kind of redundant. As long as you are not close with them that sounds like a bad take
Replying to @atzanteol@sh.itjust.works
The selfhosted guys are correct with that. Of course its not a magic pill, but it can help to minimize the attack surface immensely with little effort.
Edit: while open ports can easily be enumerated, a reverse proxy often requires knowledge of the right server name. In tls1.3 those are not transferred in clear. Depending on your threat scenario you might want to consider doh/dot etc.
Reverse proxies can require client certs, which lift the security benefit to something like a vpn. Even basic auth adds a high threshold to attackers and is simple even for random users to work with. All this is functionality many services don’t offer natively - as they assume a reverse proxy anyway I guess.