fuck xiaomi

(#i3po3ra) @prologic@twtxt.net Maybe having some kind of feature tree could help in defining how the project is structured?

(#vbpdcvq) @prologic@twtxt.net Hmm, if I post a message and then it’s gone when I reload the page, or if the message I replied to has gone, that’s definitely a bug from the UX point of view 😆 … but perhaps unavoidable in a distributed system. But since we’re both on the same pod, I don’t see why that’s an issue? Or is this pod itself running on some kind of distributed architecture?

(#tuizh4q) I guess I should go read the code before asking too many questions, but I’m a little puzzled why the same issues with a feed being huge don’t present an issue every time you want to poll for updates? Particularly with the apparent convention of the newest posts being at the bottom of the file.

As for pagination, sure, it can be hard, but why would it be harder in this case than in the cases where Yarn already does it?

(As for infinite scroll, if you have pagination on the server side already, it’s trivial on the client side. Yes you need JS of course, but not a lot)

(#6uaf4fq) @prologic@twtxt.net Thanks, glad to help! 👍

I have a soft spot for CSS for it’s simplicity and flexibility.

I’m not much of a UX/UI expert but I love searching for design and concepts and sometimes end up putting together fun ideas just for building something that “looks/feels nice”. 😎

(#tuizh4q) I also totally get whet you’re saying about a twtxt file potentially growing to be huge. I guess that, and the fact that it’s necessary to work around it with a significant caching architecture, is a major downside to the model of twtxt itself which I hadn’t considered.

(#tuizh4q) I’m clearly going to have to take a proper look at the code and get a feeling for the data architecture to understand this! From the outside I have to say if something as simple as “display all of a user’s posts” is impossible – especially when a twtxt file is literally a list of all of a user’s posts – it feels like some very strange architectural choices must have been made… but I am also well aware that a lot of painstaking thought by very clever people has gone into this, and I haven’t even looked at the code, so don’t mind me 😆

(#2kj5qta) @carsten@yarn.zn80.net Yeah, I looked up at a bunch of Twitter UI redesigns on Behance and Dribbble to understand how they tried to “improve” the app and took what felt nice to me for the #pwa

For me an ergonomic interface is very important and keeping in mind the various ways to use a touchscreen + the desktop interface, I kept the possibility of having multiple layouts to switch to the user’s liking.

(#2kj5qta) Here some mockups for the app layout and navigation, a bit better this time!

What do you guys think?
#pwa

rip insta in russia

(#fe55h2a) @carsten@yarn.zn80.net I checked it too, seems that it has a m.request that use the old XMLHttpRequest but expose a fetch style API by wrapping it in a Promise.

Here the doc page for reference

(#6uaf4fq) @ullarah@txt.quisquiliae.com Fantastic, It feels so comfy!

Just one issue i noticed, on mobile the first button .replyBtn have the ::after element under the icon pushing the label.

It seems to fix if you use:

.replyBtn .ti {
    white-space: pre;
}

https://www.techdirt.com/2022/03/10/cloudflare-says-shutting-down-in-russia-would-give-putin-what-he-wants/

(#tuizh4q) @prologic@twtxt.net

philosophical reasons […] design decision

That I can understand (though to the extent that I understand it, I think I disagree with it 😄). I was asking more about the technical barriers @mutefall@twtxt.net mentioned.

responses are provided from the cache

I see, so we’re taking about an architectural limitation in Yarn, rather than twtxt. Still, I know cache invalidation is famously hard, but surely an intentional page load from a user trying to view a feed that isn’t (fully) cached is about the best signal you could get to fetch that data from the origin? 🤔

(#tuizh4q) @prologic@twtxt.net

How do you display this in any reasonable way?

Pagination? Like Yarn uses elsewhere. Or infinite scroll, but from the server side that’s still pagination.

Which is what? To view the entire contents one someone’s feed? 😅

Exactly. Every other social network has that feature; I’ve missed it here serveral times already and it looks like I’m not the only one.

I still don’t get the difficulty from a technical point of view I’m afraid. 🤔

@prologic@twtxt.net so far as I can see both your and my most recent replies to #x6zqkha just disappeared - a bug?

(#x6zqkha) @prologic@twtxt.net Hmm but if you’re self-hosting the bridges (the only option I think since they generally have to run on the same machine as the Matrix server) that man in the middle is yourself 😉

Of course you do have to trust the code, but it’s all open source.

(#tuizh4q) @mutefall@twtxt.net @prologic@twtxt.net I don’t understand this answer at all from a technical perspective (leaving any philosophical arguments aside). A twtxt file is literally a flat file containing a list of all of a person’s posts. Surely simply displaying all of that person’s posts in Yarn should be the easiest possible thing to do, way easier than threading etc. Why would it require “investing heavily in infrastructure” or for the protocol to be “redesigned from the ground up”?

I’m guessing I’ve misunderstood what you’re saying; can you help me understand?

(#x6zqkha) @prologic@twtxt.net but if you used those external services directly without bridging, you’d still have to trust all those things, right? Take, say, FB Messenger. Whether I ‘bridge’ it to Matrix or use Messenger directly, I have to ‘trust’ Facebook (ha ha, as if! 😆) Same for Signal, WhatsApp, IRC, or anything else you bridge to.
That said, I don’t really use bridging much; for the services I tried it for it was too much hassle making the bridge work for it to be worthwhile.

listening to Egor Letov may open third eye

(#2kj5qta) @prologic@twtxt.net I’m trying to get the navigation right first, I’ll be sketching a couple more before starting on the code. #pwa

(#hw5zqkq) @~duriny@envs.net ъеъ

(#cl7vera) @mutefall@twtxt.net sorry I’m getting into the discussion, but i think searx is the best that can be

(#xmpa4da) @hecanjog@hecanjog.com -23 of celsius. :(
hope i’ll get spring weather soon too

@prologic@twtxt.net uh… how can I view all posts from account? as example from @news@twtxt.net I can see only one recent post

(#rcvjkrq) @prologic@twtxt.net comfortable*. for reading, for commenting, you know. by the way, thanks for warm welcome

— freddy, you are supposed to be on lockdown!
— Vanessa, megalovania sounds

(#ooxps7q) @darch@twtxt.net That’s my approach, yep 👍 – but I can also see @prologic@twtxt.net’s argument that Matrix is over-engineered and current servers are resource hogs and (arguably) hard to get set up…

No time to code yet but started playing around.

(#rcvjkrq) @prologic@twtxt.net thank you! I hope this place will be comfy for my future posts and readers

(#cl7vera) fact

hello world

(#ooxps7q) @prologic@twtxt.net I mean, sure, so long as it’s fully e2ee and private (Yarn and feeds in general tend to be public…) 😄

(#qqfi5za) @prologic@twtxt.net oh it looks quite different on Android 😆

(#5pe3caq) @prologic@twtxt.net for real. Sounds like the whole meeting should have just consisted of them sharing that one piece of information, instead of buying it in vaguely reassuring filler text on a screen.

(#4uape5q) @prologic@twtxt.net this is what it should look like (in Element / SchidliChat)

(#qqfi5za) @prologic@twtxt.net what’s that client? I don’t recognise it

(#4uape5q) @prologic@twtxt.net I think that’s approximately what happens behind the scenes, it shouldn’t be visible on that easy to the end user, so I guess something else is going wrong… (or bad UI in the client you’re using?) 🤔

(#4n4ppya) @prologic@twtxt.net I’m curious about this. Surely the implication of a twtxt file being self-hosted (unless you’re using someone else’s pod…) is that I control its content; I can delete/edit what I want. Sure, someone else might have saved/cached it, but the same would apply to any web page: if it’s on my server, I can delete the canonical version. Doesn’t mean every trace is immediately/permanently gone from the web, but any remaining cached versions are just outdated cache artifacts. Am I wrong?

(#hoydxeq) @prologic@twtxt.net that’s definitely a feature I’d be interested in. Bookmarking to read the RFC later!

jA0ECQMC+88Lc1s1t5z/0joBkAEIVmiKNpJ4A9TiAmJyFl+MEbOAxqyTfGqAvycVuicSsyxyTXKe DJiJD7Vkv3Er6+jQYi8zDmRd

LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQpIYXNoOiBTSEE1MTIKCnRlc3QKLS0t LS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRR3pCQUVCQ2dBZEZpRUVTMENqUTFNeGpEWHZs QXV3MTdEcDRRaUFZeWNGQW1JcGhCQUFDZ2tRMTdEcDRRaUEKWXlmR0Jnd0F3K2l3ZFJKblNLR2Zp NEZoeXRrYlJVZ0JGM3Q4N1R6UjFZRUZQRkVBbnJwMk9nRFRwcmZ4R0lzSQo5blhXZ0xwSFpuUG1k ZWkzN3NKR05zSkU3TjI0OGZTai9Ganh2REgwWlVHSUwvemFrN3JRWW9XV3FCY1EwTTR5CmhNYSsr RGdUUTFPNWNqYlhNVnlXNS9zTU1NVFNpaXlab1RvTGM3RHRlZTZDam5iNU1wb0FWTTN4WU9mczBI QzcKNWNZemtVNktaK0dlNCtGSGJxRlNoWFBvRW4zSVlvWUpUTGVOQ2taK2QzQUgzMTdsaHlkSUk4 N1VxTHBNbHlEcQpyR0d3elA1QkI3eFhWdjFlTWVtRUg5ZXNZMjEyTTArTkxHT2l5U0tIV25PZnI5 L09hQ0VieVlzL2dsOFFDNkZDCmtNTVFRV1JkV3k3MFVHS05URHZIM0w2OTFlUFlkb1dlYlJPc1Zm RUdSLzhzdGpUNUU4c0RBZ2c0VzBnUkVjczUKU1BvVzYxV1JUSUxXdWpHTkwrMFdCbW51UEl4cUR3 QmU4V1h0eUc2bDdqMGh2dlhpbXplK3RTM29WL2JqMlFteApTekdRTzg1aGtRTTlWNmVrSXlObElM aEExVVY2eTU1eHlLZ3M4R2tSamI3VlBOTmxIc3NYeHl2UkJOK3ZQTXljCjVPY0hlWm5aCj11anlr Ci0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo=

LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQpIYXNoOiBTSEE1MTIKCnRlc3QKLS0t LS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRR3pCQUVCQ2dBZEZpRUVTMENqUTFNeGpEWHZs QXV3MTdEcDRRaUFZeWNGQW1JcGd4QUFDZ2tRMTdEcDRRaUEKWXlmMlZndi9SR3owM1ZHVU5HbzZG S0JJNDBjYmpwU0l4eVBWd0U2MkR2UUpuaXY3WEx4c2tQM013c1JVWjV4UQpJUFNSQUJHMStVMk9T bGV5TEJ4d0twc2FGR1ViMmYvZk1pZmJaWFF0NWJqaGwyOXRiNWRJRTl0a1pST1FLbHhpCmRJWk1B d0RuTkp2bU8yWkJPcUhrREhkWURUNE1lazdqVUlYNWV4aUJMUGNpaVlwUDJXNXFzdExKY0ZTV2t6 MVkKN2kwSXNLVHFuWEZoS2hIOHkzVG9hVU4weUZ1VU9qVFU2R2ZUNE9uRXQwNG11MmluK2JkOG0r U1VXN1N0SWQwVgpqZnV6MW4vZ2RDUDJWdlY0V25JUDBBb0FsSGltN3YyQXZNd3NpMTFKRGpZaWUw SE9oTzg3MmM0YkpoRjViSmdyCmZXdUg0K01ReUFzQ1dsTGVaNmo3QjVFSEM1cGJONkUyZ2FMR3VH a0NETk9kQkZDWjlVOTZNVVhCamRTZ2s5OE4KMlBJbzdWK3ZVN3lJdlJWa2JmZUlZSXZLTkNNZ0da ZVZXZy81dVFYV1VtMXpRQkJ0dG16clQ0Sjgvd2cwNzhmSAozRkFwc0lyMUNWYVovVFg3NFFROEw1 dzA5RnhUUUg0VkVESHliU1RyWVpGbi8rVHhFaENSdFQ1UlBIczd3WXlsCkxlVTkxdjFrCj1ZRE4x Ci0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo=

LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQpIYXNoOiBTSEE1MTIKCmVjaG9pbmcg ZG9lc24ndCB3b3JrIHdpdGggcGlwZQotLS0tLUJFR0lOIFBHUCBTSUdOQVRVUkUtLS0tLQoKaVFH ekJBRUJDZ0FkRmlFRVMwQ2pRMU14akRYdmxBdXcxN0RwNFFpQVl5Y0ZBbUlwZ29vQUNna1ExN0Rw NFFpQQpZeWY3cUF2OUVBaDFKay9od0JLclBxakZERXVleS9VYkhJVml2NkUvbk1tYnRLT2crcVBC dDIzb2NZOVNiMEYxCnFWeFhlV25HTmNOUHhINDlRWVhLTE1yTU1rZXpTZmE5K1NMT2Nkdm1RVThu MTBaS0lURGdVN3hjM3NzNWlHQkwKeHhIc3cvOHdCZDlpTXgrdXR0citLSmdSS0RhakpXcGxoc1Ny SUdranRiTEZMZ1dub3cwSzRZOUpMRTF0WEphaQpMblFGWXBzUlBRdW1LUXh5cUFFakl6Mm1qY0tV clBZenhmaW9YWUttdkF1bzdsTXdwL29UYzVyNFZBS1AwZlIvCjZTOGdPQ1VNc3BIVU9WQkhjRVpa RmIyeFBueWUwelcrZEhHZndpN28wQlNqY3c4SlVqVzVteDlNazV0NC80enoKQ2VibDlZL01UYTV1 ZlhNb0I1a1pLRkdJM3hUSzZ3ZVlDSnlWWDVlT1dFQjBZaGFVczMyQ0FIdjJSQXlXUEVEUQpTK01H YUZIeFJtNFp4SUVhS2JsLzhOT0VwV0E5anBCZmdFb0RkUjk0NXJHdnlYQ1FZb1ZVVDIzQzEvdkpQ cWt0Ci8yWWtiaXhmdnVFR3dhTDVQZHp6WlpJRlJHd2pvS0p0d0NUWi85RGhNdGFudEZMclcvWFdS UmVSWlp4ZXVVTmwKRW9vSnpKU0kKPTQxaG8KLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tCg==

echoing doesn’t work with pipe

trying through yarnc

@test_feed@twtxt.net posting as test_feed

(#i6mikka) @carsten@yarn.zn80.net sometimes I seriously wonder whether the cons of the Internet outweigh the pros 😣

(#t47rjwa) @movq@www.uninformativ.de that’s exactly what it means 👍
As for clients, I prefer SchildiChat myself, it’s an Element fork with a few improvements. I find FluffyChat too basic, but then I never liked WhatsApp either, which I guess it what it’s trying to imitate UI-wise.

(#5pe3caq) Fascinating reading: Death by PowerPoint: the slide that killed seven people (Columbia Shuttle)