Searching We Love Privacy Club

Twts matching #yarnd
Sort by: Newest, Oldest, Most Relevant

(#zrsxk3a) @bender@bender I never implemented it actually. That’s why we have the # refresh = metadata field for those that yell loudly en …
@bender @twtxt.net I never implemented it actually. That’s why we have the # refresh = metadata field for those that yell loudly enough can add to their feeds. Otherwise yarnd uses WebSub between pods and is fairly dumb. I could never find an “intelligent” way to back-off without hurting freshness. ⌘ Read more

⤋ Read More

(#j3xacqa) @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 …
@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 pe … ⌘ Read more

⤋ Read More
In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

For point 1 and others using the metadata tags. we have implemented them in yarnd as [lang=en][meta=data]

⤋ Read More
In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

Yarnd can store password-protected keys without risk because pod owner don’t have password, but looks like i/someone should enter password for every message sent or receive? Upd: oh, it’s about ssh? i have key without password lol

⤋ Read More

(#u2ycerq) @kat It most certainly was us fucking around 🤣🤣 Turns out to be a side-effect of the way the Twt Subject extension is impleme …
@kat @yarn.girlonthemoon.xyz It most certainly was us fucking around 🤣🤣 Turns out to be a side-effect of the way the Twt Subject extension is implemented in yarnd and now apparently jenny 🤣🤣 Where it strips out the subject from the displayed/rendered content. Which is what you want… But oh well hah … ⌘ Read more

⤋ Read More

(#ot56hla) For the record; we consider the new authority on the Twtxt spec(s) going forward (has been for some years actually) to be implement …
For the record; we consider the new authority on the Twtxt spec(s) going forward ( has been for some years actually) to be implementers / primary maintainers of widely used clients. To date that is:

⤋ Read More

Hey this could be good news for self-hosters and folks that want to run their own yarnd? 🤔 Vultr is offering 1 vCPU, 500MB Memory and 10GB …
Hey this could be good news for self-hosters and folks that want to run their own yarnd? 🤔 Vultr is offering 1 vCPU, 500MB Memory and 10GB Storage for FREE! That’s right $0.00 🤣 Read more

⤋ Read More

(#gjl3gwq) @andros What do you mean by API? yarnd (which powers Yarn.social pods like twtxt.net) does have an API, however that API is desig …
@andros @twtxt.andros.dev What do you mean by API? yarnd ( which powers Yarn.social pods like twtxt.net) does have an API, however that API is designed for clients to interact with the pod and the user’s account and feed. e.g: there is a command-line client called yarnc and I used to maintain a mobile native app ( … ⌘ Read more

⤋ Read More
In-reply-to » For Example:

Are we talking about profile view heading, heading of posts or inline mentions?

Image


In yarnd I recall there is a setting for changing the heading of posts, but not for the two others as of yet.
I like the hover option for inline mentions. For the other places some like how yarnd does it in two line or “ nick (domain.tld) ” could also work.

⤋ Read More
In-reply-to » For Example:

I like the cleaness and indiewebness of using just domains for handles/shorthands similar to blusky, but the situations with more users on the same domain and that people in the fediverse (threads too?) are already familiar with the syntax speaks for webfinger. And since we already got support for webfinger in both yarnd and timeline it makes sense to stick with it.

⤋ Read More

**(#ptp2n7a) > Why is my @ mention is all over the place?

Just the way yarnd (my client) behaves, which I’m also refactoring and improving the …**

Why is my @ mention is all over the place?

Just the way yarnd (my client) behaves, which I’m also refactoring and improving the way mentions are expanded and auto-completed. ⌘ Read more

⤋ Read More

(#gctrz4q) > Alternatively, if you prefer yarnd to pretty-print all twts nicely, even ones from simpler clients, that’s fine too and you don�� …

Alternatively, if you prefer yarnd to pretty-print all twts nicely, even ones from simpler clients, that’s fine too and you don’t need to change anything. My ¼ -> ¼ thing is nothing more than a minor irritation which probably isn’t worth overthinking.

Yeah I’ve closed the PR, I just wanted to write it up and see what we all thought. Much easier to talk to a concrete spec proposal sometimes. … ⌘ Read more

⤋ Read More

(#gctrz4q) > What’s wrong with my original suggestion of doing the transformation before the text hits the twtxt.txt file? @prologic, I think …

What’s wrong with my original suggestion of doing the transformation before the text hits the twtxt.txt file? @prologic, I think it would achieve what you are trying to achieve with this content-type thing: if someone writes ¼ on a yarnd instance or any other client that wants to do this, it would get transformed, and other clients simply wouldn’t do the transformation. Every client that sup … ⌘ Read more

⤋ Read More

**(#gctrz4q) @falsifian Only that this rendering behavior comes from yarnd’s Markdown parser library that is used:

What has text/markdown go …**
@falsifian @www.falsifian.org Only that this rendering behavior comes from yarnd’s Markdown parser library that is used:

What has text/markdown got to do with this? I don’t think Markdown says anything about replacing ¼ with ¼, or other similar transformations. It’s not needed, because ¼ is already a … ⌘ Read more

⤋ Read More
In-reply-to » @prologic I'm not a yarnd user, so it doesn't matter a whole lot to me, but FWIW I'm not especially keen on changing how I format my twts to work around yarnd's quirks.

@bender@twtxt.net @prologic@twtxt.net I’m not exactly asking yarnd to change. If you are okay with the way it displayed my twts, then by all means, leave it as is. I hope you won’t mind if I continue to write things like 1/4 to mean “first out of four”.

What has text/markdown got to do with this? I don’t think Markdown says anything about replacing 1/4 with ¼, or other similar transformations. It’s not needed, because ¼ is already a unicode character that can simply be directly inserted into the text file.

What’s wrong with my original suggestion of doing the transformation before the text hits the twtxt.txt file? @prologic@twtxt.net, I think it would achieve what you are trying to achieve with this content-type thing: if someone writes 1/4 on a yarnd instance or any other client that wants to do this, it would get transformed, and other clients simply wouldn’t do the transformation. Every client that supports displaying unicode characters, including Jenny, would then display ¼ as ¼.

Alternatively, if you prefer yarnd to pretty-print all twts nicely, even ones from simpler clients, that’s fine too and you don’t need to change anything. My 1/4 -> ¼ thing is nothing more than a minor irritation which probably isn’t worth overthinking.

⤋ Read More
In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

@prologic@twtxt.net I’m not a yarnd user, so it doesn’t matter a whole lot to me, but FWIW I’m not especially keen on changing how I format my twts to work around yarnd’s quirks.

I wonder if this kind of postprocessing would fit better between composing (via yarnd’s UI) and publishing. So, if a yarnd user types ¼, it could get changed to ¼ in the twtxt.txt file for everyone to see, not just people reading through yarnd. But when I type ¼, meaning first out of four, as a non-yarnd user, the meaning wouldn’t get corrupted. I can always type ¼ directly if that’s what I really intend.

(This twt might be easier to understand if you read it without any transformations :-P)

Anyway, again, I’m not a yarnd user, so do what you will, just know you might not be seeing exactly what I meant.

⤋ Read More
In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

(#2024-09-24T12:34:31Z) WebMentions does would work if we agreed to implement it correctly. I never figured out how yarnd’s WebMentions work, so I decide to make my own, which I’m the only one using…

I had a look at WebSub, witch looks way more complex than WebMentions, and seem to need a lot more overhead. We don’t need near realtime. We just need a way to notify someone that someone they don’t know about mentioned or replied to their post.

⤋ Read More
In-reply-to » @prologic I wouldn't want my client to honour delete requests. I like my computer's memory to be better than mine, not worse, so it would bug me if I remember seeing something and my computer can't find it.

@prologic@twtxt.net Do you have a link to some past discussion?

Would the GDPR would apply to a one-person client like jenny? I seriously hope not. If someone asks me to delete an email they sent me, I don’t think I have to honour that request, no matter how European they are.

I am really bothered by the idea that someone could force me to delete my private, personal record of my interactions with them. Would I have to delete my journal entries about them too if they asked?

Maybe a public-facing client like yarnd needs to consider this, but that also bothers me. I was actually thinking about making an Internet Archive style twtxt archiver, letting you explore past twts, including long-dead feeds, see edit histories, deleted twts, etc.

⤋ Read More