"Problems are Solved by Method" 🇦🇺👨💻👨🦯🏹♔ 🏓⚯ 👨👩👧👧🛥 -- James Mills (author of twtxt.net)
Block / Report User
If this user/feed is violating this Pod's (twtxt.net) 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.
@prologic does not follow you (they may not see your replies!)
Recent twts from prologic
@email@example.com (#eymhvia) Hmmm I’ve been working on trying to remove the need to fully qualify tag URIs on this client/platform. But what you’ve just done makes me wonder whether we could/should add a
twtxt2html command-line tool reusing all the parsing, Markdown and HTML handling we’ve already worked quite hard at, including all the extensions we built on top of twtxt (all backwards compatible). Hmm? 🤔 Would you use it? 😀
@jimjim Hey there! 👋 Welcome! 🤗
Channels that I was on are all gone, my own account was dropped apparently so is everyone else’s and my channel all gone to! 😳
@wisdommaterials Hello! 👋 Welcome! 🤗
Goodbye FreeNode. 👋 – This might very well be goodbye in general to IRC for me after 18 long years of being on FreeNode and actively using IRC. 😢
starting to wonder whether I should put some things up for sale as NFTs 😂
18 years I’ve been on FreeNode!
Yes you may post whatever you like 😁 (As long as it complies with the abuse policy 🤣 — Basically don’t harass, abuse others or do anything that might be considered illegal in your country!)
@anvis Hello! 👋 Welcome to my pod! 🤗
(#oyt6lzq) This was really interesting to watch! 👌 Thanks for sharing 🤗 Brought back some memories there 🤣
@firstname.lastname@example.org (#nj3rtxa) As @email@example.com correctly points out, the timestamp is a RFC 3339 formatted datetime. The only valid way to parse timestamps and append them to a feed is RFC 3339 😀 – Doing anything else otherwise would be both invalid, weird and well just not following a standard (what’s a standard for?!) 🤣
(#lwyx7aq) @firstname.lastname@example.org Pretty sure I also have the “Celestron Ultima 100” spotting scope! I use it often as it’s quick and rough :D I need to buy GPS modules for my Celestron Nextstar 4SE so it is just “automatic” 🤣
l redo it to actually change the job schedule 👌
@email@example.com Hey 👋 One more thing you could consider… If you add an
avatar.png next to your
twtxt.txt feed and host it along-side the same root path things like https://twtxt.net (and other pods) will fetch and display your avatar instead of a generic one :)
(#jro3wba) @darch Sure! No worries I get it. Time/Energy is hard to come by when you have a full-time job, family, other activities, etc. That’s not to say that this project doesn’t see any time/effort, it does, just more slowly at the moment.
Share your ideas, I’m very curious 🙇♂️
And preserving the hash in a regular client is a hassle.
Why? Just write (#ekceh3q) – It’s pretty easy. Depending on the client you’re using maybe you could add the feature? We are probably going to drop the full URI and just stick to the hash itself in plain text.
(#g3th6hq) But also so I can decouple pods and
twtd from having C-level dependencies and break out any “media handling / serving” to a separate thing that can scale indepently.
image/jpeg support. Originally I designed the image processing to only really support WebP and PNG, WebP if possible and a fallback to PNG. In hindsight maybe JPEG should be supported oto? It wouldn’t take a lot of extra processing to handle this.
In an ideal world, I’d refactor the code entirely into a separate service that accepts an image upload, returns a unique URI for the resource and does the processing in the background. So that the user experience is quicker and more fluid…
How did you take this?