Searching yarn

Twts matching #http
Sort by: Newest, Oldest, Most Relevant
abucci
anthony.buc.ci
 (3y ago)
↳ In-reply-to » an interesting observation in a post twitter reality is how services that are sprouting up to claim some of the refugees are setting themselves up as closed gardens. without the option to federate with other services. like spoutable, counter.social, post, clubhouse and such.

@xuu@txt.sour.is this is alarmingly catchy

⤋ Read More
abucci
anthony.buc.ci
 (3y ago)
↳ In-reply-to » an interesting observation in a post twitter reality is how services that are sprouting up to claim some of the refugees are setting themselves up as closed gardens. without the option to federate with other services. like spoutable, counter.social, post, clubhouse and such.

@xuu@txt.sour.is everyone’s moving to gated communities!

⤋ Read More
carsten
yarn.zn80.net
 (3y ago)

Started with

a concept sketch of a full body end-time factory worker on a distant planet, cyberpunk light brown suite, (badass), looking up at the viewer, 2d, line drawing, (pencil sketch:0.3), (caricature:0.2), watercolor city sketch,
Negative prompt: EasyNegativ, bad-hands-5, 3d, photo, naked, sexy, disproportionate, ugly
Steps: 20, Sampler: Euler a, CFG scale: 7, Seed: 2479087078, Face restoration: GFPGAN, Size: 512x768, Model hash: 2ee2a2bf90, Model: mimic_v10, Denoising strength: 0.7, Hires upscale: 1.5, Hires upscaler: Latent

⤋ Read More
movq
www.uninformativ.de
 (3y ago)
↳ In-reply-to » @darch I think having a way to layer on features so those who can support/desire them can. It would be best for the community to be able to layer on (or off) the features.

@xuu@txt.sour.is @prologic@twtxt.net Yarn.social without threading (as it would be the case in a “truncated” feed) does not make sense to me.

Put another way: Yarn.social is not twtxt. The content that we all have in our feeds really is much closer to a web forum or usenet or whatever. It’s threaded conversations. twtxt, as I believe it was originally intended, are short little status updates – that’s it. The formats of Yarn.social and twtxt might be very similar, but the content is vastly different and, in a way, incompatible. (As such, I think I understand very well that the original twtxt crowd is disgruntled.)

That proposed truncated feed doesn’t really provide any value, if you ask me. 🤔 It’d just be chaotic.

⤋ Read More
abucci
anthony.buc.ci
 (3y ago)
↳ In-reply-to » 👋 Q: How do we feel about forking the Twtxt spec into what we love and use today in Yarn.social in yarnd, tt, jenny, twtr and other clients? 🤔 Thinking about (and talking with @xuu on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or "Yarn". Compatibility would remain with Twtxt in the sense that we wouldn't break anything per se, but we'd divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don't use, contribute in the first place or fixate on nostalgia (which doesn't really help anyone).

@darch@neotxt.dk yes!

⤋ Read More
abucci
anthony.buc.ci
 (3y ago)
↳ In-reply-to » On LinkedIn I see a lot of posts aimed at software developers along the lines of "If you're not using these AI tools (X,Y,Z) you're going to be left behind."

@prologic@twtxt.net yeah. I’d add “Big Data” to that hype list, and I’m sure there are a bunch more that I’m forgetting.

On the topic of a GPU cluster, the optimal design is going to depend a lot on what workloads you intend to run on it. The weakest link in these things is the data transfer rate, but that won’t matter too much for compute-heavy workloads. If your workloads are going to involve a lot of data, though, you’d be better off with a smaller number of high-VRAM cards than with a larger number of interconnected cards. I guess that’s hardware engineering 101 stuff, but still…

⤋ Read More
abucci
anthony.buc.ci
 (3y ago)
↳ In-reply-to » 👋 Q: How do we feel about forking the Twtxt spec into what we love and use today in Yarn.social in yarnd, tt, jenny, twtr and other clients? 🤔 Thinking about (and talking with @xuu on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or "Yarn". Compatibility would remain with Twtxt in the sense that we wouldn't break anything per se, but we'd divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don't use, contribute in the first place or fixate on nostalgia (which doesn't really help anyone).

@prologic@twtxt.net I would politely suggest again that we not react to people with bad attitudes who talk shit about yarn. If twt is forked, it should be forked to add features that are otherwise not possible. Not to appease people who will probably never be appeased.

⤋ Read More
prologic
twtxt.net
 (3y ago)

👋 Q: How do we feel about forking the Twtxt spec into what we love and use today in Yarn.social in yarnd, tt, jenny, twtr and other clients? 🤔 Thinking about (and talking with @xuu@txt.sour.is on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or “Yarn”. Compatibility would remain with Twtxt in the sense that we wouldn’t break anything per se, but we’d divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don’t use, contribute in the first place or fixate on nostalgia (which doesn’t really help anyone).

⤋ Read More
prologic
twtxt.net
 (3y ago)

💡 Quick ‘n Dirty prototype Yarn.social protocol/spec:

If we were to decide to write a new spec/protocol, what would it look like?

Here’s my rough draft (back of paper napkin idea):

  • Feeds are JSON file(s) fetchable by standard HTTP clients over TLS
  • WebFinger is used at the root of a user’s domain (or multi-user) lookup. e.g: prologic@mills.io -> https://yarn.mills.io/~prologic.json
  • Feeds contain similar metadata that we’re familiar with: Nick, Avatar, Description, etc
  • Feed items are signed with a ED25519 private key. That is all “posts” are cryptographically signed.
  • Feed items continue to use content-addressing, but use the full Blake2b Base64 encoded hash.
  • Edited feed items produce an “Edited” item so that clients can easily follow Edits.
  • Deleted feed items produced a “Deleted” item so that clients can easily delete cached items.

#Yarn.social #Protocol #Ideas

⤋ Read More