mckinley
twtxt.net
A guy on the internet. https://mckinley.cc/
Recent twts from mckinley
↳
In-reply-to
»
Budgie vs Gnome vs KDE vs Deepin
↳
In-reply-to
»
I was checking in my notes from 2019, that before using https://enso.sonnet.io, I used Calmly Writer
@eaplmx@twtxt.net I just use stock Vim with no plugins. It does everything I need it to do.
↳
In-reply-to
»
@eaplmx It's a plugin to VSCode / Codiium itself yes 👌 Essentially it replaces the garbage editor with a Neo Vim instance 🤣
@prologic@twtxt.net I remember, quite some time ago, we were talking about wanting vi keys in Web browser text boxes. A few weeks ago, I found an extension that does a similar thing to this, it puts a Neovim client into your Web browser. https://github.com/glacambre/firenvim
↳
In-reply-to
»
I ducked out early this week, but it was a good chat with @prologic and @ocdtrekkie. Some things we talked about:
* The twtxt specification rewrite I'm working on
* @ocdtrekkie's work on tube
* Electron *shudder*
* JSON Feeds
* GitHub forking mysteries
@ocdtrekkie@twtxt.net My apologies, I mistyped.
I ducked out early this week, but it was a good chat with @prologic@twtxt.net and @ocdtrekkie@twtxt.net. Some things we talked about:
- The twtxt specification rewrite I’m working on
- @ocdtrekkie@twtxt.net’s work on tube
- Electron *shudder*
- JSON Feeds
- GitHub forking mysteries
↳
In-reply-to
»
Does someone know something about locutus (except that they are start trek fan)
@tkanos@twtxt.net All the “decentralized software platforms” are starting to blur together.
↳
In-reply-to
»
Who's attending our weekly video call today? Starts in 1hr from now at 5am UTC
@prologic@twtxt.net I’ll be there.
↳
In-reply-to
»
#215 - Newlines without Unicode - yarn - Mills -- We discussed the idea of changing the way we handle Newlines in Twts once upon a time, but nobody adopted it, we didn't amend the spec and really we just kept the existing spec as-is using the
\2028 and simpler search/replace in place. Did we want to revisit this again in a potential Twtxt v2 spec rewrite, or are we happy with how this works? 🤔 cc @movq @lyse @tkanos (please add other client authors to this thread) #Twtxt #Spec #Multiline
It also says “A specific ordering of the statuses is not mandatory,” implying that the order of the lines in the file is irrelevant. If newlines are separate posts with the same timestamp, the original line order becomes very relevant. I can see how a client (that doesn’t support this newline syntax) might display posts with the same timestamp in the wrong order because of this.
↳
In-reply-to
»
#215 - Newlines without Unicode - yarn - Mills -- We discussed the idea of changing the way we handle Newlines in Twts once upon a time, but nobody adopted it, we didn't amend the spec and really we just kept the existing spec as-is using the
\2028 and simpler search/replace in place. Did we want to revisit this again in a potential Twtxt v2 spec rewrite, or are we happy with how this works? 🤔 cc @movq @lyse @tkanos (please add other client authors to this thread) #Twtxt #Spec #Multiline
@prologic@twtxt.net I don’t think the solution proposed there is a good one, and here are my reasons.
The specification says quite clearly, “The file must be encoded with UTF-8”. If an old piece of software can’t handle UTF-8, it can’t produce a valid twtxt feed at all.
I believe the intention behind this solution is to make it render in an acceptable fashion in clients that don’t support the convention, but I think it’s the opposite in reality. Separating posts like that could make it very frustrating to read in a feed. I would much rather have nothing or a replacement character separating logical lines.
I think it interferes quite heavily with human readability for the same reason. When reading a twtxt feed, it’s helpful to know that each line with a timestamp represents one post.
I just typed out a message here on Yarn, undid a few things with ctrl+z, and then tried to redo something with the vi redo key combination. That means it’s time to go to bed.