¿Me das mimos?
#catsoftwtxt

What do we think? ==> https://prologic.dev/

No te quito el ojo
#catsoftwtxt

#catsoftwtxt

@andros@twtxt.andros.dev nos comparte su artículo “twtxt, la red social en texto plano, descentralizada y minimalista”

• ¡Feliz navidad! -
  #catsoftwtxt

Gato bola 2: ahora la cosa se pone negra
#catsoftwtxt

@andros@twtxt.andros.dev Hello!

I’ve started a draft over at: https://git.mills.io/yarnsocial/twtxt.dev/src/branch/main/exts/webfinger.md

@prologic@twtxt.net maybe you meant to specify twtxt as a type similar to ActivityPub’s application/activity+json in https://webfinger.net/lookup/?resource=sorenpeter@norrebro.space

    {
      "rel": "self",
      "type": "application/activity+json",
      "href": "https://norrebro.space/users/sorenpeter"
    },

Then it would also make sense to define a Link Relations but should that then link to something like https://twtxt.dev/webfinger.html where we can describe the spec?

-¡Muy buenos días a todos los felinos! Son las 5 am y arrancamos con otra edición de recordar el desayuno a nuestros dueños.-
#catsoftwtxt

also, about twtxt … https://twtxt.dev/

@eapl.me@eapl.me you could use the tw.txt as your primary url and keep the old one as a secondary for a while (maybe even do the opposite) maybe even create the new tw.txt file and make use of the prev metadata pointing at the old … 🤷

# nick = eapl.me
# url = https://eapl.me/tw.txt
# url = https://eapl.me/twtxt.txt

or …

# url = https://eapl.me/tw.txt
# prev = https://eapl.me/twtxt.txt

-¡Se ha caído la pelota al suelo! Yo te salvaré.-
#catsoftwtxt

#catsoftwtxt

#catsoftwtxt

@bender@twtxt.net 😆 Would calling it a Single user Twtxt "Yarn Pod **Like**" software help you sleep better at night? And just in case things are not clear here, I’m being sarcastic (well, kinda…) and not trying to gaslight anyone. Think of my comment as Bromance or something like that LOL.

But seriously, Just like any UNIX-Like system to Unix™, as in non of them are UNIX™, but each of them is providing more or less similar experience and re-implementing what once was parts of “UNIX™ software” their own (more or less better) ways. Timeline is Yarn™ Pod like, (my personal take on the word pod is: “an instance of XYZ software acting an escape POD from X-BS for… ABC reasons.”) providing more or less of a similar experience, implementing some of Yarn.social Extensions, trying to add in some more …etc.

Otherwise, I don’t see the Yarn pod mention as some kind of malicious manoeuvre, but more of a tribute to what (might have) sparked inspiration for creating Timeline? Also, our friend @sorenpeter@darch.dk here has got a valid reason for using PHP (#tms7aka) so let’s let’s put our unease towards the language itself aside and maybe just help however/as much as we can in order to make internet (the World?) a better place.

but for real, i really want that sword and I’m perfectly content running my daily dev stuff using an rpi. i actually used to do client work on an old rpi laptop kit, i only stopped using that baby because the battery controller let the battery go flat.

#catsoftwtxt

• Hoy tengo muchas ofertas. Es el black cat friday -
  #catsoftwtxt

Su juguete favorito
#catsoftwtxt

So, @prologic@twtxt.net, Yarn isn’t rendering the metadata as described on the format documentation. That is, ux2028 is ignored when Yarn renders the description metadata.

#catsoftwtxt

👋 PR to propose Feed Format Extension – Request for comment 🙏

#catsoftwtxt

#catsoftwtxt

Gato pensando fuera de la caja
#catsoftwtxt

Notes on monospace, fonts, ascii, unicode | https://wonger.dev/posts/monospace-dump

👋 FYI: I’ve put in place 301 Moved Permanently redirect(s) for https://dev.twtxt.net/ and all relevant pages to the new domain https://twtxt.dev 👌

-Ni un paso más, vaquero.-
#catsoftwtxt

#catsoftwtxt

-Mi cueva impenetrable.-
#catsoftwtxt

Conde Panterita
#catsoftwtxt

Ahora es mío
#catsoftwtxt

#catsoftwtxt

#catsoftwtxt

¡El gato valenciano y orgulloso de serlo!
#catsoftwtxt

@movq@www.uninformativ.de I’d love it if you write up a page for jenny 🙏 at https://twtxt.dev 🤞

#catsoftwtxt

#catsoftwtxt

There we go!

=> twtxt.dev

🥳

I’m looking to develop a static site for twtxt.dev – A domain I own and have wanted to use for developer and specification docs for Twtxt.

Can anyone recommend a few Hugo themes you like?

All of the dev.twtxt.net content would move over as well.

@prologic@twtxt.net

See https://dev.twtxt.net

Yes, that is exactly what I meant. I like that collection and “twtxt v2” feels like a departure.

Maybe there’s an advantage to grouping it into one spec, but IMO that shouldn’t be done at the same time as introducing new untested ideas.

See https://yarn.social (especially this section: https://yarn.social/#self-host) – It really doesn’t get much simpler than this 🤣

Again, I like this existing simplicity. (I would even argue you don’t need the metadata.)

That page says “For the best experience your client should also support some of the Twtxt Extensions…” but it is clear you don’t need to. I would like it to stay that way, and publishing a big long spec and calling it “twtxt v2” feels like a departure from that. (I think the content of the document is valuable; I’m just carping about how it’s being presented.)

More thoughts about changes to twtxt (as if we haven’t had enough thoughts):

1. There are lots of great ideas here! Is there a benefit to putting them all into one document? Seems to me this could more easily be a bunch of separate efforts that can progress at their own pace:
   

1a. Better and longer hashes.

1b. New possibly-controversial ideas like edit: and delete: and location-based references as an alternative to hashes.

1c. Best practices, e.g. Content-Type: text/plain; charset=utf-8

1d. Stuff already described at dev.twtxt.net that doesn’t need any changes.

1. We won’t know what will and won’t work until we try them. So I’m inclined to think of this as a bunch of draft ideas. Maybe later when we’ve seen it play out it could make sense to define a group of recommended twtxt extensions and give them a name.

2. Another reason for 1 (above) is: I like the current situation where all you need to get started is these two short and simple documents:
   https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html
   https://twtxt.readthedocs.io/en/latest/user/discoverability.html
   and everything else is an extension for anyone interested. (Deprecating non-UTC times seems reasonable to me, though.) Having a big long “twtxt v2” document seems less inviting to people looking for something simple. (@prologic@twtxt.net you mentioned an anonymous comment “you’ve ruined twtxt” and while I don’t completely agree with that commenter’s sentiment, I would feel like twtxt had lost something if it moved away from having a super-simple core.)

3. All that being said, these are just my opinions, and I’m not doing the work of writing software or drafting proposals. Maybe I will at some point, but until then, if you’re actually implementing things, you’re in charge of what you decide to make, and I’m grateful for the work.

• Soy el príncipe de la noche, la incansable zarpita que empuja el crimen hasta hacerlo caer de la mesa.-
  #catsoftwtxt

-¿Cómo que te vas a dormir?-
#catsoftwtxt

Gato negro sobre cabezal
#catsoftwtxt

(#2024-09-24T12:39:32Z) @prologic@twtxt.net It might be simple for you to run echo -e "\t\t" | sha256sum | base64, but for people who are not comfortable in a terminal and got their dev env set up, then that is magic, compared to the simplicity of just copy/pasting what you see in a textfile into another textfile – Basically what @movq@www.uninformativ.de also said. I’m also on team extreme minimalism, otherwise we could just use mastodon etc. Replacing line-breaks with a tab would also make it easier to handwrite your twtxt. You don’t have to hardwrite it, but at least you should have the option to. Just as i do with all my HTML and CSS.

#catsoftwtxt

#catsoftwtxt