10 Male-Female Duos Who Don’t Fall in Love
Of all the feelings you can experience, love is the most coveted. Screenwriters seem to think so, at least, as many insert romances into virtually every story. If circumstances pair a male and female character together, the odds are that they’ll end up in love. This journey can, admittedly, be sweet, but it’s also predictable […]

The post [10 Male-Female Duos Who Don’t Fall in Love](https://listverse.com/2025/02/14/10-male-female-duos-who-dont-fal … ⌘ Read more

10 Broadway Props That Stole The Show
Broadway is known for its dazzling performances, unforgettable characters, and, of course, incredible props that help bring the magic to life. While the actors’ talent is the star of the show, some props have a way of stealing the spotlight and becoming just as iconic as the performances themselves. From inanimate objects that take on […]

The post [10 Broadway Props That Stole The Show](https://listverse.com/2025/02/13/10-broadway-props-that-stole-the-show … ⌘ Read more

10 Hilarious Characters Who Never Shut Up
Writers tow a fine line with chatty characters. If handled poorly, these figures can be recipes for disaster. Their incessant talking can easily grate on audiences’ nerves. The effect is akin to being annoyed by a hyperactive kid. Because of that risk, it’s safe to veer away from such characters. However, they’re not impossible to […]

The post [10 Hilarious Characters Who Never Shut Up](https://listverse.com/2025/01/27/10-hilarious-characters-who-n … ⌘ Read more

@bender@twtxt.net @prologic@twtxt.net I’m not exactly asking yarnd to change. If you are okay with the way it displayed my twts, then by all means, leave it as is. I hope you won’t mind if I continue to write things like 1/4 to mean “first out of four”.

What has text/markdown got to do with this? I don’t think Markdown says anything about replacing 1/4 with ¼, or other similar transformations. It’s not needed, because ¼ is already a unicode character that can simply be directly inserted into the text file.

What’s wrong with my original suggestion of doing the transformation before the text hits the twtxt.txt file? @prologic@twtxt.net, I think it would achieve what you are trying to achieve with this content-type thing: if someone writes 1/4 on a yarnd instance or any other client that wants to do this, it would get transformed, and other clients simply wouldn’t do the transformation. Every client that supports displaying unicode characters, including Jenny, would then display ¼ as ¼.

Alternatively, if you prefer yarnd to pretty-print all twts nicely, even ones from simpler clients, that’s fine too and you don’t need to change anything. My 1/4 -> ¼ thing is nothing more than a minor irritation which probably isn’t worth overthinking.

@prologic@twtxt.net I wrote ¼ (one slash four) by which I meant “the first out of four”. twtxt.net is showing it as ¼, a single character that IMO doesn’t have that same meaning (it means 0.25). Similarly, ¾ got replaced with ¾ in another twt. It’s not a big deal. It just looks a little wrong, especially beside the 2/4 and 4/4 in my other two twts.

Thanks @david@collantes.us, good to know, but we need to agree on what character we use, otherwise the hashes will not be the same:)

@movq@www.uninformativ.de Agreed that hashes have a benefit. I came up with a similar example where when I twted about an 11-character hash collision. Perhaps hashes could be made optional somehow. Like, you could use the “replyto” idea and then additionally put a hash somewhere if you want to lock in which version of the twt you are replying to.

@prologic@twtxt.net

There’s a simple reason all the current hashes end in a or q: the hash is 256 bits, the base32 encoding chops that into groups of 5 bits, and 256 isn’t divisible by 5. The last character of the base32 encoding just has that left-over single bit (256 mod 5 = 1).

So I agree with #3 below, but do you have a source for #1, #2 or #4? I would expect any lack of variability in any part of a hash function’s output would make it more vulnerable to attacks, so designers of hash functions would want to make the whole output vary as much as possible.

Other than the divisible-by-5 thing, my current intuition is it doesn’t matter what part you take.

1. Hash Structure: Hashes are typically designed so that their outputs have specific statistical properties. The first few characters often have more entropy or variability, meaning they are less likely to have patterns. The last characters may not maintain this randomness, especially if the encoding method has a tendency to produce less varied endings.

2. Collision Resistance: When using hashes, the goal is to minimize the risk of collisions (different inputs producing the same output). By using the first few characters, you leverage the full distribution of the hash. The last characters may not distribute in the same way, potentially increasing the likelihood of collisions.

3. Encoding Characteristics: Base32 encoding has a specific structure and padding that might influence the last characters more than the first. If the data being hashed is similar, the last characters may be more similar across different hashes.

4. Use Cases: In many applications (like generating unique identifiers), the beginning of the hash is often the most informative and varied. Relying on the end might reduce the uniqueness of generated identifiers, especially if a prefix has a specific context or meaning.

@sorenpeter@darch.dk I like this idea. Just for fun, I’m using a variant in this twt. (Also because I’m curious how it non-hash subjects appear in jenny and yarn.)

URLs can contain commas so I suggest a different character to separate the url from the date. Is this twt I’ve used space (also after “replyto”, for symmetry).

I think this solves:

• Changing feed identities: although @mckinley@twtxt.net points out URLs can change, I think this syntax should be okay as long as the feed at that URL can be fetched, and as long as the current canonical URL for the feed lists this one as an alternate.
  
• editing, if you don’t care about message integrity
  
• finding the root of a thread, if you’re not following the author
  

An optional hash could be added if message integrity is desired. (E.g. if you don’t trust the feed author not to make a misleading edit.) Other recent suggestions about how to deal with edits and hashes might be applicable then.

People publishing multiple twts per second should include sub-second precision in their timestamps. As you suggested, the timestamp could just be copied verbatim.

@movq@www.uninformativ.de we can shorten it by six characters, with (r:https://...). 😅

More:

Subject: The [tag URI scheme](https://en.wikipedia.org/wiki/Tag_URI_scheme) looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be
        somewhat trivial to parse. But there are still the issue with what the name/id should be... Maybe it doesn't have to bee that stick? Instead of using `tag:` as the prefix/protocol, it would more it clear
        what we are talking about by using `in-reply-to:` (https://indieweb.org/in-reply-to) or `replyto:` similar to `mailto:` 1. `(reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)' 2.
        `(in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)' 2. `(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)' I know it's longer that 7-11 characters, but it's self-explaining when looking at the
        twtxt.txt in the raw, and the cases above can all be caught with this regex: `\([\w-]*reply[\w-]*\:` Is this something that would work?

Subject: The [tag URI scheme](https://en.wikipedia.org/wiki/Tag_URI_scheme) looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be
        somewhat trivial to parse. But there are still the issue with what the name/id should be... Maybe it doesn't have to bee that stick? Instead of using `tag:` as the prefix/protocol, it would more it clear
        what we are talking about by using `in-reply-to:` (https://indieweb.org/in-reply-to) or `replyto:` similar to `mailto:` 1. `(reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)` 2.
        `(in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)` 3. `(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)` I know it's longer that 7-11 characters, but it's self-explaining when looking at the
        twtxt.txt in the raw, and the cases above can all be caught with this regex: `\([\w-]*reply[\w-]*\:` Is this something that would work?

Notice the difference? Soren edited, and broke everything.

The tag URI scheme looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be somewhat trivial to parse. But there are still the issue with what the name/id should be… Maybe it doesn’t have to bee that stick?

Instead of using tag: as the prefix/protocol, it would more it clear what we are talking about by using in-reply-to: (https://indieweb.org/in-reply-to) or replyto: similar to mailto:

1. (reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)
   
2. (in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)
   
3. (replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)
   

I know it’s longer that 7-11 characters, but it’s self-explaining when looking at the twtxt.txt in the raw, and the cases above can all be caught with this regex: \([\w-]*reply[\w-]*\:

Is this something that would work?

@prologic@twtxt.net earlier you suggested extending hashes to 11 characters, but here’s an argument that they should be even longer than that.

Imagine I found this twt one day at https://example.com/twtxt.txt :

2024-09-14T22:00Z Useful backup command: rsync -a “$HOME” /mnt/backup

Image

and I responded with “(#5dgoirqemeq) Thanks for the tip!”. Then I’ve endorsed the twt, but it could latter get changed to

2024-09-14T22:00Z Useful backup command: rm -rf /some_important_directory

Image

which also has an 11-character base32 hash of 5dgoirqemeq. (I’m using the existing hashing method with https://example.com/twtxt.txt as the feed url, but I’m taking 11 characters instead of 7 from the end of the base32 encoding.)

That’s what I meant by “spoofing” in an earlier twt.

I don’t know if preventing this sort of attack should be a goal, but if it is, the number of bits in the hash should be at least two times log2(number of attempts we want to defend against), where the “two times” is because of the birthday paradox.

Side note: current hashes always end with “a” or “q”, which is a bit wasteful. Maybe we should take the first N characters of the base32 encoding instead of the last N.

Code I used for the above example: https://fossil.falsifian.org/misc/file?name=src/twt_collision/find_collision.c
I only needed to compute 43394987 hashes to find it.

On my blog: Open Source Characters https://john.colagioia.net/blog/2024/08/11/open-source-characters.html #freeculture #licenses #rant

it works fine if you properly escape your urls!

 URIs include components and subcomponents that are delimited by
   characters in the "reserved" set.  These characters are called
   "reserved" because they may (or may not) be defined as delimiters by
   the generic syntax, by each scheme-specific syntax, or by the
   implementation-specific syntax of a URI's dereferencing algorithm.
   If data for a URI component would conflict with a reserved
   character's purpose as a delimiter, then the conflicting data must be
   percent-encoded before the URI is formed.

      reserved    = gen-delims / sub-delims
      gen-delims  = ":" / "/" / "?" / "#" / "[" / "]" / "@"
      sub-delims  = "!" / "$" / "&" / "'" / "(" / ")"
                  / "*" / "+" / "," / ";" / "="

@prologic@twtxt.net Yeah realised I hit the character limit lol

https://enneagram.bz/fr/types/all #writing #character building

THE ACTOR OF THE MAIN CHARACTER FROM VGHS MARRIED THE ACTRESS PLAYING HIS LOVE INTEREST

Handwritten HTML strikes again! Since June this year, I’ve been truncating the name of the month to the 1st 3 characters in my twtxt archive

Here’s the bug report, it’s very entertaining. Tony Marston is my favorite character. https://bugzilla.mozilla.org/show_bug.cgi?id=98168

Thank you Mozilla, you bloody &%$&“/§%(”). After removing the ability to switch the character encoding and replacing it with an always disabled “Repair text encoding” menu item, I had to install this third-party Override Text Encoding extension.

How Hong Kong’s redevelopment projects can be showcases of ‘organic city’ growth
The decision to bulldoze Kowloon Walled City in 1993 wasted a chance to create a cultural treasure that celebrates its history and character. Instead of cookie-cutter shopping centres and residential towers, Hong Kong needs development that evolves from the local characteristics of each district. ⌘ Read more

‘Glocalised’ school-based curriculum at Caritas Wu Cheng-chung Secondary School empowers innovation and inspires students from nearly 20 countries and regions
Caritas Wu Cheng-chung Secondary School (CWCC) embraces ‘glocalisation’ to optimise its students’ learning experience as well as their personal growth and character building. ⌘ Read more

TUIFI Manager: A file manager, in the terminal, with file icons made out of ascii characters.
Because… why not? ⌘ Read more

@prologic@prologic The immediate context was deconstructed movie characters, but I find I’m also tiring of deconstructed foods, deconstructed philosophy, deconstructed art, etc.

One year of private diary blogging
This morning I wrote my 365th diary entry. With that, I now have my first full year of daily private diary blogging complete. A milestone! The statistics tell me that’s 32245 words with 186900 characters and an average word count of 88 words per post. ⌘ Read more

This led me on quite the rabbit hole ending around this site with quite a few pages of different components of the language. https://www.bible.ca/ark/chinese/bible-evidences-chinese-language-characters-words-history-genesis.htm

all the characters in the Kullback-Leibler divergence are actually dead

Image

Pick your character! ⌘ Read more

Debunking
⌘ Read more

Telegram Ads
So Telegram now has ads. But unlike the ads from Google, Facebook or Apple, the ads are not personalized and much more privacy friendly. The ads simply consist of a maximum 160-character message with no external links and are displayed only in large public channels. ⌘ Read more

@movq@www.uninformativ.de would it be possible to trim the subject to, say, 100 or 140 characters? Just the subject.

@stackeffect@twtxt.stackeffect.de
I am seeing this characters on your twts: )?â\200¨â\200¨. Which client are you using?

@movq@www.uninformativ.de I am getting this when I run it on cron (extra lines in between becuase otherwise jenny will make them a mash):

Traceback (most recent call last):

File “/home/quark/jenny/jenny”, line 565, in

if not retrieve_all(config):

File “/home/quark/jenny/jenny”, line 373, in retrieve_all

refresh_self(config)

File “/home/quark/jenny/jenny”, line 294, in refresh_self

process_feed(config, config[‘self_nick’], config[‘self_url’], content)

File “/home/quark/jenny/jenny”, line 280, in process_feed

fp.write(mail_body)

File “/usr/lib/python3.8/encodings/iso8859_15.py”, line 19, in encode

return codecs.charmap_encode(input,self.errors,encoding_table)[0]

UnicodeEncodeError: ‘charmap’ codec can’t encode character ‘\U0001f4e3’ in position 31: character maps to

Well I’m happy to accept patches to linebanner if you’d like to add characters. :-) http://txtpunk.com/banner/index.html

Cleaned up a bit, with installation instructions for Plan 9 and p9p, tiny character tweaks, and a change log.

I wrote a ‘banner’-like program for Plan 9 (and p9p) that uses the Unicode box drawing characters: http://txtpunk.com/banner/index.html

https://www.materialui.co/unicode-characters design unicode web

http://www.netmux.com/blog/ultimate-guide-to-cracking-foreign-character-passwords-using-has cracking securité

Oh, you’ve got to be kidding me. I can get xx.xx (domain withheld) for less than I paid for mck.cx! That’s one character less!

PEOPLE DO THAT WITH A HEADLESS CHROME INSTANCE? ARE YOU KIDDING ME? WHO COULD POSSIBLY- WHY WOULD- THE- I DO NOT HAVE ENOUGH CHARACTERS.

140 characters cannot even begin to contain my problems with this blog post. https://apex.sh/blog/post/pre-render-wget/

I just want to make cute cuddly characters that sing a chitter. I don’t know how else to say this.

my tiny screen can comfortably display a text block of 45 lines with a maximum length of 79 characters. wonder what kind of information is possible to convey with that kind of information density… #halfbakedideas

@prologic@twtxt.net 36 characters left makes it rough.

I have been using Unix for 25+ years and I just learned about the status character in shells (often ^T). Huh.

The 140 character limit of the twtxt spec is annoying. I hope you got the essence of my previous post.

@vain@www.uninformativ.de the truth is, i never “got” or liked twitter. i think it’s way too noisy and a terrible way to have a conversation, what with the character limit and all. and then mastodon came along and i thought it would be different, but then it became too twitter-like. i get what you mean about twtxt and discoverability, that is one of its drawbacks.

@prologic@twtxt.net Txtnish adds a 28 character timestamp to the message, so in Bash: tweet=tail -1 the current twtxt.txt file and then pipe echo body=${tweet:28} to twt.

@prologic@twtxt.net Txtnish adds a 28 character timestamp to the message, so in Bash: tweet=tail -1 the current twtxt.txt file and then pipe echo body=${tweet:28} to twt.