2024-09-29T12:08:15Z (#7wdvhia) @<lyse https://lyse.isobeef.org/twtxt.txt> love 27! Is that your town as seeing from the mountain, or some other town? From 395 to 40 is quite some picking! I figure that’s the most difficult part, right?
Ah, 16°C… what dreams are made of! 😍
2024-09-29T12:08:15Z\t(#7wdvhia) @<lyse https://lyse.isobeef.org/twtxt.txt> love 27! Is that your town as seeing from the mountain, or some other town? From 395 to 40 is quite some picking! I figure that’s the most difficult part, right?
Ah, 16°C… what dreams are made of! 😍
Ah, 16°C… what dreams are made of! 😍
Happening now: https://meet.mills.io/call/Yarn.social
> "@bender I am also in camp no edit signals. deletes only breaks the head of a thread. all the replies are unaffected."
I figure I could also answer *every* single twtxt like this, so that if the original gets edited, or deleted, at least I don't sound foolish without knowing exactly what I replied to. 🤭
That board is really… something (really can’t explain it with words). Also found interesting that’s a board for a single five-stars user, “Admin”. 😳
> 3.4 Multi-Line Twts: What exactly do you think are bad things with multi-lines?
OP doesn’t want/like markdown (or some of it). He believes multi-lines propitiates or, rather, encourages it.
> "Edits and Deletions should go; see also Section 6. This is probably the worst example of this document pushing a text document to do more protocol-like things."
Edit and deletions are precisely what brought us here. Currently, if one replies to a twtxt, and the original gets later edited, it breaks replies, and potentially drastically changes context.
Anyway… cheers!
Joy starts at you, not the platform you use. When you get bored, disgusted, offended, and leave X, come and let us know. I will be interested to read all about your experiment then. For now, “¡hasta pronto!”
I have little to contribute on this reply. On bullet two, he meant the original hash. On the last bullet, markdown is already part of it (after all, it is plain text). Yarn, being a web client/server, simply renders it.
1. Add the ability to allow feed address changes.
2. Increase hash from 7 to 11, and/or change the hashing algorithm to something else, better.
3. Implement
movq (I simply can’t mention while on mobile) second option (the one you like, which maintains content addressing).
(replyto:...) as well. If the feed changes, well, it is the same as changing emails (and deleting the old one). No?
2024-09-19T20:20:00+02:00\tI don't like Australians!
And then deleted it, fearing the Australian Mafia (which, as we know, is very powerful in Bavaria). But I got the hash for it,
p5zdahq, and that timestamp has tt written all over it. That's my proof! 😅😅😅
2024-09-19T20:20:00+02:00 I don't like Australians!
And then deleted it, fearing the Australian Mafia (which, as we know, is very powerful in Bavaria). But I got the hash for it,
p5zdahq, and that timestamp has tt written all over it. That's my proof! 😅😅😅
😂😂😂
", and other "spurious" characters in it?
main.go (but it can be done on a template now, so no reason to touch the code):
<time class="dt-published" datetime="{{ $twt.Created | date "2006-01-02T15:04:05Z07:00" }}">
{{ $twt.Created | date "2006-01-02 15:04:05 MST" }}
</time>
See https://ferengi.one. I am going to further customise things, but that's a start.
+0000 UTC+0000. Same on a local test I am running.I tried changing
{{ $twt.Created | date "2006-01-02T15:04:05Z07:00" }} to {{ $twt.Created | date "2006-01-02T15:04:05" }}, but no dice. I don't really care about the timezone. LOL.
<!DOCTYPE html>
<html lang="en">
<head>
<link rel="stylesheet" href="https://cdn.simplecss.org/simple.min.css">
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0">
<title>{{ .Title }}</title>
</head>
\t<body class="preload">
\t <main class="container">
\t\t{{ range $_, $twt := $.Twts }}
\t\t <article id="{{ $twt.Hash }}" class="h-entry">
\t\t\t<div class="u-author h-card">
\t\t\t <div class="dt-publish">
\t\t\t\t<a class="u-url" href="#{{ $twt.Hash }}">
\t\t\t\t <time class="dt-published" datetime="{{ $twt.Created | date "2006-01-02T15:04:05Z07:00" }}">
\t\t\t\t\t{{ $twt.Created }}
\t\t\t\t </time>
\t\t\t\t</a>
\t\t\t\t<span> {{ $twt.Created | time }}</span>
\t\t\t\t<a class="u-search" href="https://search.twtxt.net/twt/{{ $twt.Hash }}">(search)</a>
\t\t\t </div>
\t\t\t</div>
\t\t\t<div class="e-content">
\t\t\t {{ formatTwt $twt }}
\t\t\t</div>
\t\t </article>
\t\t{{ end }}
\t </main>
\t</body>
</html>
<!DOCTYPE html>
<html lang="en">
<head>
<link rel="stylesheet" href="https://cdn.simplecss.org/simple.min.css">
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0">
<title>{{ .Title }}</title>
</head>
<body class="preload">
<main class="container">
{{ range $_, $twt := $.Twts }}
<article id="{{ $twt.Hash }}" class="h-entry">
<div class="u-author h-card">
<div class="dt-publish">
<a class="u-url" href="#{{ $twt.Hash }}">
<time class="dt-published" datetime="{{ $twt.Created | date "2006-01-02T15:04:05Z07:00" }}">
{{ $twt.Created }}
</time>
</a>
<span> {{ $twt.Created | time }}</span>
<a class="u-search" href="https://search.twtxt.net/twt/{{ $twt.Hash }}">(search)</a>
</div>
</div>
<div class="e-content">
{{ formatTwt $twt }}
</div>
</article>
{{ end }}
</main>
</body>
</html>
jenny to convert twtxt.txt to HTML using @prologic's code?
jenny renders this:
Original:
Modified:
Lyse's sunset
Order placed!Now the wait starts. 😩😂