@tantek.com good post, fwiw, there's some complicated history surrounding that change, and there's a long term goal to fix that, but it's a rather hard and difficult path due to how everything's been built. There was some discussion in the mastodon discord about this the other day.
Conversation
Notices
-
Embed this notice
Emelia 👸🏻 (thisismissem@hachyderm.io)'s status on Friday, 16-Feb-2024 11:02:52 JST Emelia 👸🏻
-
Embed this notice
Emelia 👸🏻 (thisismissem@hachyderm.io)'s status on Friday, 16-Feb-2024 11:02:50 JST Emelia 👸🏻
@KevinMarks @tantek.com I'm honestly not sure. But maintaining both server-side rendered pages + a large client-side javascript app is a lot, and the client-side app is beginning to show it's age with hard to update dependencies.
(my contributions mainly focus on the moderation tools, streaming server, and OAuth 2.0 stuff)
-
Embed this notice
Kevin Marks (kevinmarks@xoxo.zone)'s status on Friday, 16-Feb-2024 11:02:51 JST Kevin Marks
@thisismissem @tantek.com would an initial start be to restore the microformats on the /embed page, before adding that back to the full html?
The pre 4.0 microformats markup was very good at expressing replies and any referred-to post as well.
As Tantek noted, putting the post text in proprietary markup for silos but not in the html is an odd choice.Tim Chambers repeated this.
-
Embed this notice