home.social

#hypermedia — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #hypermedia, aggregated by home.social.

fetched live
  1. Building Progressively Enhanced Forms with htmx

    In which I go into things I've learned over the course of the last year building moderately complex web UIs for ties, using plain HTML and htmx.

    rafa.ee/articles/progressive-e

    #smallweb #webdev #html #hypermedia #htmx

  2. Building Progressively Enhanced Forms with htmx

    In which I go into things I've learned over the course of the last year building moderately complex web UIs for ties, using plain HTML and htmx.

    rafa.ee/articles/progressive-e

    #smallweb #webdev #html #hypermedia #htmx

  3. Building Progressively Enhanced Forms with htmx

    In which I go into things I've learned over the course of the last year building moderately complex web UIs for ties, using plain HTML and htmx.

    rafa.ee/articles/progressive-e

    #smallweb #webdev #html #hypermedia #htmx

  4. Building Progressively Enhanced Forms with htmx

    In which I go into things I've learned over the course of the last year building moderately complex web UIs for ties, using plain HTML and htmx.

    rafa.ee/articles/progressive-e

    #smallweb #webdev #html #hypermedia #htmx

  5. Building Progressively Enhanced Forms with htmx

    In which I go into things I've learned over the course of the last year building moderately complex web UIs for ties, using plain HTML and htmx.

    rafa.ee/articles/progressive-e

    #smallweb #webdev #html #hypermedia #htmx

  6. Aus meinem Laboratorium für interaktive Geschichten und Spiele: Decker-Updates

    Der regelmäßig auf diesen Seiten erwähnte »Freund aus Bremen« hat wieder zugeschlagen. Vor ein paar Tagen machte er mich darauf aufmerksam, daß es von Decker, ein neues Update gäbe. kantel.github.io/posts/2026072 #Decker #InteractiveFiction #Retrocomputing #Hypermedia #GameDev

  7. Aus meinem Laboratorium für interaktive Geschichten und Spiele: Decker-Updates

    Der regelmäßig auf diesen Seiten erwähnte »Freund aus Bremen« hat wieder zugeschlagen. Vor ein paar Tagen machte er mich darauf aufmerksam, daß es von Decker, ein neues Update gäbe. kantel.github.io/posts/2026072 #Decker #InteractiveFiction #Retrocomputing #Hypermedia #GameDev

  8. Aus meinem Laboratorium für interaktive Geschichten und Spiele: Decker-Updates

    Der regelmäßig auf diesen Seiten erwähnte »Freund aus Bremen« hat wieder zugeschlagen. Vor ein paar Tagen machte er mich darauf aufmerksam, daß es von Decker, ein neues Update gäbe. kantel.github.io/posts/2026072 #Decker #InteractiveFiction #Retrocomputing #Hypermedia #GameDev

  9. Aus meinem Laboratorium für interaktive Geschichten und Spiele: Decker-Updates

    Der regelmäßig auf diesen Seiten erwähnte »Freund aus Bremen« hat wieder zugeschlagen. Vor ein paar Tagen machte er mich darauf aufmerksam, daß es von Decker, ein neues Update gäbe. kantel.github.io/posts/2026072 #Decker #InteractiveFiction #Retrocomputing #Hypermedia #GameDev

  10. Your REST API returns a status field. The client still has to guess what comes next.

    In this tutorial I build a small Quarkus service where HAL links change with workflow state. A CREATED shipment shows pay and cancel. After payment, those disappear and pack shows up.

    The server tells the truth about valid actions. The client follows links instead of maintaining its own state machine.

    the-main-thread.com/p/quarkus-

    #Quarkus #Java #REST #HAL #Hypermedia

  11. Your REST API returns a status field. The client still has to guess what comes next.

    In this tutorial I build a small Quarkus service where HAL links change with workflow state. A CREATED shipment shows pay and cancel. After payment, those disappear and pack shows up.

    The server tells the truth about valid actions. The client follows links instead of maintaining its own state machine.

    the-main-thread.com/p/quarkus-

    #Quarkus #Java #REST #HAL #Hypermedia

  12. Your REST API returns a status field. The client still has to guess what comes next.

    In this tutorial I build a small Quarkus service where HAL links change with workflow state. A CREATED shipment shows pay and cancel. After payment, those disappear and pack shows up.

    The server tells the truth about valid actions. The client follows links instead of maintaining its own state machine.

    the-main-thread.com/p/quarkus-

    #Quarkus #Java #REST #HAL #Hypermedia

  13. Your REST API returns a status field. The client still has to guess what comes next.

    In this tutorial I build a small Quarkus service where HAL links change with workflow state. A CREATED shipment shows pay and cancel. After payment, those disappear and pack shows up.

    The server tells the truth about valid actions. The client follows links instead of maintaining its own state machine.

    the-main-thread.com/p/quarkus-

    #Quarkus #Java #REST #HAL #Hypermedia

  14. Your REST API returns a status field. The client still has to guess what comes next.

    In this tutorial I build a small Quarkus service where HAL links change with workflow state. A CREATED shipment shows pay and cancel. After payment, those disappear and pack shows up.

    The server tells the truth about valid actions. The client follows links instead of maintaining its own state machine.

    the-main-thread.com/p/quarkus-

    #Quarkus #Java #REST #HAL #Hypermedia

  15. This RSS-translator will be in the next release of janusweb.
    Link/surf to any RSS-URL in your 3D space, and it'll give you a portal to this room ♥️

    #janusweb #webxr #hypermedia #rss

    coderofsalvation.github.io/jan

    xrhf.isvery.ninja

  16. This RSS-translator will be in the next release of janusweb.
    Link/surf to any RSS-URL in your 3D space, and it'll give you a portal to this room ♥️

    #janusweb #webxr #hypermedia #rss

    coderofsalvation.github.io/jan

    xrhf.isvery.ninja

  17. This RSS-translator will be in the next release of janusweb.
    Link/surf to any RSS-URL in your 3D space, and it'll give you a portal to this room ♥️

    #janusweb #webxr #hypermedia #rss

    coderofsalvation.github.io/jan

    xrhf.isvery.ninja

  18. This RSS-translator will be in the next release of janusweb.
    Link/surf to any RSS-URL in your 3D space, and it'll give you a portal to this room ♥️

    #janusweb #webxr #hypermedia #rss

    coderofsalvation.github.io/jan

    xrhf.isvery.ninja

  19. This RSS-translator will be in the next release of janusweb.
    Link/surf to any RSS-URL in your 3D space, and it'll give you a portal to this room ♥️

    #janusweb #webxr #hypermedia #rss

    coderofsalvation.github.io/jan

    xrhf.isvery.ninja

  20. 𝗗𝗮𝘁𝗮𝘀𝘁𝗮𝗿:

    #Hypermedia #Framework #Datastar

    thewhale.cc/posts/datastar

    Datastar is a lightweight framework for building everything from simple sites to real-time collaborative web apps.

  21. 𝗗𝗮𝘁𝗮𝘀𝘁𝗮𝗿:

    #Hypermedia #Framework #Datastar

    thewhale.cc/posts/datastar

    Datastar is a lightweight framework for building everything from simple sites to real-time collaborative web apps.

  22. 𝗗𝗮𝘁𝗮𝘀𝘁𝗮𝗿:

    #Hypermedia #Framework #Datastar

    thewhale.cc/posts/datastar

    Datastar is a lightweight framework for building everything from simple sites to real-time collaborative web apps.

  23. #ThoughtProvoker 🤔

    There are interesting paradigm shifts possible today, which result in great opportunities to break the browser oligopoly, and SaaS + cloud vendor hegemony of Web 2.0 with its Rube Goldberg technology stack.

    @strypey referred to one of them, in a post to the Open App Ecosystem community group on #Loomio: The #hypermedia #web.

    Since my hobby (it doesn't earn income yet) involves elaborating #SX methodology as a Social experience designer, I thought it interesting to add my follow-up from that perspective..

    loomio.com/d/VYPyO17M/building

    #SocialCoding #SocialExperienceDesign #SocialWeb #fediverse

  24. #ThoughtProvoker 🤔

    There are interesting paradigm shifts possible today, which result in great opportunities to break the browser oligopoly, and SaaS + cloud vendor hegemony of Web 2.0 with its Rube Goldberg technology stack.

    @strypey referred to one of them, in a post to the Open App Ecosystem community group on #Loomio: The #hypermedia #web.

    Since my hobby (it doesn't earn income yet) involves elaborating #SX methodology as a Social experience designer, I thought it interesting to add my follow-up from that perspective..

    loomio.com/d/VYPyO17M/building

    #SocialCoding #SocialExperienceDesign #SocialWeb #fediverse

  25. #ThoughtProvoker 🤔

    There are interesting paradigm shifts possible today, which result in great opportunities to break the browser oligopoly, and SaaS + cloud vendor hegemony of Web 2.0 with its Rube Goldberg technology stack.

    @strypey referred to one of them, in a post to the Open App Ecosystem community group on #Loomio: The #hypermedia #web.

    Since my hobby (it doesn't earn income yet) involves elaborating #SX methodology as a Social experience designer, I thought it interesting to add my follow-up from that perspective..

    loomio.com/d/VYPyO17M/building

    #SocialCoding #SocialExperienceDesign #SocialWeb #fediverse

  26. #ThoughtProvoker 🤔

    There are interesting paradigm shifts possible today, which result in great opportunities to break the browser oligopoly, and SaaS + cloud vendor hegemony of Web 2.0 with its Rube Goldberg technology stack.

    @strypey referred to one of them, in a post to the Open App Ecosystem community group on #Loomio: The #hypermedia #web.

    Since my hobby (it doesn't earn income yet) involves elaborating #SX methodology as a Social experience designer, I thought it interesting to add my follow-up from that perspective..

    loomio.com/d/VYPyO17M/building

    #SocialCoding #SocialExperienceDesign #SocialWeb #fediverse

  27. #ThoughtProvoker 🤔

    There are interesting paradigm shifts possible today, which result in great opportunities to break the browser oligopoly, and SaaS + cloud vendor hegemony of Web 2.0 with its Rube Goldberg technology stack.

    @strypey referred to one of them, in a post to the Open App Ecosystem community group on #Loomio: The #hypermedia #web.

    Since my hobby (it doesn't earn income yet) involves elaborating #SX methodology as a Social experience designer, I thought it interesting to add my follow-up from that perspective..

    loomio.com/d/VYPyO17M/building

    #SocialCoding #SocialExperienceDesign #SocialWeb #fediverse

  28. 🥳 New Kitten Release

    • Fix: Events on `KittenComponent` hierarchies are now bubbled in reverse (from children down to parents). This provides for predictable event firing in cases where parents might emit events (e.g., a page emitting an event from its `onConnect()` handler). Your existing code should work as before with certain edge cases that might have broken before no longer breaking.

    Enjoy!

    :kitten:💕

    #Kitten #KittenReleases #SmallWeb #SmallTech #web #dev #events #serverSide #eventBased #components #hypermedia #streamingHTML

  29. 🥳 New Kitten Release

    • Fix: Events on `KittenComponent` hierarchies are now bubbled in reverse (from children down to parents). This provides for predictable event firing in cases where parents might emit events (e.g., a page emitting an event from its `onConnect()` handler). Your existing code should work as before with certain edge cases that might have broken before no longer breaking.

    Enjoy!

    :kitten:💕

    #Kitten #KittenReleases #SmallWeb #SmallTech #web #dev #events #serverSide #eventBased #components #hypermedia #streamingHTML

  30. 🥳 New Kitten Release

    • Fix: Events on `KittenComponent` hierarchies are now bubbled in reverse (from children down to parents). This provides for predictable event firing in cases where parents might emit events (e.g., a page emitting an event from its `onConnect()` handler). Your existing code should work as before with certain edge cases that might have broken before no longer breaking.

    Enjoy!

    :kitten:💕

    #Kitten #KittenReleases #SmallWeb #SmallTech #web #dev #events #serverSide #eventBased #components #hypermedia #streamingHTML

  31. 🥳 New Kitten Release

    • Fix: Events on `KittenComponent` hierarchies are now bubbled in reverse (from children down to parents). This provides for predictable event firing in cases where parents might emit events (e.g., a page emitting an event from its `onConnect()` handler). Your existing code should work as before with certain edge cases that might have broken before no longer breaking.

    Enjoy!

    :kitten:💕

    #Kitten #KittenReleases #SmallWeb #SmallTech #web #dev #events #serverSide #eventBased #components #hypermedia #streamingHTML

  32. 🥳 New Kitten Release

    • Fix: Events on `KittenComponent` hierarchies are now bubbled in reverse (from children down to parents). This provides for predictable event firing in cases where parents might emit events (e.g., a page emitting an event from its `onConnect()` handler). Your existing code should work as before with certain edge cases that might have broken before no longer breaking.

    Enjoy!

    :kitten:💕

    #Kitten #KittenReleases #SmallWeb #SmallTech #web #dev #events #serverSide #eventBased #components #hypermedia #streamingHTML

  33. 🥳 New Kitten Release

    • `KittenComponent` (and thereby `KittenPage`) gains an `emit()` method.

    Use this to bubble events from your page to all child components or from any component to all of its child components.

    This is useful, for example, for setting the state of a page or a component where each child component knows how to present itself for that state.

    (That, in turn, is useful if you want to be able to restore state based on URLs.)

    The naming convention-based mapping of event names to event handler names is the same as for the events you receive from the client. So an event called `myEvent` will result in `onMyEvent` handlers on child components being called.

    (Also update @small-web/kitten to version 7.1.0 to get language intelligence for the new method.)

    Enjoy!

    :kitten:💕

    #Kitten #KittenReleases #SmallWeb #SmallTech #web #dev #events #serverSide #eventBased #components #hypermedia #streamingHTML

  34. 🥳 New Kitten Release

    • `KittenComponent` (and thereby `KittenPage`) gains an `emit()` method.

    Use this to bubble events from your page to all child components or from any component to all of its child components.

    This is useful, for example, for setting the state of a page or a component where each child component knows how to present itself for that state.

    (That, in turn, is useful if you want to be able to restore state based on URLs.)

    The naming convention-based mapping of event names to event handler names is the same as for the events you receive from the client. So an event called `myEvent` will result in `onMyEvent` handlers on child components being called.

    (Also update @small-web/kitten to version 7.1.0 to get language intelligence for the new method.)

    Enjoy!

    :kitten:💕

    #Kitten #KittenReleases #SmallWeb #SmallTech #web #dev #events #serverSide #eventBased #components #hypermedia #streamingHTML

  35. 🥳 New Kitten Release

    • `KittenComponent` (and thereby `KittenPage`) gains an `emit()` method.

    Use this to bubble events from your page to all child components or from any component to all of its child components.

    This is useful, for example, for setting the state of a page or a component where each child component knows how to present itself for that state.

    (That, in turn, is useful if you want to be able to restore state based on URLs.)

    The naming convention-based mapping of event names to event handler names is the same as for the events you receive from the client. So an event called `myEvent` will result in `onMyEvent` handlers on child components being called.

    (Also update @small-web/kitten to version 7.1.0 to get language intelligence for the new method.)

    Enjoy!

    :kitten:💕

    #Kitten #KittenReleases #SmallWeb #SmallTech #web #dev #events #serverSide #eventBased #components #hypermedia #streamingHTML

  36. 🥳 New Kitten Release

    • `KittenComponent` (and thereby `KittenPage`) gains an `emit()` method.

    Use this to bubble events from your page to all child components or from any component to all of its child components.

    This is useful, for example, for setting the state of a page or a component where each child component knows how to present itself for that state.

    (That, in turn, is useful if you want to be able to restore state based on URLs.)

    The naming convention-based mapping of event names to event handler names is the same as for the events you receive from the client. So an event called `myEvent` will result in `onMyEvent` handlers on child components being called.

    (Also update @small-web/kitten to version 7.1.0 to get language intelligence for the new method.)

    Enjoy!

    :kitten:💕

    #Kitten #KittenReleases #SmallWeb #SmallTech #web #dev #events #serverSide #eventBased #components #hypermedia #streamingHTML

  37. 🥳 New Kitten Release

    • `KittenComponent` (and thereby `KittenPage`) gains an `emit()` method.

    Use this to bubble events from your page to all child components or from any component to all of its child components.

    This is useful, for example, for setting the state of a page or a component where each child component knows how to present itself for that state.

    (That, in turn, is useful if you want to be able to restore state based on URLs.)

    The naming convention-based mapping of event names to event handler names is the same as for the events you receive from the client. So an event called `myEvent` will result in `onMyEvent` handlers on child components being called.

    (Also update @small-web/kitten to version 7.1.0 to get language intelligence for the new method.)

    Enjoy!

    :kitten:💕

    #Kitten #KittenReleases #SmallWeb #SmallTech #web #dev #events #serverSide #eventBased #components #hypermedia #streamingHTML

  38. Rich and balanced comparison of the performance of SPA and hypermedia based web app with interesting findings 👏 The post includes limitations/caveats along with balanced when-to-use recommendations 👍

    #SPA #web #hypermedia #performance

    zweiundeins.gmbh/en/methodolog

  39. Rich and balanced comparison of the performance of SPA and hypermedia based web app with interesting findings 👏 The post includes limitations/caveats along with balanced when-to-use recommendations 👍

    #SPA #web #hypermedia #performance

    zweiundeins.gmbh/en/methodolog

  40. Rich and balanced comparison of the performance of SPA and hypermedia based web app with interesting findings 👏 The post includes limitations/caveats along with balanced when-to-use recommendations 👍

    #SPA #web #hypermedia #performance

    zweiundeins.gmbh/en/methodolog

  41. Rich and balanced comparison of the performance of SPA and hypermedia based web app with interesting findings 👏 The post includes limitations/caveats along with balanced when-to-use recommendations 👍

    #SPA #web #hypermedia #performance

    zweiundeins.gmbh/en/methodolog

  42. @steve @evan

    Oh, that is very interesting. I will queue this up for inclusion in the delightful fediverse development curated list.

    #Datastar may be a great library to check out here, and goes further in #hypermedia approach, where #HTMX considers itself feature-complete. Datastar uses #SSE to keep the connection to the client open. The client-side JS lib that is needed is super small. In datastar apps most of the business logic lives in the backend, and it lends itself very well for #EventSourcing. The original author/co-maintainer uses it with #NATS which also serves as the event store.

    data-star.dev

  43. @steve @evan

    Oh, that is very interesting. I will queue this up for inclusion in the delightful fediverse development curated list.

    #Datastar may be a great library to check out here, and goes further in #hypermedia approach, where #HTMX considers itself feature-complete. Datastar uses #SSE to keep the connection to the client open. The client-side JS lib that is needed is super small. In datastar apps most of the business logic lives in the backend, and it lends itself very well for #EventSourcing. The original author/co-maintainer uses it with #NATS which also serves as the event store.

    data-star.dev

  44. @steve @evan

    Oh, that is very interesting. I will queue this up for inclusion in the delightful fediverse development curated list.

    #Datastar may be a great library to check out here, and goes further in #hypermedia approach, where #HTMX considers itself feature-complete. Datastar uses #SSE to keep the connection to the client open. The client-side JS lib that is needed is super small. In datastar apps most of the business logic lives in the backend, and it lends itself very well for #EventSourcing. The original author/co-maintainer uses it with #NATS which also serves as the event store.

    data-star.dev

  45. @steve @evan

    Oh, that is very interesting. I will queue this up for inclusion in the delightful fediverse development curated list.

    #Datastar may be a great library to check out here, and goes further in #hypermedia approach, where #HTMX considers itself feature-complete. Datastar uses #SSE to keep the connection to the client open. The client-side JS lib that is needed is super small. In datastar apps most of the business logic lives in the backend, and it lends itself very well for #EventSourcing. The original author/co-maintainer uses it with #NATS which also serves as the event store.

    data-star.dev

  46. @steve @evan

    Oh, that is very interesting. I will queue this up for inclusion in the delightful fediverse development curated list.

    #Datastar may be a great library to check out here, and goes further in #hypermedia approach, where #HTMX considers itself feature-complete. Datastar uses #SSE to keep the connection to the client open. The client-side JS lib that is needed is super small. In datastar apps most of the business logic lives in the backend, and it lends itself very well for #EventSourcing. The original author/co-maintainer uses it with #NATS which also serves as the event store.

    data-star.dev

  47. Is HTMX's dogmatic insistence on HTML holding it back? Discover JSON partials as the future of cross-platform UI and secure AI-generated hypermedia interfaces. hackernoon.com/the-html-partia #hypermedia

  48. Is HTMX's dogmatic insistence on HTML holding it back? Discover JSON partials as the future of cross-platform UI and secure AI-generated hypermedia interfaces. hackernoon.com/the-html-partia #hypermedia

  49. Is HTMX's dogmatic insistence on HTML holding it back? Discover JSON partials as the future of cross-platform UI and secure AI-generated hypermedia interfaces. hackernoon.com/the-html-partia #hypermedia

  50. Is HTMX's dogmatic insistence on HTML holding it back? Discover JSON partials as the future of cross-platform UI and secure AI-generated hypermedia interfaces. hackernoon.com/the-html-partia

  51. Is HTMX's dogmatic insistence on HTML holding it back? Discover JSON partials as the future of cross-platform UI and secure AI-generated hypermedia interfaces. hackernoon.com/the-html-partia #hypermedia