As promised, I’ll be online here:
James Mills has invited you to a meeting on Peer Calls.
Feel free to join, anyons is welcome! 🤗 Just state who you are at least, your Twtxt / Yarn.social feed will suffice 🤣
@email@example.com (#payoedq) Neato. It’s so hard to get the lighting right when taking pictures of birds. 😢 They always end up too dark. Or the background is way too bright. Guess I’d need HDR. 🥴
@firstname.lastname@example.org @email@example.com (#6gszxta) The only problem with time-based approaches is that if a feed is down for some reason (or just not fetched in time) you might miss older twts you haven’t seen. Depending on the use case that might even be a feature to ignore outdated content. In my client I just mark every twt read and the next time I start it, all fully read conversations will be hidden.
(#dewqhaa) Didn’t disappear but my pod may have restarted 😂
It’s not just a perk of being on a new platform I don’t think. We’ve gone out of our way to build and design for small interconnected communities of pods.
* 5fdff4a 2021-10-23 | Fix bug with User.FollowAndValidate() to use heuristics to set an alias for the feed if none given (HEAD -> master, origin/master) [James Mills]
@firstname.lastname@example.org Hehe you’re getting quite a following from across the network of pods (as small as the network is currently) 😁
Birds were quite active in front of my window this morning, unfortunately, the sun wasn’t really out yet. https://lyse.isobeef.org/voegel-2021-10-23/
@email@example.com not sure the manual Follow function (that I only just noticed now has been moved to Settings) resolves the
nick quite right. I followed the https://feeds.twtxt.net/tiktok/twtxt.txt feed on my pod by pasting in the URL, but it adds it to the Following list without any nick attached.
See the top of my Following list on my twtxt.txt: https://yarn.andrewjvpowell.com/user/eldersnake/twtxt.txt
Every time a package has “pandoc” as a build dependency, I’m like: “Holy mother of cows, did I just install the entire haskell ecosystem? 🤯”
@firstname.lastname@example.org Not every great name for a “thing” has to be tarnished by shitty evil corporations that build disgusting platforms and apps that harm children and teenages 🤣
(#6gszxta) @email@example.com Bloody LOL, I’ve always avoided the tiktok feed thinking it had something to do with the shitty social media platform, just now I went and looked at the feed and realised it was for the time 🤣
(#vels76a) i’m not sure if the storm is getting worse on whether I should shut down or not…
this concept of a marker could itself just be built into a client in my opinion
(#7x6gora) @firstname.lastname@example.org The thing is if you stick around long enough you’ll get to understand and find out the reasons why we made certain decisions and choices along the way 🤗 many of which actually have significant social impacts on individuals and groups of people ☺️
I may have to power down my server room until this storm blows over 😳
Sorry @email@example.com 😁 This is just bad timing! 🤣 I bought a UPS! it’s coming early next week 👌
@firstname.lastname@example.org (#cdl6foa) I agree on a release process. However, I’m not so sure on the code signing part. M$ lately signed rootkits again. So it’s more a false sense of security. Could be a different story for your own code, though, as there’s no other party involved. Need to think about that a bit more.
@email@example.com (#6gszxta) :-D Don’t get me wrong, the idea isn’t bad at all, maybe just needs slight tweaking. Like maybe showing the new unread twts in that conversation if you’re logged in. But I think there’s no concept of read/unread twts in yarnd, so well, probably won’t work, but could be useful I reckon. It’s just an appearance issue.
(#gyxy4ta) @firstname.lastname@example.org Hmmm you might be right there. I’ll double check and do some testing 👌 The problem is that even non-feeds often don’t produce errors as such so it’s quite hard to tell for sure whether a feed is actually valid or not 🤔
Dunno but hope we hear that said more and more often
Would be nice to!
(#7x6gora) @email@example.com Oh hahah 😂 And you’ve discovered the the side-effect of how this all works. 😂 Since Yarn.social is actually based on and around the Twtxt spec, it has some of its drawbacks, however we also did a lot of work to extend the spec and support what was needed to actually make it viable and useful. The web interface of
yarnd only lets users edit their “last post” for a couple of reasons, it’s hard to go back to more than just the last line and it has consequences like changing the hashes 😂
@firstname.lastname@example.org (#gyxy4ta) So that’s not too bad. But skimming over
Cache.FetchTwts(…) reveals that the cache isn’t touched when the parsing of the feed fails. Assuming that an invalid feed produces an error (might be wrong, didn’t investiage any further), the cache is not populated, triggering a fetch each time somebody visits the profile.
This is a quote text
(#qjwta3a) Yeah, seriously give Goryon/Yarn a try. For a relatively young app, on an also relatively young social media platform, it works beautifully well and ties in really well with the web experience.
I get that, but shouldn’t it only shorten @email@example.com and not @canine 🤔
Oh I see what you mean
@firstname.lastname@example.org gets shortened arguably incorrectly. Hmmm 🤔
I’ll have to look in to this, I know why this happens, but I guess we use the same
@nick@domain format, so it might be a bit tricky…
Also just FYI this thread (conversation we call them) got forked 😉