@andros@twtxt.andros.dev Yes 🙌
Business trips / Off-Sites can be rather exhausting 😴
Yes
@xuu@txt.sour.is Nice! 👍
@movq@www.uninformativ.de This is pretty good, love the music 🎶 Haha 😆
@xuu@txt.sour.is Got a sample to show/share? 🤔
Kind of catchty 😄
@movq@www.uninformativ.de Bahahahahaha 😂
@xuu@txt.sour.is Oh wow! Thank you ! 🙏 And yeah even at 2x it sounds good enough to comprehend 🤣
@movq@www.uninformativ.de apparently very hard 😆
@movq@www.uninformativ.de I’d have to hear it to get it 🤣
@eapl.me@eapl.me@eapl.me
for me, which then gets eaten as two mentions, probably matching twice against my following list?
(#uavwuqq) @eapl.me@eapl.me@eapl.me@eapl.me Nah, my pod seems to have the correct URL 🤣
yarnd
pods that form a "distributed network".
@xuu@txt.sour.is Yeah looks like an edge case. Because of the way he announces his preferred nick in the feed the “Reply” button spits out @eapl.me@eapl.me@eapl.me
for me, which then gets eaten as two mentions, probably matching twice against my following list?
@eapl.me@eapl.me@eapl.me@eapl.me I replied in the fork, but essentially there’s no reason we can’t support two different models here. We already do this anyway with numerous single-user, single hosted and managed feeds + a bunch of multi-user yarnd
pods that form a “distributed network”.
@eapl.me@eapl.me@eapl.me@eapl.me I think the general idea that we’re settling on here is that maybe we can build a simple solution to this whole “wtf is this hash?” problem. yarnd
already forms a sort-of “distributed network” amongst its peers and whilsts uses Twtxt (of course) is both decentralised and distributed. Nothing wrong with that. – I tried to build a search engine and crawler, but getting that resource efficient and useful is hard™.
So if we can have a small network of participating members of the community forming a “distributed network” of the Twtxt™ space, we can solve this problem quite easily. We could even put some GeoDNS routing in place and a single A record/domain to make things even easier. Let’s call it s “Registry Service” if you will :)
@movq@www.uninformativ.de Same 😢
@andros@twtxt.andros.dev What a nice thing to say 🙇♂️
@andros@twtxt.andros.dev Would it help if I documented the two protocols that yarnd uses today for this “distributed network”? 🧐
@andros@twtxt.andros.dev Simple enough 👍
@eapl.me@eapl.me@eapl.me@eapl.me I don’t think there’s anything wrong with an optional distributed network with participating members of the community. As long as it’s optional.
@andros@twtxt.andros.dev this is actually already achieved with yarnd
@eapl.me@eapl.me@eapl.me@eapl.me So what was the definition of a web log back in the day? 🧐
@bender@twtxt.net Me neither 🙌
@lyse@lyse.isobeef.org Ita more so that with enough data you start to need an index
@andros@twtxt.andros.dev I agree 💯
@kat@yarn.girlonthemoon.xyz We missed you too 🤗
You’re all wrong 😑 @anth@a.9srv.net will happily tell you (hopefully) that we’ve been doing this whole “microblogging” / “status update” thing decades earlier than anything you’ve ever seen in the form of finger
🤣 and “plan” files 😅
@kat@yarn.girlonthemoon.xyz Yeah okay, I’ll see if I can reproduce this silly nonsense version string 🤣 cheers! 🍻
@andros@twtxt.andros.dev Yeah I think @xuu@txt.sour.is has built some interesting stuff around this? 🤔
@andros@twtxt.andros.dev I’m not entirely sure what this means:
development that requires a database
Obviously I wasn’t in the discussion so I feel like I’m missing some context here 🤔
@doesnm@doesnm.p.psf.lt Actually that’s a fantastic idea 🙌
@eapl.me@eapl.me@eapl.me@eapl.me No worries 🤗 My emotionally state are my own to sort out 🤣
@kat@yarn.girlonthemoon.xyz Welcome back! 🙌
@kat@yarn.girlonthemoon.xyz Actually that’s’ a known bug I haven’t worked out yet hmmm 🧐
@kat@yarn.girlonthemoon.xyz Arw you running make build or go build?
@lyse@lyse.isobeef.org I also think we need to remove ourselves a bit from the “Twtxt” format as it was originally designed by Buckket.
The beauty of twtxt is, you put one file on your server, done. One.
I’m not talking (nor ever was here) about that. We should be allowed to and encourage dot evolve its usage and our own.
It would be far better as a community to focus on the utility of our tools, services, protocols, formats and specifications as well as our own clients and usages thereof rather than this “idealised” design from © 2016.
If you strongly disagree with this, then I think I’ll just honestly step away from all of this as the back ‘n forth on this whole “beaty” and “simplify” argument is honestly wearing me down 😢
@lyse@lyse.isobeef.org Sorry I didn’t mean to upset you or anyone here in the community. I am/was merely trying to solve what I perceive to be a problem and an ask in the community:
How do I know what a hash refers to?
I believe the reason for this stems from a curiosity of the user of whether they might find that thread interesting or whether there are new interested feeds to follow?
Although my idea increases complexity slightly (introducing a new concept) I don’t think it’s particular hard to understand, reason about or implement (complicated). One could even even make the implementation quite simple in fact.
Either way, the idea of a service (cantralised) or participating clients/registries (distributed) providing reverse hash lookups doesn’t sound too bad really.
What do you propose to solve the above problem? 🤔
One of the biggest gripes of the community with the way the threading model currently works with Twtxt v1.2 (https://twtxt.dev) is this notion of:
What is this hash?
What does it refer to?
Idea: Why can’t we all agree to implement a simple URI scheme where we host our Twtxt feeds?
That is, if you host your feed at https://example.com/twtxt.txt
– Why can’t or could you not also host various JSON files (let’s agree on the spec of course) at https://example.com/twt/<hash>
? 🤔
That way we solve this problem in a truly decentralised way, rather than every relying on yarnd
pods alone.
@unexplained_mysteries@feeds.twtxt.net Interesting article on the philosophy of thougjts 🙌
We’ve now had centimeters of rainfall in the last 24hrs 😱
– Yesterday afternoon the local creek near us had already gone several inches over the footbridge too! 😱😱
@emmanuel@wald.ovh That’s not good mate 😢 Hope you’re feeling better? 🤗
So… Cylone Alfred made landfall (whatever that means) last night, and I watched it hit my wife’s Uncle/Aunt’s place on one of the outer islands, then move westwards and sort of fizzle out. It’s now been downgrade to a “Tropical Low” (I guess not good enough for a Cat X anymore?), but we’re still in the Eye of it, and there’s still a swirling mass of winds (just not as fast). Now we get to look forward to flooding 🤣
@andros@twtxt.andros.dev I think you’ve done an amazing job of this client 🙌