While we're on the subject, here's a great video I found showing Microsoft's efforts to push you into using Edge.
* Original 720p H.264/AAC [93.8 MiB][93.8 MiB=] [Most compatible][Most compatible=]
* 720p H.265/AAC [33.1 MiB][33.1 MiB=] [Least compatible][Least compatible=]
* 480p VP9/Opus [36.4 MiB][36.4 MiB=] [Probably compatible][Probably compatible=]*
While we're on the subject, here's a great video I found showing Microsoft's efforts to push you into using Edge.
* Original 720p H.264/AAC \n\n\n\n \n\n\n\n
* 720p H.265/AAC \n\n\n\n \n\n\n\n
* 480p VP9/Opus \n\n\n\n \n\n\n\n*
While we're on the subject, here's a great video I found showing Microsoft's efforts to push you into using Edge.
* Original 720p H.264/AAC [93.8 MiB][93.8 MiB=][93.8 MiB][93.8 MiB=][93.8 MiB][93.8 MiB=][93.8 MiB][93.8 MiB=] [Most compatible][Most compatible=][Most compatible][Most compatible=][Most compatible][Most compatible=][Most compatible][Most compatible=]
* 720p H.265/AAC [33.1 MiB][33.1 MiB=][33.1 MiB][33.1 MiB=][33.1 MiB][33.1 MiB=][33.1 MiB][33.1 MiB=] [Least compatible][Least compatible=][Least compatible][Least compatible=][Least compatible][Least compatible=][Least compatible][Least compatible=]
* 480p VP9/Opus [36.4 MiB][36.4 MiB=][36.4 MiB][36.4 MiB=][36.4 MiB][36.4 MiB=][36.4 MiB][36.4 MiB=] [Probably compatible][Probably compatible=][Probably compatible][Probably compatible=][Probably compatible][Probably compatible=][Probably compatible][Probably compatible=]*
While we're on the subject, here's a great video I found showing Microsoft's efforts to push you into using Edge.
* Original 720p H.264/AAC [93.8 MiB][93.8 MiB][93.8 MiB][93.8 MiB][93.8 MiB][93.8 MiB][93.8 MiB][93.8 MiB] [Most compatible][Most compatible][Most compatible][Most compatible][Most compatible][Most compatible][Most compatible][Most compatible]
* 720p H.265/AAC [33.1 MiB][33.1 MiB][33.1 MiB][33.1 MiB][33.1 MiB][33.1 MiB][33.1 MiB][33.1 MiB] [Least compatible][Least compatible][Least compatible][Least compatible][Least compatible][Least compatible][Least compatible][Least compatible]
* 480p VP9/Opus [36.4 MiB][36.4 MiB][36.4 MiB][36.4 MiB][36.4 MiB][36.4 MiB][36.4 MiB][36.4 MiB] [Probably compatible][Probably compatible][Probably compatible][Probably compatible][Probably compatible][Probably compatible][Probably compatible][Probably compatible]*
While we're on the subject, here's a great video I found showing Microsoft's efforts to push you into using Edge.
* Original 720p H.264/AAC [93.8 MiB] (Most compatible)
* 720p H.265/AAC [33.1 MiB] (Least compatible)
* 480p VP9/Opus [36.4 MiB] (Probably compatible)*
While we're on the subject, here's a great video I found showing Microsoft's efforts to push you into using Edge.
* Original 720p H.264/AAC \n\n\n\n\n\n\n\n \n\n\n\n\n\n\n\n
* 720p H.265/AAC \n\n\n\n\n\n\n\n \n\n\n\n\n\n\n\n
* 480p VP9/Opus \n\n\n\n\n\n\n\n \n\n\n\n\n\n\n\n*
While we're on the subject, here's a great video I found showing Microsoft's efforts to push you into using Edge.
* Original 720p H.264/AAC [93.8 MiB]\n[93.8 MiB]\n[93.8 MiB]\n[93.8 MiB]\n [Most compatible]\n[Most compatible]\n[Most compatible]\n[Most compatible]\n
* 720p H.265/AAC [33.1 MiB]\n[33.1 MiB]\n[33.1 MiB]\n[33.1 MiB]\n [Least compatible]\n[Least compatible]\n[Least compatible]\n[Least compatible]\n
* 480p VP9/Opus [36.4 MiB]\n[36.4 MiB]\n[36.4 MiB]\n[36.4 MiB]\n [Probably compatible]\n[Probably compatible]\n[Probably compatible]\n[Probably compatible]\n*
While we're on the subject, here's a great video I found showing Microsoft's efforts to push you into using Edge.
* Original 720p H.264/AAC \n\n \n\n
* 720p H.265/AAC \n\n \n\n
* 480p VP9/Opus \n\n \n\n*
While we're on the subject, here's a great video I found showing Microsoft's efforts to push you into using Edge.
* Original 720p H.264/AAC [93.8 MiB] [Most compatible]
* 720p H.265/AAC [33.1 MiB] [Least compatible]
* 480p VP9/Opus [36.4 MiB] [Probably compatible]*
I think the more likely explanation is that Putin let Snowden stay to rub it in our face and recently gave him citizenship for the same reason. Anything is possible, though.
I wouldn't mind this *so* much, but you can't register an account unless you're using an approved IP address.
Some things we talked about this fine evening:
* Post deletion on yarnd
* Search functionality for yarnd
* @tkanos dropped by to say hello and showed us his strange hotel room
* How much it would cost to run the Mills DC in The Cloud (A lot)
* The Kagi search engine
* Goldbacks
* Datasette, an extensible database explorer*
> Personally I think that if a discussion is alive posts will be there, I don’t really mind if an old post/page lose its comments.
I disagree with that. I always enjoy reading what people have to say about blog posts, and it's not uncommon for comments to be months or even years apart. Discussion doesn't have to be "alive" for a comment to be worth reading.
As @movq 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.
@prologic, step 3 when? :)
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.
* The twtxt specification rewrite I'm working on
* @ocdtrekkie's work on tube
* Electron \\*shudder\\*
* JSON Feeds
* GitHub forking mysteries*
* The twtxt specification rewrite I'm working on
* @ocdtrekkie's work on tube
* Electron \*shudder\*
* JSON Feeds
* GitHub forking mysteries*
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.
@darch, I think that specific line had a use as a visual separator between the non-interactive text and the interactive buttons, but it's not a hill I'm willing to die on.
Is there community interest for such a thing?
$ grep -r '@<[^ ]*>'
buckket.org.txt:2016-02-12T18:37:00+01:00 Hey @<http://vigintitres.eu/twtxt.txt>, @<teddy https://data.trafficking.agency/twtxt.txt> und @Jim@example.org was geht? Ich bin’s @GEHEIM@buckket.org!
[...]
hecanjog.com.txt:2020-09-03T17:36:00-05:00 @https://tilde.town/~lucidiot/twtxt.tx@ twtxt via DNS TXT would be insane and fun.
$ grep -r '@<[^ ]*>'
buckket.org.txt:2016-02-12T18:37:00+01:00\tHey @<http://vigintitres.eu/twtxt.txt>, @<teddy https://data.trafficking.agency/twtxt.txt> und @<Jim http://example.org> was geht? Ich bin’s @<GEHEIM https://buckket.org/twtxt.txt>!
[the uses in this thread]
hecanjog.com.txt:2020-09-03T17:36:00-05:00\t@<https://tilde.town/~lucidiot/twtxt.txt> twtxt via DNS TXT would be insane and fun.
$ grep -r '@<[^ ]*>'
buckket.org.txt:2016-02-12T18:37:00+01:00\tHey @<http://vigintitres.eu/twtxt.txt>, @<teddy https://data.trafficking.agency/twtxt.txt> und @Jim@example.org was geht? Ich bin’s @GEHEIM@buckket.org!
[...]
hecanjog.com.txt:2020-09-03T17:36:00-05:00\t@https://tilde.town/~lucidiot/twtxt.tx@ twtxt via DNS TXT would be insane and fun.
$ grep -r '@[^@'
buckket.org.txt:2016-02-12T18:37:00+01:00\tHey @<http://vigintitres.eu/twtxt.txt>, @<teddy https://data.trafficking.agency/twtxt.txt> und @Jim@example.org was geht? Ich bin’s @GEHEIM@buckket.org!
[...]
hecanjog.com.txt:2020-09-03T17:36:00-05:00\t@https://tilde.town/~lucidiot/twtxt.tx@ twtxt via DNS TXT would be insane and fun.
du -b * | sort -nr | head -n 10
5253921\twww.lord-enki.net.txt
842733\tcnbeta-com-rssding-yue.txt
755925\tsearch.twtxt.net.txt
654717\tprologic.txt
394380\tjlj.txt
371632\tassets.txt
246520\toff_grid_living.txt
243953\tmckinley.txt
225256\twww.uninformativ.de.txt
225256\tuninformativ.de.txt
cnbeta-com-rssding-yue.txt seems to be a syndication feed for https://cnbeta.com/ in twtxt format, assets.txt is @maya, and the rest are fairly self-explanatory.
du -b * | sort -nr | head -n 10
5253921 www.lord-enki.net.txt
842733 cnbeta-com-rssding-yue.txt
755925 search.twtxt.net.txt
654717 prologic.txt
394380 jlj.txt
371632 assets.txt
246520 off_grid_living.txt
243953 mckinley.txt
225256 www.uninformativ.de.txt
225256 uninformativ.de.txt
cnbeta-com-rssding-yue.txt seems to be a syndication feed for https://cnbeta.com/ in twtxt format, assets.txt is @maya, and the rest are fairly self-explanatory.
> Mentions are embedded within the text in either
@source.nick@ or @source.ur@ format and should be expanded by the client, when rendering the tweets.cc @movq @lyse
> Mentions are embedded within the text in either
@<source.nick source.url> or @<source.url> format and should be expanded by the client, when rendering the tweets.
> Mentions are embedded within the text in either
@<source.nick source.url> or @<source.url> format and should be expanded by the client, when rendering the tweets.cc @movq @lyse
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.
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.
https://puri.sm/posts/internet-of-snitches/
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.
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.
https://loki.network/service-nodes/
https://imaginary.stream/sn/
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.
Sources:
* https://loki.network/service-nodes/
* https://imaginary.stream/sn/
> 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.
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
#^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
#| |
# age
Although, I just remembered that the tab character is technically a control code, so it shouldn't be allowed.
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
#^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
#| |
# age
Although, I just remembered that the tab character is technically a control code, so it shouldn't be allowed in
$ nc kyoko-project.wer.ee 1234 in your terminal, it's a remake of Among Us as a multiplayer text adventure.
This is exactly what I'm talking about. We should have a concrete specification so Markdown can be rendered consistently between client implementations.
[My website][1]
![An image on my website][2]
[1]: https://mckinley.cc/
[2]: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
[My website][My website][My website][My website][My website][My website][My website][My website][1][1][1][1][1][1][1][1]
![An image on my website][2]
[1][1][1][1][1][1][1][1]: https://mckinley.cc/
[2][2][2][2][2][2][2][2]: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
[My website]\n[My website]\n[My website]\n[My website]\n[1]\n[1]\n[1]\n[1]\n
![An image on my website][2]
[1]\n[1]\n[1]\n[1]\n: https://mckinley.cc/
[2]\n[2]\n[2]\n[2]\n: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
\n\n\n\n
![An image on my website][2]
\n\n: https://mckinley.cc/
\n\n: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
\n\n\n\n\n\n\n\n
![An image on my website][2]
\n\n\n\n: https://mckinley.cc/
\n\n\n\n: https://mckinley.cc/img/ladybird-yarn-20220924-2.png