Avatar @alexonit

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! 🤞

vor ≈1 Monat | #x4s4mla |
Antworten zu #x4s4mla von @alexonit
Avatar @bender | #x4s4mla

@zvava agreed. I think display_name will be redundant, and add to the "busy" factor. That is, the opposite of simplicity.

vor ≈1 Monat | #jfon3ta |
Avatar @bender | #x4s4mla

Of course, all things optional is fine. Like, it will be ignored (just like banner would) for clients having no knowledge of it.

vor ≈1 Monat | #uh5p56q |
Antworten zu #uh5p56q von @bender
Avatar @zvava | #uh5p56q

@bender @alexonit funnily enough i came up with the idea for a banner field when i started working on bbycll too (though i still need to implement avatar uploads themselves first)

vor ≈1 Monat | #o67wmcq |
Avatar @alexonit | #uh5p56q

@zvava It is a common UI element in most social platform after all, it's easy to include when planning something similar.

vor ≈29 Tagen | #qywfedq |
Avatar @alexonit | #x4s4mla

@zvava @bender At first I added it without thinking when planning the possible fields based on other UIs I was researching.

I was about to discard it but after thinking about it a bit I noticed that the services allowing to have a separated nick and display_name could unlock some good uses.

For example some added context or at-a-glance information like pronouns or statuses (like Artist [Accepting commissions] or App Name (v2.5)) while other used a more readable version of the nick (blog.domain.com became Person Name's Blog).

Of course it is absolutely optional and it can be safely ignored, but with my vision of being able to build more that a pure twtxt clients, giving it a first-class support just like the other known fields felt right to me.

vor ≈1 Monat | #n7ngrla |