I am very excited about this, and it seems like something the twtxt crowd might enjoy: https://anewsession.com/

@anth@a.9srv.net Did you work at Bell Labs, did I read correctly?

@lyse@lyse.isobeef.org What do you do at your day job?

“Designing Episode’s Interactive Fiction in Three Phases” — https://dbohdan.com/episode-interactive-fiction

The Art of Interactive Design — https://dbohdan.com/art-of-interactive-design

Behind the Curve — https://dbohdan.com/behind-the-curve

Zero to One — https://dbohdan.com/zero-to-one

Your Mommy Kills Animals — https://dbohdan.com/your-mommy-kills-animals

@prologic@twtxt.net Bug in your profile links: it’s repeating a segment. For example, your face tries to get to https://twtxt.net/user/https://twtxt.net/user/prologic/twtxt.txt

cyberpunk begins: NYPD have deployed robot dogs. Here’s a guide on how to combat them if you get robo-attacked. https://www.jwz.org/blog/2021/02/guide-to-combat-against-robot-war-dogs/

Let’s talk about a better plan for the teens at the border…. https://www.youtube.com/watch?v=HY9GkB8VUIM

Drilling into computations in the shell for the Mu computer: https://merveilles.town/@akkartik/105790894303047592

https://gamejolt.com/games/JSRFMP/336004

https://store.steampowered.com/app/1353230/Bomb_Rush_Cyberfunk/

UNDERSTAND UNDERSTAND UNDERSTAND UNDERSTAND THE CONCEPT OF LOVE💕 https://www.youtube.com/watch?v=ugo6ASPVu9g

Mulling switching gears for the Mu shell to a less ambitious Lisp-based language: https://merveilles.town/@akkartik/105771735864653468

@thewismit@twtxt.psynergy.io @jlj@twt.nfld.uk in old school terminal jargon the ^H means control H or the sequence used in some terminals to indicate backspace. The “joke” is that the term failed to interpret it correctly and you can see the partially typed word before they changed it.

WIP for a new branding and top-navn

@adi@twtxt.net @movq@www.uninformativ.de ah.. looks like you still follow movq as vain.

https://www.unicode.org/L2/L2020/20248-mayan-update.pdf

https://linguistics.berkeley.edu/sei/progress-overview.html

https://www.unicode.org/roadmaps/smp/

mm yeah newlines without unicode is much better https://github.com/jointwt/twtxt/issues/215

seems like the \u2028 approach breaks some clients, maybe i will try another way https://github.com/jointwt/twtxt/pull/166

Last year, we spent 51 days at sea during the passage from Japan to Canada, it was the hardest thing we had ever done. We kept a physical logbook of daily happenings onboard. This is that logbook, revised, and with a ton of extra notes. https://hundredrabbits.itch.io/busy-doing-nothing

https://www.aljazeera.com/opinions/2020/12/20/romani-americans-struggle-with-inherent-criminality-stereotypes

@golang_news @prologic@twtxt.net Woot!

Go 1.16 is released ⌘ Read more…

my body is ready for oberon https://people.inf.ethz.ch/wirth/ProjectOberon/PO.System.pdf

@xuu@txt.sour.is Errors are gone! 👌

@xjix@xj-ix.luxe Saw your oldish note about wanting an offline/async twtxt workflow. Do you have something that works for you? My (very young!) client was designed with that in mind.

@prologic@twtxt.net Exactly, but that reduces the argument for URLs in the post. The client should figure out how to search based on the hashtag.

@bml@twtxt.net Yup, several. My favorite is RFC 1149, another that’s since been implemented. https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for_Comments

@prologic@twtxt.net You may be interested in https://github.com/u-root/u-root (I work with a contributor).

@bml@twtxt.net It was totally an April Fools’ joke; the IETF has a bunch of those. But! It has also been implemented. And 418 is my favorite error code.

interesting RFC dated April 1st, 1998: Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0):

https://tools.ietf.org/html/rfc2324

looking at the date this was published, i think the authors originally meant this as an apil’s fool joke/prank.

funny because now we have IOTs and this is somewhat a reality today :P

@prologic@twtxt.net @anth Sounds like a good idea. The hash to conv/search url should stay local to a pod.

@prologic@twtxt.net Looks like twtxt.net is already happy with it, so that’s good! I’m just going to aim for that.

My silly Plan 9 rc twtxt client now has a web page: http://txtpunk.com/tw/index.html

@prologic@twtxt.netFor example, this should work (no idea if it does).

@prologic@twtxt.netYes, I think tags should just be #foo, and let the client figure out searching if it cares.

@lyse@lyse.isobeef.org Yes, I often read the raw messages. But more to the point, the simplicity of the format is the bulk of the appeal.

@movq@www.uninformativ.de No argument that threading is an improvement. But I think (#hash) does that, and I think figuring out how to search should mostly be up to the client.

I don’t have any issue with the (foo) subjects, it’s the proliferation of the (foo url) tags. They’re just too long and ugly.

@prologic@twtxt.net yah I’ll get a fix out soonish

@darch@twtxt.net @prologic@twtxt.net Technically it should be at the start.. Though the parser doesn’t currently care where it is. Though that leads to artifacts like any random string inside perens becoming a subject.

Tutorial - Write a Shell in C • Stephen Brennan

cc @adi@twtxt.net

@prologic@twtxt.net I’ve just never had it be a rewarding experience.

@prologic@twtxt.net rc, the Plan 9 shell.