mckinley

twtxt.net

A guy on the internet. https://mckinley.cc/

Recent twts from mckinley
In-reply-to » @mckinley Kind of wondering whether you'd contribute your XLST to yarnd so we can use/apply it to all Atom feeds of the Pod's timeline and User feeds (presented as Atom)? 🤔 Could be interesting? 🤔

These aren’t things I could fix myself, and in my opinion some of them wouldn’t be worth it if I could.

⤋ Read More
In-reply-to » @mckinley Kind of wondering whether you'd contribute your XLST to yarnd so we can use/apply it to all Atom feeds of the Pod's timeline and User feeds (presented as Atom)? 🤔 Could be interesting? 🤔

@prologic It would definitely be interesting. I don’t think there could be any substantial code reuse but I’m open to the idea. I looked into doing it, but there are a few hangups that would probably need to be addressed first:

  • Something in the pipeline is adding U+FFFD Replacement Characters to the ends of certain twts
  • Markdown isn’t rendered to HTML in the Atom feed, but mentions are.
  • <summary> elements (which should probably be <contents> instead) are type="html", escaped HTML. It wouldn’t be possible to embed twt contents in the generated page on Firefox-based browsers due to my favorite bug
    • The other options are either plain text or inline XHTML which means you have to make sure every twt is valid XHTML.
  • I don’t know how to handle different themes short of JavaScript which can be buggy when used with client-side XSLT or dynamically generated XSLT which is completely and utterly ridiculous.

⤋ Read More
In-reply-to » I have been hacking away on replacing the PicoCSS with Simple.css, since it offer a much manageable set of color variables that can ease the work of making your own team a whole lot.

@darch@neotxt.dk That’s exactly what I was thinking, it looks really nice. I can’t decide if I like the dark/blue or the dark/yellow theme better.

⤋ Read More
In-reply-to » I have been hacking away on replacing the PicoCSS with Simple.css, since it offer a much manageable set of color variables that can ease the work of making your own team a whole lot.

@darch@neotxt.dk I’m talking about the gray color for the Tabler icons in the first two themes, i.e. the rich text buttons. I was wondering what they would look like if they used the theme’s accent color or the text color. Now that I think of it, the text color wouldn’t look right either.

The third theme (black/yellow) uses the accent color for those buttons. I was using that as an example.

⤋ Read More
In-reply-to » I have been hacking away on replacing the PicoCSS with Simple.css, since it offer a much manageable set of color variables that can ease the work of making your own team a whole lot.

@darch@neotxt.dk Looks great. What would the 1st and 2nd themes look like if the icons were the color of the text? Or the accent color like the 4th theme?

⤋ Read More
In-reply-to » I was bored tonight, so I created a generator of twtxt file using git (https://github.com/tkanos/gitwtxt) : - Each commit is a message - Each branch is a thread --> Then I generate a twtxt file out of it.

@prologic@twtxt.net I must be mistaken. I thought, when we realized @maya@maya.land was still posting in the future, that there was an entire thread (with a /conv/ page) and the hash didn’t resolve to anything until the timestamp of the parent twt. Perhaps yarnd gave it a /conv/ page because it knew about the twt but didn’t display it because it was in the future. Perhaps I need to go to bed.

⤋ Read More
In-reply-to » I was bored tonight, so I created a generator of twtxt file using git (https://github.com/tkanos/gitwtxt) : - Each commit is a message - Each branch is a thread --> Then I generate a twtxt file out of it.

I wonder, what’s stopping users from not following the twt hash spec and prepending a Git commit hash to every new post? AFAIK yarnd will display the oldest post it has for a hash as the root, but it assumes that it’s a reply to another post with that hash and that people replying should add to that chain. I’m not advocating for breaking the spec, but how do other clients handle this?

⤋ Read More
In-reply-to » Hahaha, brilliant! https://scrolller.com/snip-off-yer-damned-ends-3kvk3v18hb And with that I'm off to bed. https://scrolller.com/yeah-yeah-right-it-s-not-my-first-core-sample-drv0r837k3

Completely off topic: I was hoping to make a redirect rule for Scrolller to Libreddit, but it seems their post IDs are just random.

I did find that the original path on Reddit is in the page inside a stringified JSON object as a global variable defined in a script element. JSON.parse(window.scrolllerConfig).item.redditPath will return the path.

I suppose this could be done with a userscript, but the whole point is to not load the Scrolller page. Interestingly, the first one you posted has been deleted from Reddit.

⤋ Read More
In-reply-to » The last two times I tapped milk I thought: that's never a whole liter, so much air left in the bottle. Just now the bottle overflowed. Couldn't see in the pitch dark.

@lyse@lyse.isobeef.org I figured it was a milk vending machine, but I’d never heard of such a thing. Interesting. That’s better than Canadian bagged milk.

⤋ Read More

A very insightful chat tonight with @prologic@twtxt.net, @ocdtrekkie, @darch@neotxt.dk, and @ocdtrekkie’s friend Ian who is, presumably, still primarily using legacy social networks. Hopefully we can change that. Some things we talked about tonight:

  • The rationale behind GoNix
  • @darch@neotxt.dk’s thoughts on social networking (https://blog.neotxt.dk/)
  • Bringing people on to free platforms
  • Bot prevention on Yarn.social (#981)
  • Funding for Yarn.social
  • Goryon, material design, and satanism

⤋ Read More