(#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)

(#rm3puaa) @prologic@twtxt.net Oh for sure. I just would prefer if the twtxt file could be consumed raw inasmuch as possible; that seems to me to be one of the main points of a raw text-based format vs something more structured. But as you say, this doesn’t really break that. As I say, a clever workaround to an annoying flaw in the original spec. 😉

(#pv7ouaq) @caesar@twtxt.net Yeah, I’ll probably be making some kind of toy project in Go to test it out and see how it fit me when empty handed. 😏

(#rm3puaa) @prologic@twtxt.net Ah cheers. Pity the original spec doesn’t allow real newlines, maybe with indentation or escaping a-la-Markdown to indicate continuation lines… but using \u2028 is a clever solution to working around that limitation.

(#pv7ouaq) @prologic@twtxt.net I love most of the modern Javascript syntax, including arrow functions (this doesn’t include JSX, which is not Javascript and I hate it 🙈) but I do agree that terseness can go too far to the point of getting in the way of readability – definitely an issue with Python IMO. Honestly the only good thing about Python in my opinion is the ecosystem, particularly for data science.
I do like Go from my very limited experience with it; I will definitely be using it more.

(#pv7ouaq) @prologic@twtxt.net Yeah, I was planning to try it myself in the future, there’s seems to be lot of other Python developers that made the switch for the same reason.

I prefer working on the frontend the most, but I’ll surely get my hands on it sooner or later. 😎

@prologic@twtxt.net how do newlines in twts work? I see they don’t show up in the raw twtxt.txt (in my browser at least). The twtxt spec seems (?) to forbid actual newlines, so I’m guessing you are using some sort of workaround specific to Yarn?

(#35kn2ia) @prologic@twtxt.net Huh, supply chain problems, who’d’a thunk it 😆😫 Definitely not going to get better in the short (medium?🤔) term…

(#35kn2ia) @mckinley@twtxt.net I was lucky in a way: I was homeshooled and my studies were very much self-directed. My parents encouraged my interest in tech though they are complete muggles themselves and couldn’t teach me anything about it, so I was entirely self-taught – like many geeks, it seems. As for schools, I do think the situation is improving, at least from what I’ve heard from friends with school-age kids. @prologic@twtxt.net’s experience is reassuring. I’m sure it varies hugely from area to area though; it definitely needs to be a part of national curricula.

(#35kn2ia) @prologic@twtxt.net

you’ll love what my company is trying to do here

I’m intrigued… look forward to hearing more!

(#pv7ouaq) @prologic@twtxt.net No problem! 👍

I can understand your reasoning and i know the pure syntax is not the only part involved when developing in general.

I guess when a programming language changes a lot it’s much harder to adapt and break habits.

Having a clear idea of what you expect from your code and language is a lifesaver when working with many people, ever more in open source projects like yarn.

Keep it up! 💪😎

(#knoga2q) @ullarah@txt.quisquiliae.com Ugh, please no! 😫 As a user I hate those interstitial pages, because they add an unwanted step between me and the page I’m trying to get to, and they obscure the real target of the link (also they’re often used for user tracking). And as a web geek I hate the fact that they break the semantic model of a link pointing to its real target, turning external links into faux internal ones.

(#m7o5dpa) @ullarah@txt.quisquiliae.com I’ll try! ✌️

(#m7o5dpa) @prologic@twtxt.net I can agree on JSX and similar but I must say that arrow functions, classes and so on are quite nice once you get used to them.

I too ended up wanting less and less but exactly for that reason I really enjoy those new stuff the platform offers natively.

Anyway, I’ll keep your style as much as I can. 👍

(#7boroia) @prologic@twtxt.net I think the “worst that could happen” is “it would be semantically wrong”. I don’t think it could ever be actively harmful, since it is correctly treated as a claim, not proof of ownership of the target – it can be used to prove ownership of the origin page, but not of the destination.

That said, I would be in favour of making it explicit (ideally in the Metadata spec) that “User Links” SHOULD be “connected to the feed or author”, not just “usually”. This would make the link metadata more semantically useful.

(#7boroia) @david@netbros.com I’m not sure what you mean. rel="me" is just an html attribute which makes a claim that the target of the link belongs to the same person. It doesn’t prove it; unless it’s reciprocal.

(#m7o5dpa) @prologic@twtxt.net Understandable. 😉

Then I’ll try to make my best to make something nice. 😎

One last question, is it okay to go with standard fetch for API calls or you’re planning to use twt.js?

The repo seems archived though.