@bender@twtxt.net A: Yes

@bender@twtxt.net Yup! It maybe should try to detect a pipe maybe too?

And yes @bender@twtxt.net pods will reintroduce old root Twts like this back into active caches 🤣 Just not the ones in/between (old replies)

Funny how well shit works that we’ve collectively built 🤣

@jdtron@tilde.team As did I 🤣

@bender@twtxt.net Haha 😝

@bender@twtxt.net LOL 😂 I tried to even read the blog post, but I couldn’t. In all bluntness and honestly the layout and style of the website is total garbage, not to mention it’s written in a language I cannot read, but because it’s just so poorly written the translation service can’t translate it properly 🤦‍♂️ So point across FAIL

@bender@twtxt.net What is?! 😆

@lyse@lyse.isobeef.org Ahh yea! I’ll setup some CD for it this weekend 👌

@bender@twtxt.net Hmmm? 🤔

@movq@www.uninformativ.de

If you all were to clear your caches, would your clients fetch archived feeds?

No.

And I’m also thinking of nuking my pod at some point and starting over. But maybe after we refactor a few important things.

@bender@twtxt.net I think it comes down to one of the principles Yarn.social was founded on, which is to say, users should have choices and what they “see” is not driven by “algorithms”. The “Discover” view in and of itself has utility/value to others, and is otherwise just a “view” of a pod’s cache, but I agree with you. It was even getting noisey for me 🤣

@aelaraji@aelaraji.com Unofficially yarn supports the type field

Meg https://feeds.twtxt.net/slashdot/twtxt.txt

@aelaraji@aelaraji.com Probably not? https://dev.twtxt.net/doc/metadataextension.html

@aelaraji@aelaraji.com Same to you!

In other words, there isn’t anything specifically wrong with the Twtxt spec (+extensions), but if you for example use a client and server combination that never considered the User-Agent header and check logs or intercept requests for your feed, than you end up missing an important part of the whole flow (unless you are of course deliberating ignoring that, e.g: 1-way feeds, news feeds, etc).

In my opinion, this can all be solved by a “better standard client”.

For example I noticed in this thread, someone, me, and you, and now it’s just a bad @-mention mentioned Soren Peter with a bad link :/

This also just reminds me of the other problems that exist:

• bad mentions.
  
• knowing whether someone will you’ve @-mentioned will even see your reply at all.

@mckinley@twtxt.net I think we just need a way of surfacing this information better for both users and operators? 🤔

@mckinley@twtxt.net I did!

@mckinley@twtxt.net Yeah this is what was being “cleaned up”

Yo be honest I don’t think there is a good solution IMO

You’re right we should
never be like Microshit 😆

@mckinley@twtxt.net I think “posting to the void” was/is a poor choice of words hete.

Today in the news

Microsoft is a security risk

@slashdot@feeds.twtxt.net Oh boi! 😆 Gotta take a screenshot of this in case Microsoft demand the article be taken down 🤣

@dfaria@twtxt.net Also, I don’t really care whether you continue to use my pod or not frankly.

One more reason not to use https://twtxt.net/

negative comments like this are completely unconstructive and have no basis in merit. If you have issues with the way I administer my pod, speak up, provide alternatives. If you have good technical suggestions for Twtxt/Yarn, we’re all ears. We are only trying (or attempt to try) to make things better for all, which as you can appreciate is a hard thing to do.

Next time, please leave your constructive criticisms at home. No-one forces you to use my pod (for free).

Oh never mind! 🤦‍♂️ That’s your other feed that you syndicate some stuff to? 🤔 Research?

@dfaria@twtxt.net And btw, even if I block a feed or whole domain, it doesn’t stop you from following. it just removes it from the “Discover” view.

@bender@twtxt.net +1

@dfaria@twtxt.net And here I thought you never or we’re not capable (client?) of interacting with other users? 🤣

@lyse@lyse.isobeef.org Same 😢

@eapl.me@eapl.me We went out for nice breakfast and put the camper trailer away 😅

@mckinley@twtxt.net Yeah pretry by hand at the moment.I only backup what I cannot reproduce.

@mckinley@twtxt.net I use Restic and backup to another machine on my network as well as Backblaze B2

@sorenpeter@darch.dk Good points 👌

@lyse@lyse.isobeef.org This ☝️

@lyse@lyse.isobeef.org Thanks! 🙇‍♂️

@mckinley@twtxt.net Do you have an alternate proposal? What we want to avoid really (if possible) is the idea of “1-ay posting” or “posting to the void”. As an obvious example, the idea of syncing your Mastoon toots to Twtxt twts that you never see replies to is well umm just silly 🤣 and thus creates unwanted noise as it’s just like talking to a “brick wall” 😥

@rrraksamam@twtxt.net You must live in the southern hemisphere? 🤔 It doesn’t ever snow here in Brisbane 🤣

@bender@twtxt.net This is what I fell over and bunged up my shin 😱

@test@aelaraji.com Looks fine to me? 🤔

@bender@twtxt.net LOL no 🤣

6x4 Medium Duty Smooth Floor Box Trailer For Sale Brisbane good lightweight trailer 😅

@aelaraji@aelaraji.com No worries! We can work this out, Unicode is hard™ at the best of times 🤣

@xuu Like it’s pretty easy to use really:

prologic/go-htmx-demo: A simple Web App written in Go using htmx on the frontend to drive a single-page-app (SPA) experience. - go-htmx-demo - Mills

@aelaraji@aelaraji.com Can you perhaps setup a temporary/test feed, link me and let’s debug this together? Maybe it’s a bug in Jenny? 🤣

@aelaraji@aelaraji.com The only thing I’ve observed so far is your server isn’t setting a charset. e.g:

$ curl -v -o /dev/null https://twtxt.net/~prologic/twtxt.txt 2>&1 | grep 'content-type'
< content-type: text/plain; charset=utf-8

@aelaraji@aelaraji.com I’ll inspect your feed later and see if I can work out wtf is going in 🤣

@xuu How about we just refactor the existing UI with it? 🤔