this is a serious issue Evan and dismissing it with replies like this really doesn’t help anything. Its fine to not like the solution of using a custom uri scheme but currently there is not an easy way to interact with a remote object from your home server, and this is one solution to that issue that some people are already familiar with.
@wakest For good or ill, ActivityPub objects are supposed to use HTTPS URIs. It's in the spec: "Publicly facing content SHOULD use HTTPS URIs."
The discovery document shows a few good ways to discover if an HTML page, like a page loaded in a browser, represents an ActivityPub object.
https://swicg.github.io/activitypub-html-discovery/
One of the reasons I'm working on ActivityPub API adoption is to make this use case easier. You can see an explanation here:
https://evanp.me/2024/04/22/cross-server-interactions-in-activitypub/
If you have a fediverse account, you can quote this note from your own instance. Search https://cosocial.ca/users/evan/statuses/116020129900170727 on your instance and quote it. (Note that quoting is not supported in Mastodon.)