I wish I could sleep like dolphins, I would be able to do all the things I wanted much faster.

Hello again everyone! A little update on my twtxt client.

I think it's finally shaping a bit better now, but... ☝️

As I'm trying to put all the parts together, I decided to build multiple parallel UIs, to ensure I don't accidentally create a structure that is more rigid than planned.

I already decided on a UI that I would want to use for myself, it would be inspired by moshidon, misskey and some other "social feeds" mock-ups I found on dribbble.

I also plan on building a raw HTML version (for anyone wanting to do a full DIY client).

I would love to get any suggestions of what you would like to see (and possibly use) as a client, by sharing a link, app/website name or even a sketch made by you on paper.

I think I'll pick a third and maybe a fourth design to build together with the two already mentioned.

For reference, the screens I think of providing are (some might be optional or conditionally/manually hidable):

• Global / personal timeline screen
• Profile screen (with timeline)
• Thread screen
• Notifications screen or popup (both valid)
• DM list & chat screens (still planning, might come later)
• Settings screen (it'll probably be a hard coded form, but better mention it)
• Publish / edit post screen or popup (still analysing some use cases, as some "engines" might not have direct publishing support)

I also plan on adding two optional metadata fields:

• display_name: To show a human readable alternative for a nick, it fallback to nick if not defined
• banner: Using the same format as avatar but the image expected is wider, inspired by other socials around

I also plan on supporting any metadata provided, including a dynamically parsable regex rule format for those extra fields, this should allow anyone to build new clients that don't limit themselves to just the social aspect of twtxt, hoping to see unique ways of using twtxt! 🤞

I always wanted to build a terrarium, but after cleaning my keyboard today, I think I already have one...

Hi everyone, here's a little introduction of my twtxt client (still WIP).

The client I'm developing is a single tenant project that runs entirely in the browser (it might use an optional backend).

It's entirely based on native web-components and vanilla JS, it is designed to act closer to a toolkit than a full-fledged client, allowing users to "DIY" their own interface with pure html or plain javascript functions.

Users can also build their own engines by including a global javascript object that implement the defined internal API (TBD).

I'm planning to build a system that is easy enough to build and use with any skill level, using only pure html (with a homebrew minimal template engine) or via plain JS (I'll be also providing some pre-made templates too).

Everything can be self-hosted on any static hosting provider, this allows to spread twtxt within communities like Neocities and similarly hosted websites (basically any Indieweb/Smallweb/Digital garden website and any of the common GitHub/Lab/Berg/lify Pages).

It will be probably named something like TxtCraft or craf.txt but I'm not really sure yet... 🤔 (Maybe some suggestions could help)

I'm still in the experimental phase, so there's no decent source-code to share yet, but it will soon enough!

While working on the Discoverability for my twtxt client (it runs client-side) I found out that Chrome doesn't allow to set a custom user agent. 🙃

I thought it was a general thing for browsers, but it that was actually allowed in a newer specification, yet it's still not implemented in Chrome, it does work in Firefox though.

Hello everyone! 👋

After a long while away, I'm back on twtxt with this new feed.

Some of you might remember me as justamoment@twtxt.net, that was a test account I made for trying things out, but I ended up keeping it more than planned.

I also tried other social platforms in search of a place that felt right for me.

In the end twtxt was the one that ticked all of my boxes:

• Slow social: it act more like a feed reader and I really appreciate that there's no flood of content that I can't keep up with.
• No server needed: I absolutely love to have total control over my content, I tend to avoid having moving parts that might break, plus you can put your feed under version control and it's all backed up.
• Ownership: I can put my feed anywhere I want and nobody can decide if I can access it or not.
• For hackers: a single .txt file allows me to join a community, how cool is that!

This is why I decided to build my own twtxt client, one that allows you to decide how the feed is presented on your "instance".

It's still in the making but I'll try to share a bit of it once I defined how things should work.

Coincidentally, I discovered that @itsericwoodward and @zvava were also building a twtxt client, seems like twtxt is set to grow!

Hello world, everyone!