Conversation

Notices

1. Embed this notice
   vidak (vidak@social.solarpunk.au)'s status on Thursday, 28-Nov-2024 08:28:29 JST vidak

   neocities is really one of the best things on the web, embodying so much of the spirit of what it means to use hypertext

   makes me think if the solution to leaving web is to 'do a gemini' but for HTML--deliberately designing a protocol that is incompatible with the worst parts of HTML.

   it's not altogether that difficult--just look at the simplicity of the gemini RFC

   just wondering about it--from memory, most of the coding back during the geocities/myspace era was probably just copying and pasting little snippets here and there

   i suppose the methodical way would be to step through the HTML5 standard and removing every element that contradicts our requirements

   anyway, food for thought...

   • Embed this notice
     alcinnz (alcinnz@floss.social)'s status on Thursday, 28-Nov-2024 08:30:32 JST alcinnz

     in reply to

     @vidak I suspect the list of elements to remove would be much smaller than the list of elements to find non-objectionable...

   • Embed this notice
     alcinnz (alcinnz@floss.social)'s status on Thursday, 28-Nov-2024 09:02:29 JST alcinnz

     in reply to

     @vidak Allow me to generalize.

     Most HTML elements merely encode some semantic meaning or other, since HTML5 the new ones rarely even only provide any default styling. Call these "semantic elements", which are most HTML elements!

     Other classifications could include:
     * "table elements"
     * "metadata elements"
     * "form elements"
     * "interactive elements" namely <a> & <details>
     * Elements only meaningful if you include JS, or now the `popovertarget` attribute.
     * Embed media
     * Incorporate JS or CSS

   • Embed this notice
     vidak (vidak@social.solarpunk.au)'s status on Thursday, 28-Nov-2024 09:02:30 JST vidak

     in reply to

     • alcinnz

     @alcinnz could you elaborate a little further, if you have time?

     what would you remove?

     i am discovering all the time that i am re-inventing the wheel 😅😂

   • Embed this notice
     alcinnz (alcinnz@floss.social)'s status on Thursday, 28-Nov-2024 09:11:27 JST alcinnz

     in reply to

     @vidak Personally when it comes to blocking malfeatures or simplifying the implementation, I find JS the main culprit. So I'd remove <script> & the handful of elements reliant on it.

     I think it could be good to reengineer the form elements to better promote accessibility, which could simplify implementation.

     Interactive elements could help webdevs make peace with the lack of JS.

     Semantic & metadata elements are to my mind non-issues.

     I wonder what you think?

   • Embed this notice
     alcinnz (alcinnz@floss.social)'s status on Thursday, 28-Nov-2024 09:24:33 JST alcinnz

     in reply to

     @vidak Yeah, I've spent a lot of time thinking about this...

   • Embed this notice
     vidak (vidak@social.solarpunk.au)'s status on Thursday, 28-Nov-2024 09:24:34 JST vidak

     in reply to

     • alcinnz

     @alcinnz this is really, really cool!

     i completely agree with what you're recommending!

   • Embed this notice
     alcinnz (alcinnz@floss.social)'s status on Thursday, 28-Nov-2024 10:08:04 JST alcinnz

     in reply to

     @vidak You could be interested in reading my browser-dev blog...

     I'm not sure what else right off...

     https://argonaut-constellation.org/blog

   • Embed this notice
     vidak (vidak@social.solarpunk.au)'s status on Thursday, 28-Nov-2024 10:08:05 JST vidak

     in reply to

     • alcinnz

     @alcinnz do you have anything more i could read?

     i might dabble in this area for a bit, personally i dislike HTML's syntax

   • Embed this notice
     alcinnz (alcinnz@floss.social)'s status on Thursday, 28-Nov-2024 10:09:50 JST alcinnz

     in reply to

     @vidak Though I will remark that my goal is to balance maintaining backwards compatibility against addressing my complaints. I attempt to do both!