incoming links from medium dot com rendering source files

Strange indeed. It looks like Medium adds "?source" after the link? That's why it triggers the file view on Blot. My workaround would be to add an extra random "?part" at the end of your link, so that when Medium adds "?source", it won't trigger the source file view on Blot. ev.lc/work?nope would become lev.lc/work?nope?source (and it works.) (at least that's what I would try) Hope this helps!

Good one, thanks! Unfortunately medium just adds "&source=user_about" after "?something=" and it triggers the same source view with blot. I didn't know of that feature, that by adding "/?source=x" to any link on a blot site we can retrieve its source file.

Ah I think when adding a first "?something" Medium transform its "?" into "&" and it still trigger the "?source" view on Blot. Try adding "#top" at the end of your URL in Medium instead maybe? (not sure if it will work)

Thanks again! An anchor (like #top) was the first thing I tried, but Medium just appended it to the end of the link. I also tried using %3F after the link, creating redirects, and even using medium%20query%20string%20parameter.md and medium?source=user_about----------------------c0540a6dd76c--------------- as permalinks—which, I know, is completely futile. ))

I wish David were here to say he would enable the option to turn off the source view in the settings. )

After Medium support replied that there is nothing they can (read: "want to") do, I used ChatGPT to write a Cloudflare Worker. For anyone in the same situation, here are my notes on the process: https://lev.lc/medium-query-parameter

Very smart solution indeed. Well documented too. 👏