https://www.wumpus-cave.net/post/2024/05/2024-05-12-solarpunk-internet-principles/index.html
Musing about programming
Not 100% sure if this is a Summit issue or something in Lemmy more generally. Here's the post in question:
https://midwest.social/post/10123989
The link to the blog works on my instance for the desktop. Several other users were reporting the link being broken, and it does break for me on Summit, as well.
When I hit the link on Summit, the requests on the server are GET /api/v3/post?id=2024
and GET /api/v3/comment/list?max_depth=6&post_id=2024&sort=Top&type_=All
. It looks like it parsed out the "2024" from the original link and tried to use that in a Lemmy API call.
Here's the post in question: https://midwest.social/post/10123989
Which linked to my blog here: https://wumpus-cave.net/post/2024/03/2024-03-20-moores-law-is-dead/index.html
On my instance (midwest.social), this works fine. However, some other users were reporting a broken link, and I also see a broken link when using my mobile app (Summit). When it breaks, I see these calls in the server logs:
GET /api/v3/post?id=2024
GET /api/v3/comment/list?max_depth=6&post_id=2024&sort=Top&type_=All
Which appear to be Lemmy API calls with some of the actual link data built in.
https://wumpus-cave.net/post/2024/03/2024-03-20-moores-law-is-dead/index.html
Musing about programming
@frezik
@midwest.social