— W3C, HTML Design Principles § 3.2 Priority of Constituencies
— W3C, HTML Design Principles § 3.2 Priority of Constituencies
autofocus="true" has always been the case (_the template for the postbox has conditional logic_) for Timeline, Discover and Mention views. There are like one or two views where it is set to false. So hmmm I'm not sure wtf I was thinking back then 🤔 How should it behave?
autofocus="true" has always been the case (_the template for the postbox has conditional logic_) for Timeline, Discover and Mention views. There are like one or two views where it is set to false. So hmmm I'm not sure wtf I was thinking back then 🤔 How should it behave?
(#d4acmcq was:zllu75a) just for an example. Extending the Subject Extension to support (#hash [was:<hash>])? 🤔
(#d4acmcq was:zllu75a) just for an example. Extending the Subject Extension to support (#hash [was:<hash>])? 🤔
- I'm not really that happy with the code between
PostHandler() and DeleteTwtHandler() anymore 😢 It _really_ needs some major refactoring, and better tests.- This only works for users (_for now_), no support for Persona(s) / Feeds sorry.
One side-effect I've noticed (_which was always the case_); an Edited Twt whilst preserves the original timestamp, gets appended to your feed at the bottom of the file. This is counter intuitive when you think about editing text files with a text editor, but it does make sense in the way
yarnd treats feeds as append-only (_I had just forgotten_). I'm not doing anything about this though.
- I'm not really that happy with the code between
PostHandler() and DeleteTwtHandler() anymore 😢 It _really_ needs some major refactoring, and better tests.- This only works for users (_for now_), no support for Persona(s) / Feeds sorry.
One side-effect I've noticed (_which was always the case_); an Edited Twt whilst preserves the original timestamp, gets appended to your feed at the bottom of the file. This is counter intuitive when you think about editing text files with a text editor, but it does make sense in the way
yarnd treats feeds as append-only (_I had just forgotten_). I'm not doing anything about this though.
Username: _<focused field>____
Password: ____________________
[x] Remember me (Enabling this feature will keep
you logged in, even after closing your browser.
Do not active this setting on shared devices.)
[Login]
The "remember me" checkbox could be already activated by default. This would benefit people like @bender.
An alternative would be to make the session lifetime configurable in the user profile. So bender would then set this to forty-two years. :-) Definitely something for power users who know what they're doing. More dangerous for the average Joe, though.
Sunset
Afaik, that’s not possible on Wayland. slurp exists but there is no standard way (yet?) for it to query the window tree. It’s different for each Wayland compositor. slurp’s README includes an example for Sway; for dwl you need this patch; and selecting individual windows probably does not work at all on labwc (because those guys try to stick only to established protocols/standards – an admirable goal).
This is just a small example. I think things like these slow down Wayland progress/adoption a lot. You could get a lot more done on X11 because the rules weren’t so strict. On Wayland, everything has to become an official protocol (that each compositor then has to implement individually) or it’s going to be an incompatible, unofficial, compositor-specific solution.
Both approaches have pros and cons. Wayland is much more idealistic than the “wild west” of X11. The price is that it takes a hell of a lot more time and energy to push things forward on Wayland.
Afaik, that’s not possible on Wayland. slurp exists but there is no standard way (yet?) for it to query the window tree. It’s different for each Wayland compositor. slurp’s README includes an example for Sway; for dwl you need this patch; and selecting individual windows probably does not work at all on labwc (because those guys try to stick only to established protocols/standards – an admirable goal).
This is just a small example. I think things like these slow down Wayland progress/adoption a lot. You could get a lot more done on X11 because the rules weren’t so strict. On Wayland, everything has to become an official protocol (that each compositor then has to implement individually) or it’s going to be an incompatible, unofficial, compositor-specific solution.
Both approaches have pros and cons. Wayland is much more idealistic than the “wild west” of X11. The price is that it takes a hell of a lot more time and energy to push things forward on Wayland.
Afaik, that’s not possible on Wayland. slurp exists but there is no standard way (yet?) for it to query the window tree. It’s different for each Wayland compositor. slurp’s README includes an example for Sway; for dwl you need this patch; and selecting individual windows probably does not work at all on labwc (because those guys try to stick only to established protocols/standards – an admirable goal).
This is just a small example. I think things like these slow down Wayland progress/adoption a lot. You could get a lot more done on X11 because the rules weren’t so strict. On Wayland, everything has to become an official protocol (that each compositor then has to implement individually) or it’s going to be an incompatible, unofficial, compositor-specific solution.
Both approaches have pros and cons. Wayland is much more idealistic than the “wild west” of X11. The price is that it takes a hell of a lot more time and energy to push things forward on Wayland.
Afaik, that’s not possible on Wayland. slurp exists but there is no standard way (yet?) for it to query the window tree. It’s different for each Wayland compositor. slurp’s README includes an example for Sway; for dwl you need this patch; and selecting individual windows probably does not work at all on labwc (because those guys try to stick only to established protocols/standards – an admirable goal).
This is just a small example. I think things like these slow down Wayland progress/adoption a lot. You could get a lot more done on X11 because the rules weren’t so strict. On Wayland, everything has to become an official protocol (that each compositor then has to implement individually) or it’s going to be an incompatible, unofficial, compositor-specific solution.
Both approaches have pros and cons. Wayland is much more idealistic than the “wild west” of X11. The price is that it takes a hell of a lot more time and energy to push things forward on Wayland.
----
- Event: Yarn.social Online Meetup
- When: 22nd June 2024 at 12:00pm UTC (midday)
- Where: Mills Meet : Yarn.social
- Cadence: 4th Saturday of every Month
- Agenda:
> Anything we want to talk about. Twtxt, Yarn, self hosting, cool stuff you’ve been working on. chit-chat, whatever 😅
#Yarn.social #Meetup
----
- Event: Yarn.social Online Meetup
- When: 22nd June 2024 at 12:00pm UTC (midday)
- Where: https://meet.mills.io/call/Yarn.social
- Cadence: 4th Saturday of every Month
- Agenda:
> Anything we want to talk about. Twtxt, Yarn, self hosting, cool stuff you’ve been working on. chit-chat, whatever 😅
#Yarn.social #Meetup
----
- Event: Yarn.social Online Meetup
- When: 22nd June 2024 at 12:00pm UTC (midday)
- Where: https://meet.mills.io/call/Yarn.social
- Cadence: 4th Saturday of every Month
- Agenda:
> Anything we want to talk about. Twtxt, Yarn, self hosting, cool stuff you’ve been working on. chit-chat, whatever 😅
#Yarn.social #Meetup