darch@neotxt.dk

neotxt.dk

No description provided.

Recent twts from darch@neotxt.dk
In-reply-to » Good read of on the perspective of decentralize social form the common folks: https://werd.io/2023/this-moment-isnt-about-decentralization

@prologic@twtxt.net that if we want to get more people using twtxt/yarn, mastodon, ssb, matrix etc. etc. we should focus on making sure these alternative solve social problems that they understand and care about instead of just talking about the technological aspects

⤋ Read More

@kevin@oh.mg All right so the problem is that + are converted to spaces in URLs.

It would be better if you used Z instead of +00:00 in your twtxt.txt, but editing this for existing posts will break threading (which you do not seem to use anyway).

I can also try to make a fix, so +00:00 is stripped from the links.

⤋ Read More
In-reply-to » I kind of want to make a yarn.social pod, but geez, it's extensive work. I wonder how to do it with just a twtxt.txt file and then use my own domain...

@chunkimo@twtxt.net It’s not that much work to setup a pod, but selfhosting your twtxt.txt is easier, but then you will be lacking a UI for reading and posting.

I’m self-hosting this feed and displaying it on my site and got a post and image upload feature going using my own php-tools. You can learn more about it on http://darch.dk/social

There are also terminal base solicitous, such as @movq@www.uninformativ.de’s jenny and @lyse@lyse.isobeef.org’s tt

⤋ Read More
In-reply-to » An idea for helping humans and machines understand when a twtxt-feed are using some of the yarn.social extensions by applying a mix of a hash-bang and a DTD to the first line of the txt-file:

@prologic@twtxt.net Come to think about it, I’m more in favor of @lyse@lyse.isobeef.org ’s approach; Make it human readable with relevant links and not do anything specific for the machines. This is almost already the case for twtxt.txt served by yarnd, we just need to add a line to the Yarn.social section explaining about the extensions.

⤋ Read More

Ah, I what the problem is now: You are using +00:00 instead of Z in the end of the datetime. I’m sure +00:00 can be supported as well as Z, but if you are up for it take a look at the source code if you are not allergenic to PHP

⤋ Read More

An idea for helping humans and machines understand when a twtxt-feed are using some of the yarn.social extensions by applying a mix of a hash-bang and a DTD to the first line of the txt-file:

#! DOCTYPE = twtxt (https://twtxt.readthedocs.io) with extension for multi-line and conversation treading from Yarn.social (https://dev.twtxt.net)

It would be nice if the link to the extension could be to dev.yarn.social, docs.yarn.social or similar instead of dev.twtxt.net to make it less confusing.

⤋ Read More

All art is a lie. But the art-ifical can point our attention and experience towards (a/the?) truth which cannot been seen or heard in the natural world

⤋ Read More
In-reply-to » 👋 Q: How do we feel about forking the Twtxt spec into what we love and use today in Yarn.social in yarnd, tt, jenny, twtr and other clients? 🤔 Thinking about (and talking with @xuu on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or "Yarn". Compatibility would remain with Twtxt in the sense that we wouldn't break anything per se, but we'd divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don't use, contribute in the first place or fixate on nostalgia (which doesn't really help anyone).

The “problem” as I see it is not technical, but social, so we should try to approach solving it according.

⤋ Read More
In-reply-to » 👋 Q: How do we feel about forking the Twtxt spec into what we love and use today in Yarn.social in yarnd, tt, jenny, twtr and other clients? 🤔 Thinking about (and talking with @xuu on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or "Yarn". Compatibility would remain with Twtxt in the sense that we wouldn't break anything per se, but we'd divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don't use, contribute in the first place or fixate on nostalgia (which doesn't really help anyone).

I’m with @abucci@anthony.buc.ci here. Let’s enjoy our freedom to listen i.e. not pay too much attention to people how argue for the sake of arguing.

A way around their criticism choud be to put a disclaimer in our twtxt.txts stating that this feed uses features that might not be compatible with some clients. Like the old “Best viewed in Netscape”-icons

⤋ Read More
In-reply-to » 💡 Quick 'n Dirty prototype Yarn.social protocol/spec:

@prologic@twtxt.net Having to deal with json and cryptography is not very appealing to me. It’s the simplicity and hackability of twtxt.txt that I’m drawn by. That you can in fact handwrite your posts and you can throw pretty much anything at it after the datetime+tab and it still being somewhat human readable and work in most clients. If you do something that a client does not like, then you will have to take up the debate with the devs or make your own. And if people like some features that you invented, then your new client might get more users, or your end up doing something just or for yourself.

⤋ Read More
In-reply-to » I don't buy jan6's premise that twts with markdown and image links is hard to read. Markdown came out of how people simulated typeset text in plain text and the URL part of links to images and others resources are also easy for humans to read and parse.

@prologic@twtxt.net Also considering the original tagline of twtxt:

twtxt is a decentralised, minimalist microblogging service for hackers.

if a hacker can’t handle some markdown and urls in their microblogging, then user != hacker

⤋ Read More
In-reply-to » Given the continued hostility of jam6 and buckket over Yarn'a use of Twtxt (even after several years! 😱) I am continuing to face hard decisions.

I don’t buy jan6’s premise that twts with markdown and image links is hard to read. Markdown came out of how people simulated typeset text in plain text and the URL part of links to images and others resources are also easy for humans to read and parse.

Multi-line is another matter, but I also never used the original client. I guess it could have been implemented in a was that would not break other clients. Using something like -- or just two space at the end of a line like in markdown would also work.

⤋ Read More
In-reply-to » @prologic maybe this will work: https://github.com/pfefferle/wordpress-twtxt

@shreyan@twtxt.net Got it working now – just needed to figure out the right URL: http://darch.dk/wp-test/twtxt

  1. Download zip from https://github.com/pfefferle/wordpress-twtxt/archive/refs/heads/master.zip
  2. Unzip it and rename the folder from wordpress-twtxt-master to just twtxt
  3. Log in via FTP and upload the twtxt folder to: wp-content/plugins/
  4. Go to http://example.com/wp-admin/plugins.php and activate the plugin
  5. Wait a bit or swap themes to get it to render the twtxt feed
  6. Access the twtxt file via this URL: http://example.com/twtxt (no .txt!)

⤋ Read More
In-reply-to » Anyone know of any good, cheap laptops to use for just day-to-day activities (web surfing, sysadmin, web design, etc) that’s not a Chromebook? My Microsoft Surface Go I got some years ago blue screens when I plug it into my dock.

What about a PineBook or PineTab with a keybord: https://pine64.com

⤋ Read More
In-reply-to » NetNewsWire has been working out pretty well as my primary news source over the last couple days. I'm kind of grossed out by just how much I relied on Twitter in that role over the last several years.

@axodys@octobloc.xyz I’m also a happy user of NetNewsWire in combinations with self-hosted FreshRSS as a backed to sync to other devices besides my Mac. And migrating my YouTube subscriptions to RSS is such a nicer experiance than being locking into the dark design patterns of YouTube’s web UI.

⤋ Read More