@funbreaker@twtxt.net Looks legit 👌

@shreyan@twtxt.net I am actually seriously considering forking the spec and putting this to the community.

One of the motivating reasons to do this (besides to avoid the continued hostility) is we don’t share the same goals or visions.

Decentralized microBlogging is for all (not just retro enthusiasts and hackers)

@shreyan@twtxt.net It honestly means nothing. It’s like 12-factor apps 😆

@lyse@lyse.isobeef.org Nice! 👌 What species of bird is that? Crow or Raven?

Nice 👌

@stigatle@yarn.stigatle.no I’m yhe movile app we default to https:// if no scheme was provided by the user.

@xuu Devils advocate: what value would be really be providing here? Would, for example @lyse@lyse.isobeef.org and/or @movq@www.uninformativ.de switch to following the new Uarn feeds or stick with the truncated unmarked up and out-of-context pure twtxt feeds?

@funbreaker@twtxt.net Why not 🤗

@lyse@lyse.isobeef.org Yeah we can do someyhing similar for the crawler 👌

He is following an archived feed for some reason 😆

@lyse@lyse.isobeef.org Yup this is on you 😆

@screem@yarn.yarnpods.com Just sign it out 😆

@movq@www.uninformativ.de Wow 😳 That is quite magical 🙇‍♂️

Is there a bug in yarnd here?

@shreyan@twtxt.net I love where you’re going with this 😆

‘You Just Lied’: Elon Musk Slaughters BBC Reporter In Live Interview - YouTube As much as I don’t hold a very high opinion of Elon Musk (and to be fair I don’t actually know him all that well, only what I’ve read about him and observed), this particular video however is quite hilarious. This (ignoring the Twitter™ nonsense) is hilariously funny and quite on point. “Who decides whether its misinformation anyway?” And “You can’t even provide one example” Haha 🤣

PS: Don’t read too much in my posting this 😅

RackMac mini 1U Rack Enclosure for Mac mini - Sonnet – If you’re ever in need of rack-mounting up a pair of Apple™ Mac Mini(s), these look pretty cool 👌

@marado@twtxt.net ++ 💯

@drewdevault@fosstodon.org Fine by me 👌

Really getting quite tired of all this Kubernetes Cloud Native projects in my GitHub feed 🤦‍♂️

🤣🤣🤣

@stigatle@yarn.stigatle.no That is simply gorgeous! 👌 😍

Yeah the argument is pretty flawed when authors can pretty much write whatever content they like including gibberish, XML, HTML or even Binary 😆

Yeah remember that the extensions we built as a community didn’t come out of thin air 😆 We did our research and studied the ecosystem that was 👌

@stigatle@yarn.stigatle.no No no it’s not 🤦‍♂️

@stigatle@yarn.stigatle.no I posted an alternative link here

Good call 😆

@shreyan@twtxt.net Thanks for your encouraging words 🤗

I also agree that buckket’s twtzt dlient makes a terrible Yarn client – I would even go so far as to say it’s not very well maintained either as it has been broken for some time 😢

Yes we can raise a PR against the original reference client – But I’m not convinced it’ll get accepted 😢

@xuu@txt.sour.is Yeah I agree changing or detracting from the underlying Twtxt format we use would ruin our other hard work 😢 Like Salty.IM 👌

@xuu@txt.sour.is Yeah this is a great idea👌 I was just thinking of the storage format and what clients would fetch as a resource 🤔

@marado@twtxt.net Ahh good point, or with a --? I sometimes try to separate different paragraphs or points with a -- instead of a new line / paragraph break. I don’t mind either way, but will amend the PR later when I get back from the tournament, unless you’d like to make the suggested change and I’ll just accept it? 🙏

Competing in a handicap (Easter handicap tournament) table-tennis 🏓 today 😅 I hope I do better than last year’s Xmas handicap 🤣

here’s the 1-line patch: https://github.com/buckket/twtxt/compare/master…prologic:twtxt-1:patch-1 (untested)

But as you say, if you don’t find it useful, don’t like it, or whatever, simply don’t follow it.

Also whilst I understand the appeal of curl url | less to read a feed, I find this a terrible user experience in the first place, yes it should be possible to use UNIX text manipulation tools for feeds, which is why using Twtxt as the “spec” and “transport” of the content is so ideal. – Should you read feeds this way primarily? Probably not.

@marado@twtxt.net Yup I completely agree. 💯 @lyse@lyse.isobeef.org has significant bug fixes for buckket’s original twtxt client, including support for multi-lines (\u2028), I suppose anyone (even I) could put up a PR that addresses that, it’s a trivial 1-line patch.

As for your very positively written position and point, absolutely 100% 👌 The fact that some folks write cryptic posts to their Twtxt feed (e.g: the feed that posts geospatial coordinates updates and a status of some reading off a device), or some other formats (rare, but do exit), plain text, Markdown or HTML are all attributes of what the author chooses to write. Probably the only form that would be quite hard to cope with manually would be XML/HTML 🤣

Hmmm

Recently (research and documentation begun in 2007) I have had sufficient experience with a variety of different types of trolls on the internet (in communities, email lists, wikis, and news stories) that it seemed useful to document, categorize, classify, and provide methods for dealing with each type, towards the goal of identifying and defeating trolls as quickly as possible in the interest of creating and maintaining PositiveCommunities.

May be something good to learn from here 🤔👌

Son in theory we could have a yarn.txt feed and a stripped-down and limited twtxt.txt feed. But I am 98% convinced this wouldn’t solve any of the perceived problems, actually I’m 100% certain. Mostly because there are no offered solutions, no actionable feedback, no contributions, just complains and arguments.

@marado@twtxt.net See, even if we (for example) did something to change the behaviour of yarnd such that it:

1. produced a twtxt.txt feed that stripped \u2028 so all posts are single-line.
   
2. converted Markdown to “plain text”
   
3. limited posts to 140 characters
   

Would this make few that scream and shout the loudest happier that Yarn is more properly using Twtxt? 🤔 Would Yarn then be considered to be using Twtxt as-it-is/was intended? 🤔

Of course this would have the side effect of:

• Your longer posts would now be truncated and meaningless.
  
• Posting links to images would no longer work.
  
• Threading would no non-existent.
  

And so we’re back to square one, where Twtxt as-it-was-is intended is a spec that whilst on its own useful for a very limited number of use-cases it lacks certain features that make microBlogging and interacting with others viable.

The problem of course is the position this forces me in to, with all of this “nonsense”, means you end up having so many different competing specs and protocols that you end up in exactly the position we’re in now with “chat”:

where none of them work with one another and there’s no effective bridging, data or identity portability.

Here’s an alternative link: https://gist.github.com/prologic/16a88f1ebbd3d13e4cc6352615919b87

@marado@twtxt.net Yeah it would be possible to have “bridges” just like I think we should have a bridge finally for Twtxt<->ActivityPub. The motivation behind this proposal/idea is to get away from the trolls and hostility of Twtxt. Its of course too late to change what we did in the past (nearly getting on 3 years now), but trying to find ways to deal with this going forward…

@marado@twtxt.net Working for me?

=> https://files.mills.io/download/Twtxt%20IRC%20Logs%202023-04-14.md

tantek / TrollTaxonomy

Blah I forgot Avatar, but that could be icon I guess or image.

An example feed would look like this:

{
    "name": "prologic",
    "desc": "\"Problems are Solved by Method\" 🇦🇺👨‍💻👨‍🦯🏹♔ 🏓⚯ 👨‍👩‍👧‍👧🛥 -- James Mills (operator of twtxt.net / creator of Yarn.social 🧶)",
    "key": "kex17m00vqjduqlf6j5xcvtpyhk2zg3shv2x8r5qzyancjlhgl4ytj8slvt7h0",
    "links": [
        {
            "title": "My CV",
            "href": "https://prologic.shortcircuit.net.au/"
        }, 
        {
            "title": "My Projects",
            "href": "https://git.mills.io/prologic"
        },
        {
            "title": "My Github profile (@prologic)",
            "href": "https://github.com/prologic"
        }
    ],
    "items": [
        {
            "id": "https://yarn.mills.io/permalink/xt2mrjwfmwlh6xrcoom7ywpmg6hdrduy56cvzjoi76ibdjjiycwa",
            "hash": "xt2mrjwfmwlh6xrcoom7ywpmg6hdrduy56cvzjoi76ibdjjiycwa",
            "sig": "3vdKTvI_WGDcM_cUUPGmWHPFpZ9IpORgFkhVFndcxbuUm3XF2w895nEvh2CIA0P3OekfmW6pWQP4wSsXZSCMAA",
            "format": "text/markdown",
            "time": "2023-04-16T11:04:28+10:00",
            "content": "Hello World"
        }
    ]
}

💡 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

I found myself wanting to upload a Markdown document (IRC Logs) today to my pod. This has come up as a feature request before, should we do this soon™? 🤔 Would anyone else find it useful to upload and link to other types of files besides “multimedia”? 🤔

Here you go: https://files.mills.io/download/Twtxt%20IRC%20Logs%202023-04-14.md

Arggg “Forbidden” 🤦‍♂️

@stigatle@yarn.stigatle.no Does this work? 🤔 https://www.irccloud.com/log-export/160242/irccloud-export-110340-2023-04-16-09-41-27.zip