A guy on the internet. https://mckinley.cc/
A guy on the internet. https://mckinley.cc/
Testing something… @@example.com
@email@example.com 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.
@firstname.lastname@example.org 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.
@email@example.com 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.
@firstname.lastname@example.org The specification just says:
Also note that a status may not contain any control characters.
Which is extremely vague, but U+0009 Horizontal Tabulation is in the C0 control code block
I’m sure 99% of twtxt parsers don’t treat additional tabs any differently. Even Buckket’s reference implementation includes additional tabs in the message. Although, in fairness, it doesn’t check for any for control codes.
Maybe we need a less ambiguous specification documenting how twtxt feeds are being written in the wild. Did you know that the comment convention is not a part of the original spec? I feel like it’s used everywhere, even among feeds that don’t use any Yarn extensions.
I’m sorry, I didn’t explain this properly and that has led to a misunderstanding of my actual proposal. I was not intending for the title to be a special field unless the client explicitly understood my syndication format.
The original twtxt format specification gives no special meaning to the tab character, excluding the one that separates the timestamp from the text. I was under the impression that the tab character could appear in a twt so it would be interpreted as follows, replacing ␉ with a tab character.
2022-09-22T14:53:26-07:00␉Bringing Back a Useful Browser Feature With a Bookmarklet␉https://mckinley.cc/blog/20220922.html #^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ #| | # ```- Timestamp `- Message
Although, I just remembered that the tab character is technically a control code, so it shouldn’t be allowed.
@email@example.com I wasn’t making a criticism, I was just pointing out the difference in the format. I agree, there’s some great stuff on there.
$ nc kyoko-project.wer.ee 1234 in your terminal, it’s a remake of Among Us as a multiplayer text adventure.
@firstname.lastname@example.org Referenced links also work on the Web client, but I tried both CommonMark syntax options for the horizontal rule and only one worked on Goryon.
This is exactly what I’m talking about. We should have a concrete specification so Markdown can be rendered consistently between client implementations.
I think I broke it, though, because I started a game alone and then accidentally pressed ctrl+c. When I try to log back in, it says there’s a game in progress and I can’t start a new one. Sorry about that…