Searching txt.sour.is

Twts matching #follows.
Sort by: Newest, Oldest, Most Relevant
github_blog
feeds.twtxt.net
 (3y ago)

More than meets the pull request: maintainers talk contributions
Creating an open source project can feel a bit like sending out an open invite to a party—will it be a roaring good time, or will you unbegrudginly dine on leftover junk food for the following week after nobody shows? When the first guest arrives, you breathe a sigh of relief. The party’s a success, […] ⌘ Read more

⤋ Read More
stigatle
yarn.stigatle.no
 (3y ago)

@carsten@yarn.zn80.net Yeah, I keep my account too - do not want to get rid of it, but I do not post much anymore there at all, just retweet stuff I find interresting. Also I’m so boring there that I get almost no followers and such, never got any traction there, even though I’ve been there since 2008. I write more here then there, and get more response here as well.

⤋ Read More
xuu
txt.sour.is
 (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.

We could ask them? But on the counter would bukket or jan6 follow the pure twtxt feeds? Probably not either way… We could use content negotiation as well. text/plain for basic and text/yarn for enhanced.

⤋ Read More
xuu
dev.txt.sour.is
 (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.

We could ask them? But on the counter would bukket or jan6 follow the pure twtxt feeds? Probably not either way… We could use content negotiation as well. text/plain for basic and text/yarn for enhanced.

⤋ 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
user/chunkimo
twtxt.net
 (3y ago)

Hi guys! My first ever Yarn post 😺 📦

I already think I am going to like this better than mastodon. My question is, is this federated… @support@twtxt.net ?? If so I am a lifer. Haha and I’ve been here 5 minutes 💖

I like to occasionally do some graphical artwork from time to time. For the first place to get all my art and other’s too check out XMPP at this address: xmpp:artwork@chat.toofast.vip?join

Another question, is this using markdown for markup? @thecanine@twtxt.net ?? Follow me back mateo! 😎

⤋ Read More
stigatle
yarn.stigatle.no
 (3y ago)
↳ In-reply-to » Q: Is anyone actually finding the activitypub experimental feature I've been working on (for those running main) actually useful? 🤔 (because I'm not and having second thoughts...)

@prologic@twtxt.net I like it, I get to follow some people I could not follow before, which I find useful.
But if you have second thoughts about it all - then I can understand that.
If you decide to pull the plug on it - then I’ll just get some additional activitypub service installed on my server and use that for that (I was thinking about installing this: https://github.com/tsileo/microblog.pub ) if needed.

⤋ Read More
newest_python_peps
feeds.twtxt.net
 (3y ago)

PEP 710: Recording the provenance of installed packages
This PEP describes a way to record the provenance of installed Python distributions. The record is created by an installer and is available to users in the form of a JSON file provenance_url.json in the .dist-info directory. The mentioned JSON file captures additional metadata to allow recording a URL to a :term:`distribution package` together with the installed distribution hash. This proposal is built on top of PEP 610 following :ref:`its corresponding canonical PyPA spec … ⌘ Read more`

⤋ Read More