Spent an absurd amount of time searching for the “update fork” button on #gitlab’s web interface.
Why? Because it turns out you can only see it if you are in landscape, in portrait view the button simply does not exist…
You know what! tt2 UX kicks 🍑 !! Message previews and all … Sheeeeesh! 😁
yarnd
.
Hopefully I haven’t missed or messed anything upu 😅
* 101f3eb0 - (HEAD -> main) Fix a bunch of UX to do with following/unfollowing, bookmarking and unbookmarking (3 seconds ago) <James Mills>
Testing UI/UX is hard™ 😉
Going to try and few up a few more UX bugs today with yarnd
.
@bender@twtxt.net Hehe good sleuthing 🤣 I swear it was an edit ✍️ Haha 😂 yarnd
now “sees” both every single time, where-as before it would just obliterate the old Twt, but remain in archive. Now you get to see both 😅 Not sure if that’s a good thing or not, but it certainly makes it much clearer how to write “code logic” for detecting edits and doing something more UX(y) about ‘em 🤔
yarnd
UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
The nice thing here is that any Ui/UX rendering for a “good user experience” is similar to what yarnd
does for Youtube/Spotify/whatever embedding. Plus anyone can participate, even if they don’t really have a client that understand it, it’s just text with some “syntax” afterall.
💡 I had this crazy idea (or is it?) last night while thinking about Twtxt and Yarn.social 😅 There are two things I think that could be really useful additions to the yarnd
UI/UX experience (for those that use it) and as “client” features (not spec changes). The two ideas are quite simple:
- Voting – a way to cast, collect a vote on a decision, topic or opinion.
- RSVP – a way to “rsvp” to a virtual (pr physical) event.
Both would use “plain text” on top of the way we already use Twtxt today and clients would render an appropriate UI/UX.
** leibovitz **
Folks what that haunt me (positive) on the Fediverse may have seen me sharing progress shots from this, but here I am, and I have made another camera application for the web. Leibovitz combines a lot that I learned making my other camera applications into one, hopefully less clunky package.
With leibovitz you can either take new photos, or upload any image file and apply filters to it. The UX to toggle between the two modes is … ⌘ Read more
Twtxt was made for nerds, by nerds.
I’d like to change that. It’s by nerds/hackers, for nerds/hackers and friends of these. It doesn’t have to be hacky all the time, as you don’t need to be a nerd to have a blog.
But, for that to happen, someone has to build the tools to improve UX.by design there really is no way to easily discovers others
Yeah, I agree, and although there are directories of email addresses, usually you don’t want that, unless you are a ‘public figure’.
I couldn’t say that a microblogging is a “social network” by default, as a blog is not either. At the same time, people would expect to find new people and conversations, as you’d do in a forum.
I think of two features on top of the current spec:
- Clients showing a few posts of what your following are watching but you don’t, so perhaps you find something interesting to follow next. Or that feature of “Your ‘followings’ are following these accounts/people”. (Hard to explain in english, but I hope you get the idea)
- Sharing your .txt into some directory, saying “Hey, I have this twtxt URL, I want to be discovered”. I’m thinking of something like the Federated tab on Mastodon.
@prologic@twtxt.net I’m speculating, but if I had to guess I’d say it’s probably asking for your user password in order to access some user keyring (or whatever your OS uses to manage user secret credentials) used to safely store your passkeys related data in order to do its passkeys /ME doing air quotes Magic™ … you could try with a different password manager to avoid said scenario.
Also, passkeys UX sucks.
ok, sounds like a ‘large’ project to me.
Is it more an API (more oriented to developers), more oriented to UI/UX/Frontend? Perhaps both?
I’d go with prologic’s advice of measuring and prioritizing. Perhaps you have a budget or at least something like “let’s see how far can we reach in 6 months”, and possibly you won’t finish in the time you have (just guessing).
Something that has helped me was defining “Why do you we want to refactor this project?”.
Could it be to make it compile on newer versions, or making it easier to grow and scale, or perhaps they are trying to sell that product to another company. Every reason has a different path, IMO.
This UX can be very frustrating.
ofrnxmr completes third milestone for BasicSwapDEX CCS
ofrnxmr1 has completed2 the third milestone (M3-F/M3-B) for their CCS proposal3 to empower and steward BasicSwapDex4 to production quality software:
Request for M3-F and M3-B (M3-O comes end of month 4) [..] This next sprint (month) will add some of the more exciting functionality, further improve the UX and add some security features (such as client auth for the api port and amm integra … ⌘ Read more
@xuu@txt.sour.is I have a theory as to why your pod was misbehaving too. I think because of the way you were building it docker build
without any --build-arg VERSION=
or --build-arg COMMIT=
there was no version information in the built binary and bundled assets. Therefore cache busting would not work as expected. When introducing htmx and hyperscript to create a UI/UX SPA-like experience, this is when things fell apart a bit for you. I think….
👋 If y’all notice any weird quirks or UI/UX bugs of late on my pod, please let me know! 🙏 For those that have a Javascript enabled web browser will notice (hopefully) a SPA (single page app) like experience, even in Mobile! No more full page refreshes! All this without writing a single line of Javascript (let alone React or whatever) 😅 – HTMX is pretty damn cooL! 😎 #htmx
It would help for UX for sure. emoji keyboards are hard to come by on the desktop.
📣 NEW: Announcing the new and improved Yarns search engine and crawler! search.twtxt.net – Example search for “Hello World” Enjoy! 🤗 – @darch@neotxt.dk When you have this, this is what we need to work on in terms of improving the UI/UX. As a first step you should probably try to apply the same SimpleCSS to this codebase and go from there. – In the end (didn’t happen yet, time/effort) most of the code here in yarns
will get reused directly into yarnd
, except that I’ll use the bluge indexer instead.
@ullarah@txt.quisquiliae.com Didn’t we talk about at some point a way to set the maximum height of te panels with some UX way to read the rest? 🤔 Is that still on the cards or a bad ideas? 🤔
Oh, me too: FreeBSD, macOS, and Solaris in server environments extensively, and Linux, AIX, HP/UX, Irix, probably others I’m forgetting. Plan 9 is a whole other class of thing.
@prologic@twtxt.net :-D i consider myself subpar on UX outside of React, but can def give it a stab.
The typical failure mode of UX is no longer the shaggy-dog story (i.e., the turing tarpit: a lot of build-up for a disappointing conclusion); it’s bunch of shallow one-liners with no connecting thread, which are as funny as they can be for their length but don’t make the most of a set.
Other ways in which UX is like stand-up comedy: if you omit the setup, the punchline won’t land; reading the room is a vital skill
Audacious Fox: The UX of Hidden Game Mechanics https://audaciousfox.net/linked/2018/hidden-game-mechanics