A guy on the internet.

Block / Report User

If this user/feed is violating this Pod's ( community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

@mckinley does not follow you (they may not see your replies!)

Recent Twts

Recent twts from mckinley

How many forks deep is this Bitcoin conversation?

As said:

Step 1, someone builds something which doesn’t support a “reply” feature at all. Step 2, the thing grows, now people want “reply”. Step 3, it gets confusing with all the linear replies and now people want “full threading”. That’s also basically what happened to twtxt/yarn. Maybe, over time, everything evolves into Usenet., step 3 when? :)


(#skbye2a) If a government bans the currency, it wouldn’t have a hope of being enforced unless they could make all the internet service providers enforce a domain whitelist. Not a blacklist like the Great Firewall of China.

The GFW also does deep packet inspection, and perhaps that could be used (likely on a per-currency basis) to limit the access of nodes, but that can be circumvented with Tor bridges.

The government could cut off a country from the Internet like you said, but then you have bigger problems than your favorite internet currency being unusable. Even then, there would still be ways around it.


(#wql4w5q) 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.


(#wql4w5q) I don’t think the solution proposed there is a good one, and here are my reasons.

  1. 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.

  2. 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.

  3. 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.


(#64wq5na) Yes, I’ve been thinking of writing a new, unambiguous version of the original spec with some small changes to bring it in line with how feeds are actually being constructed in the wild. The comment syntax, for example, but not the Yarn extensions.

Is there community interest for such a thing?


(#wzwth7a) Outside of this thread, this comment syntax has been used exactly twice when searching every known, currently accessible twtxt feed on the Web.

$ grep -r '@<[^ ]*>'	Hey @<>, @<teddy> und was geht? Ich bin’s!
[...]	@ twtxt via DNS TXT would be insane and fun.


(#luy6xva) Here are the top ten feeds by size. is artificially low on the list because it’s separated into chunks, and is listed twice. Once as, once as I blame yarnd.

du -b * | sort -nr | head -n 10
842733	cnbeta-com-rssding-yue.txt
654717	prologic.txt
394380	jlj.txt
371632	assets.txt
246520	off_grid_living.txt
243953	mckinley.txt

cnbeta-com-rssding-yue.txt seems to be a syndication feed for in twtxt format, assets.txt is, and the rest are fairly self-explanatory.


(#vfxgqmq) I think there is value in cryptocurrencies as long as they have sufficient privacy protections. If you have someone’s Bitcoin or Ethereum address, you can see every transaction he’s ever been involved in. Not enough people know that.

The value is in being able to send a scarce resource to anyone on the planet, any time of the day, any day of the week, and have it received in 20 minutes. As long as privacy is preserved, I think it’s great.

It’s completely useless in the context of a chat service, though. The blockchain nonsense was part of the reason why I ditched Session, but it was mostly the Electron client.


(#zdoe7hq) It is not a tough dilemma for me. A government has no right to perform mass surveillance on its citizens, treating everyone as if they were criminals. It starts with something we can all agree is reprehensible, and they say it stops there, but history tells us it never just stops there.

In addition, computers are really bad at their jobs. How many innocent people will be punished with a false positive? How many mothers will be punished for sending a photo of their newborn to the doctor?

I’m talking about punishment not only in the legal sense, but with the time, money, and worry associated with fighting legal punishment. Do you even trust your legal system enough that it will protect innocent people in these circumstances from having their lives ruined?

There are questions to be raised about the effectiveness of such a policy for its intended purpose but I’m running out of characters.


(#vfxgqmq) It’s proof of stake, so you need to stake 15,000 units of their cryptocurrency $OXEN, worth $3118 US, to run a “full service node” and 3750 $OXEN ($779 US) to run a “shared node”. If I understand correctly, only “full service nodes” can route Session messages.

If you don’t have enough $OXEN, you can pool what you do have with other people and run a node that way.

TL;DR: Not very easy. To help route Session messages at all, you have to buy in to their cryptocurrency.