Searching yarn

Twts matching #reading:
Sort by: Newest, Oldest, Most Relevant
In-reply-to » I'm closing down neotxt.dk as a yarn pod. It will instead offer hosting of timeline or what ever other php stuff you want to run. To get started send me a poem to poem@neotxt.dk

@bender@twtxt.net ha! He goes his โ€œpoemโ€:

A string of letters, a forgotten name,
An email crafted, a message to claim.
We hit send with a click, a hopeful sigh,
But a bounce-back arrives, a tear in our eye.

โ€œDelivery failed,โ€ the message reads cold,
The address it seems, is a story untold.
A ghost in the system, a memoryโ€™s trace,
Lost in the void of cyberspace.

:-D

โค‹ Read More

More basement:

I completely forgot that DVD-RAM was a thing once. Found my old disks and they still work. ๐Ÿคฏ The data on them is from 2008, so theyโ€™re not that old. Still impressive.

The disks are two-sided. On the photo, that particular side of the disk on the left appears to be completely unused. ๐Ÿค”

And then I read on Wikipedia that DVD-RAMs arenโ€™t produced anymore at all today. Huh.

(I refuse to tag this as โ€œretrocomputingโ€. Read/write DVDs that you can use just like a harddisk, thanks to UDF, are still โ€œnew and fancyโ€ in my book. ๐Ÿ˜‚)

โค‹ Read More
In-reply-to » Also made a webfinger lookup resolver that works with my own webfinger endpoint as well as yarnd servers: http://darch.dk/wf-lookup.php Media Media

Thanks @prologic@twtxt.net, I also just manage to get my own version of webmentions working. Please have a read at Webmentions vs. Custom Mentions Spec for Twtxt/Yarn - HedgeDoc and User Lookup for Twtxt/Yarn - Webfinger or Decentralized Identifiers (DIDs) - HedgeDoc for how it sorta works

โค‹ Read More

Somewhere I read that changing location, like entering a room, can rejigger neural pathways so that some thoughts and memories are somehow associated with the space. Itโ€™s the same for me when picking up a laptop. My purpose feels clear until I open a blank web browser window and my mind goes blank, too. In all the moments where Iโ€™m drawing a total blank, and then suddenly the thoughts come easily again: maybe thatโ€™s my brain looking for the room it was in before.

โค‹ Read More
In-reply-to » Question of the day: What configuration file formats do you all like and use?

Yeah, the lack of comments makes regular JSON not a good configuration format in my view. Also, putting all keys in quotes and the use of commas is annoying. The big upside is thatโ€™s in lots of standard libraries.

I think the appeal with YAML is that is has comments, is kind of easy to write and read and also provides unlimited nesting levels. But it has all its drawbacks, no question. Forbidding tabs, thousands of different string flavors, having so many boolean options (poor Norwegians) etc. I use it, but I donโ€™t particularly enjoy it.

Among simple key value pairs, I like INI files, but with # for comments, not ;. I never used TOML, read up on it yesteray before writing this question, but it looks a bit weird and has some strange rules. I guess I have to give it a try one day.

And yes, as mentioned by several of you, it always depends on the complexity of the configuration at hand.

Iโ€™m developing something for the scouts at the moment with rather simple requirements on the config. Currently, there are just four settings. Even INI would be overkill with its section. I selected JSON for now, because thatโ€™s readily available with Goโ€™s std lib. But I do not like it.

Btw. whatโ€™s your own config format, @xuu@txt.sour.is?

โค‹ Read More

Linus Torvalds Has โ€˜Robust Exchangesโ€™ Over Filesystem Suggestion on Linux Kernel Mailing List
Linus Torvalds had โ€œsome robust exchangesโ€ on the Linux kernel mailing list with a contributor from Google. The subject was inodes, notes the Register, โ€œwhich as Red Hat puts it are each โ€˜a unique identifier for a specific piece of metadata on a given filesystem.โ€™โ€

Inodes have been the subj โ€ฆ โŒ˜ Read more

โค‹ Read More
In-reply-to » (#fytbg6a) What about using the blockquote format with > ?

@sorenpeter@darch.dk this makes sense as a quote twt that references a direct URL. If we go back to how it developed on twitter originally it was RT @nick: original text because it contained the original text the twitter algorithm would boost that text into trending.

i like the format (#hash) @<nick url> > "Quoted text"\nThen a comment
as it preserves the human read able. and has the hash for linking to the yarn. The comment part could be optional for just boosting the twt.

The only issue i think i would have would be that that yarn could then become a mess of repeated quotes. Unless the client knows to interpret them as multiple users have reposted/boosted the thread.

The format is also how iphone does reactions to SMS messages with +number liked: original SMS

โค‹ Read More