I think the concern re:geoblock is that the REST API is just out there, unauthenticated. I need to shut those off or limit them to the internal network with Traefik, but I still need the short links to resolve. I’m not sure if that API is used for that, or what. I haven’t explored the code yet.
How so? I am hosting and maintaining it for my own work and links. I have every incentive to keep it up. And if it goes down, only my links to my own content go down. And, the reason I did this was Bluesky has a character limit.
Interesting. I deploy to my homelab with Docker so it was a fit for me. But I do want to tinker on the API to disable everything but GET. Can you share anything more about breaking it up?
I’m not a raycast user, but it has a CLI and REST API, so if Raycast has any extensibility, my guess is yes
I looked at yourls, too. I found Shlink devex to be more mature and the automated geolocation-blocking integration sold me.
It also hasn’t had a release in 2 years and is a self-described “set of PHP scripts”. Doesn’t fit my standard for what I deploy to my homelab
I need them for micro blogging where the urls count against character limits. Maybe I’ll expand them when cross-posting to Lemmy, since you asked so nicely