Interview with an NFT enthusiast - YouTube – Bahahahahahahaha 🤣 #NFT
Got an acknowledgement of our Salty.im funding proposal to NLnet this evening. I look forward to the outcome 🤞 #Salty.im
pondering about the difference between my use of the tags #idea and #halfbaked . halfbaked looks like something in a more advanced stage, merely lacking execution #meta
Does anyone of you use PGP encrypted mail, or any kind or email encryption? Why? Why not?
#Wordle 235 4/6*
⬛🟨🟨⬛⬛
🟨🟨⬛⬛⬛
⬛⬛🟨🟨🟩
🟩🟩🟩🟩🟩
Finally! 😂
@eldersnake@yarn.andrewjvpowell.com There isn’t an equivalent for those because:
Markdown is not a replacement for HTML, or even close to it. Its syntax is very small, corresponding only to a very small subset of HTML tags.
You can read more of its philosophy at Daring Fireball. There are enhancements to Markdown (CommonMark, for example), that add extra to it.
@adi@f.adi.onl Yes, it did—at least I don’t see the same issue as before on twtxt.net. Weird, as it was never an issue on other pods. 🤷🏻♂️
@fastidious@arrakis.netbros.com Hmm… the empty line needs to be left alone.
@prologic@twtxt.net should we enable all unicode glyphs for tags? https://txt.sour.is/conv/55yrura
@xuu@txt.sour.is Is this of any use? https://libretranslate.com/ – Congrats on the new job!
@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 I’ve just never had it be a rewarding experience.
@prologic@twtxt.net rc, the Plan 9 shell.
Hey @xuu@txt.sour.is another mention that didn’t render ☝️
@thewismit@twtxt.psynergy.io Hey! It’s easy. Just install the twt
CLI with something like:
go get github.com/jointwt/twtxt/cmd/twt/...
Then use it in some hooks/scripts to post some content to your Pod.
@prologic@twtxt.net speaking of complexity.. How would checking twts for sub conversations complexify things?
but if we kept things simple stupid I how would the poor little darlings in middle-management have a job? 😂
@xuu@txt.sour.is Speak of lang… Do you think we could detect the user’s lang by what they write? Probably just inspect a random subset?
💁♂️ If you’re ever on a UNIX machine of some kind without any useful networking utilities like ip
or ifconfig
, fear now! You can view the network topology of the Kernel by just doing:
cat /proc/net/fib_trie
@prologic@twtxt.net yep. it actually extracts everything at parse time. like mentions/tags/links/media. so they can be accessed and manipulated without additional parsing. it can then be output as MarkDown
@prologic@twtxt.net as promised! https://github.com/JonLundy/twtxt/blob/xuu/integrate-lextwt/types/lextwt/lextwt_test.go#
the lexer is nearing completion.. the tough part left is rooting out all the formatting code.
@oevl@twtxt.net @prologic@twtxt.net (#) for the most part a subject is just the content in the perens. Usually it’s a tag. It appears near the start after any mentions. It can also contain text like (re: subjects)
@deadguy @prologic@twtxt.net been stewing on a discovery proto for twtxt. support for defining multiple ways to host/mirror a twtxt file. while being low tech enough to still be scriptable with basic Unix commands.
@prologic@twtxt.net (#keh22ka) maybe a custom linking method on a pod level? like can pass a template that gets translated. ex https://{domain}/wiki/{nick}/{tag}
+ !somepage
-> https://sour.is/wiki/xuu/somepage
@prologic@twtxt.net do you have any info on how the ‘!’ tags are supposed to work? are they just a different kind of hash tag?
@prologic@twtxt.net I have some ideas to improve on twtxt. figure I can contribute some. 😁 bit more work and it will almost be a drop in replacement for ParseFile
Kinda wish types.Twt was an interface. it’s sooo close.
@xuu@txt.sour.is Not too happy with WKD’s use of CNAME over SRV for discovery of openpgpkey.. That breaks using SNI pretty quick. I suppose it was setup as a temporary workaround anyhow in the RFC..
Building docker image with name and tag …
@reednj@twtxt.xyz Thanks for making and hosting http://twtxt.xyz - the agreggation of twtxts users, tweets and tags is really cool