Mozilla is playing with fire. I don't like their latest "AI" pivot. AI doesn't exist and never will, and whatever is called AI right now is not it. And is not worth using.

Seriously, "AI text" "detectors"? They don't really work that well. They sometimes also misidentify input texts written by someone not proficient with language as LLM output.

happy birthday to me! 🎉🎉🎉

Tailscale, without any sort of warning or public announcement, seems to have banned all Russian IPs from connecting to its coordination server.

I had to spend an entire workday migrating my setup to Headscale, the self-hosted alternative! I could've spent this time playing games or working, if not for this bullshit!

This "pseudo-sanctions compliance" virtue signalling must stop. All lawyers and PR personnel responsible for this should be fired and shunned. VPNs are critical to allow people in oppressive countries to get truth via the Internet, and just banning them from connecting to VPNs is exactly what the oppressors want.

My markdown parser refuses to accept HTML input for some reason. I wonder why. This is not really compliant with the Markdown standard.

If I were to include a quote made by a language model on my website, I'd like them to be specifically highlighted to make it obvious that the output was not written by a human.

Something like this, maybe?

figure.llm-quote {
  background: #ddd;
  border-left: 0.5em solid black;
  border-image: repeating-linear-gradient(45deg, #000000, #000000 0.75em, #FFFF00 0.75em, #FFFF00 1.5em) 8;
  padding: 0.5em;
  padding-left: 0.75em;
  margin-left: 3em;
}
figure.llm-quote > figcaption {
  font-size: 0.95em;
  font-style: italic;
}
@media (prefers-color-scheme: dark) {
  figure.llm-quote {
    color: #f0f0f0;
    background-color: #242424;
  }
}

And use it like this:

<figure class="llm-quote">
  <blockquote>
<p>I'm an artificial intelligence model known as Llama. Llama stands for "Large Language Model Meta AI."</p>
  </blockquote>
  <figcaption>
    Output generated by Llama 3.2-3B
  </figcaption>
</figure>

To get something like this (I sure hope this will display correctly! I still need to tweak my Markdown parser a bit.):

is it a bad idea to overload the subtraction operator on an MF2 post type to produce a difference between the two posts in the Micropub update format?

An addition of a post and a diff would, of course, patch the post with a diff, for symmetry.

Just realized Kittybox doesn't even display the p-summary field anywhere yet. What a shame. Gotta fix that later.

So nice to see random websites support Webmentions!

Fun fact: I'm building a Micropub posting app, and one of it's features is letting the user automatically draft a summary for the post they're writing; I wonder what would happen if I fed it this post...

Hello! IndieAuth seems to be working in Bowl now. It even stores the tokens in the GNOME Keyring for me!

The code is really janky and I would like to refactor it before actually publishing. But it's good enough to post from, so I guess this is a victory.

It's kinda nice to be able to post from my own Micropub client. Feels liberating.

From #indieweb-dev:

...but it breaks outdated clients that aren't updated... How much ground an I willing to give to outdated software?

why did I ever think it would be a "small" refactor?!

Added a ToastOverlay to the post composer.

Currently thinking to do a small refactor to make the posting logic independent from the UI (currently the UI contains the logic to post, but I want to make the parent component responsible for posting).

I also need to implement the tag list component.

It looks like private posts are working, but aren't shown in the feed. I guess I gotta fix this.

(Also making Ctrl+Enter send posts in Bowl would be nice.)

if you can see this, my new micropub client written in GTK4 and Rust is working! It's called Bowl and I really want to publish it soon!

(but I need to make IndieAuth work first — I had to manually retrieve a token to crate this post.

also i think i need to make the window scrollable.