In-reply-to » Something odd I have been noticing. Occasionally, when I come to twtxt.net on mobile, the keyboard comes up but there is nothing to type. There is some code left behind from the old onfocus that’s causing this, I gather.

@bender I can see in the templates that 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?

⤋ Read More
In-reply-to » Something odd I have been noticing. Occasionally, when I come to twtxt.net on mobile, the keyboard comes up but there is nothing to type. There is some code left behind from the old onfocus that’s causing this, I gather.

@bender I noticed that too. But I couldn’t remember whether that was a preexisting behavior or not. So hmmmm

⤋ Read More

Something odd I have been noticing. Occasionally, when I come to twtxt.net on mobile, the keyboard comes up but there is nothing to type. There is some code left behind from the old onfocus that’s causing this, I gather.

⤋ Read More
In-reply-to » @bender Nothing that isn't already a known side effect. Really it is up to clients to figure this out and have storage or caching mechanisms that can cope with diverging threads.

@bender This is true! (as we spoke!) It’s okay though, I think we’ll eventually solve this as it becomes a thing that annoys us too much 🤣 I like your idea of having some optional, but recommended of handling edits. Like having something like (#d4acmcq was:zllu75a) just for an example. Extending the Subject Extension to support (#hash [was:<hash>])? 🤔

⤋ Read More
In-reply-to » @bender Nothing that isn't already a known side effect. Really it is up to clients to figure this out and have storage or caching mechanisms that can cope with diverging threads.

@prologic@twtxt.net but the problem is with Yarn too (the front end)! You know it has happened before a few times. Now the chances increase.

⤋ Read More
In-reply-to » @prologic hey mate, all working well here so far. The login issue isn't really an issue as far as actually logging in goes, rather if I get my password wrong it gives the response error code in console, the response of which contains the HTML for the wrong password page if you inspect it, but on the frontend itself nothing actually happens which is the confusion. Just stays on the login page as if it was never submitted. Am I alone in having this issue as well?

@prologic@twtxt.net Perfect 👌

⤋ Read More
In-reply-to » Just added support for deleting and editing arbitrary Twt(s) at anypoint in your timeline. Some things to note:

@bender Nothing that isn’t already a known side effect. Really it is up to clients to figure this out and have storage or caching mechanisms that can cope with diverging threads.

⤋ Read More
In-reply-to » Oh boi! 🤦‍♂️ I totally forgot to put this notice up, and the month has flown by so quickly! 😅 Sorry folks! Hope it's not too late! ⏰ for our monthly Yarn.social Online Meetup! 🤞

@bender Sounds good 👌

⤋ Read More
In-reply-to » @prologic what is the side effect of this for others not using Yarn? Right now conversations break upon editing, wouldn’t this potentially cause more havoc? Wouldn’t the specification need to be extended somehow to force a refresh of any edited twtxt?

@bender Let’s discuss on the call later today 👌

⤋ Read More
In-reply-to » @prologic what is the side effect of this for others not using Yarn? Right now conversations break upon editing, wouldn’t this potentially cause more havoc? Wouldn’t the specification need to be extended somehow to force a refresh of any edited twtxt?

I mean, I like it, but I can’t help foreseeing mess. 😬

⤋ Read More
In-reply-to » Just added support for deleting and editing arbitrary Twt(s) at anypoint in your timeline. Some things to note:

@prologic what is the side effect of this for others not using Yarn? Right now conversations break upon editing, wouldn’t this potentially cause more havoc? Wouldn’t the specification need to be extended somehow to force a refresh of any edited twtxt?

⤋ Read More
In-reply-to » Oh boi! 🤦‍♂️ I totally forgot to put this notice up, and the month has flown by so quickly! 😅 Sorry folks! Hope it's not too late! ⏰ for our monthly Yarn.social Online Meetup! 🤞

@prologic@twtxt.net that’s tomorrow at 08:00 EDT. I will try joining from mum’s. That’s about the time I sip coffee with them on weekends. 😊

⤋ Read More
In-reply-to » Oh boi! 🤦‍♂️ I totally forgot to put this notice up, and the month has flown by so quickly! 😅 Sorry folks! Hope it's not too late! ⏰ for our monthly Yarn.social Online Meetup! 🤞

Anyone coming to today’s meetup? 🤔

⤋ Read More

Just added support for deleting and editing arbitrary Twt(s) at anypoint in your timeline. Some things to note:

  • 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.

⤋ Read More
In-reply-to » @bender Hmmmm I'm not sure about this... 🧐 Does anyone have any other opinions that know this web/session security better than me?

@prologic Visiting the login page would give you something like this:

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.

⤋ Read More

In (old, pre-compositor) X11, windows were rectangles on screen. Every normal X11 client could query all windows and their positions. Tools like slop were easy to implement: You can use it to interactively select one of the windows on the screen, e.g. to make a screenshot of that window. slop just queries the window under the mouse pointer, it can then highlight it and read its position. Done. (slop includes more bloat/eyecandy, but that’s beside the point.)

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.

⤋ Read More

Oh boi! 🤦‍♂️ I totally forgot to put this notice up, and the month has flown by so quickly! 😅 Sorry folks! Hope it’s not too late! ⏰ for our monthly Yarn.social Online Meetup! 🤞

Anything we want to talk about. Twtxt, Yarn, self hosting, cool stuff you’ve been working on. chit-chat, whatever 😅

#Yarn.social #Meetup

⤋ Read More
In-reply-to » @prologic hey mate, all working well here so far. The login issue isn't really an issue as far as actually logging in goes, rather if I get my password wrong it gives the response error code in console, the response of which contains the HTML for the wrong password page if you inspect it, but on the frontend itself nothing actually happens which is the confusion. Just stays on the login page as if it was never submitted. Am I alone in having this issue as well?

@eldersnake@we.loveprivacy.club Fixed!

⤋ Read More