{
  "@context":[
    "https://www.w3.org/ns/activitystreams",
    {"Hashtag":"as:Hashtag"}
  ],
  "published":"2024-10-26T13:38:28.691Z",
  "attributedTo":"https://epiktistes.com/actors/toddsundsted",
  "replies":"https://epiktistes.com/objects/_mfoFbzmzd8/replies",
  "to":["https://www.w3.org/ns/activitystreams#Public"],
  "cc":["https://epiktistes.com/actors/toddsundsted/followers"],
  "content":"<p>TIL <a href=\"https://developer.mozilla.org/en-US/docs/Web/CSS/@media/scripting\">scripting media queries</a>... gone are the days of the <code>no-js</code> class on the <code>body</code> tag...</p><p>i'm working on improving the <a href=\"https://github.com/toddsundsted/ktistec\">ktistec</a> user experience when <em>javascript is disabled</em>.</p><p>ktistec uses <a href=\"https://github.com/basecamp/trix\">trix</a> as its rich text editor.  of course. trix doesn't work without javascript. behind the scenes, however, trix uses a hidden <code>textarea</code> to hold the body of the post being edited. using scripting media queries, ktistec can now show (or hide) either the editor or the <code>textarea</code> based on the availability of javascript (<a href=\"https://github.com/toddsundsted/ktistec/commit/2030b26b34330918d0c9fea4678bb448d8e24f76\">2030b26b</a>). </p><p><a href=\"https://epiktistes.com/tags/ktistec\" class=\"hashtag\" rel=\"tag\">#ktistec</a> <a href=\"https://epiktistes.com/tags/activitypub\" class=\"hashtag\" rel=\"tag\">#activitypub</a> <a href=\"https://epiktistes.com/tags/fediverse\" class=\"hashtag\" rel=\"tag\">#fediverse</a></p>",
  "mediaType":"text/html",
  "attachment":[],
  "tag":[
      {"type":"Hashtag","name":"#ktistec","href":"https://epiktistes.com/tags/ktistec"},
      {"type":"Hashtag","name":"#activitypub","href":"https://epiktistes.com/tags/activitypub"},
      {"type":"Hashtag","name":"#fediverse","href":"https://epiktistes.com/tags/fediverse"}
  ],
  "type":"Note",
  "id":"https://epiktistes.com/objects/hZN4JBNHwnY"
}