@aelaraji@aelaraji.com Haha don’t ask me 🤣 I don’t do PHP 😆
It’s nice to see we’re all largely thinking along the same lines. e.g: Salty.im 😅
@eapl.me@eapl.me Yeah this is true. Previously RSA and AES were more common. These days Salsa and Chacha and Curve are fairly prevalent. For example all the Wireguard stuff uses Curve25519 / Ed25519 crypto. Signal uses very similar crypto too, but with some very nice double ratcheting 3DH.
twtxt
(for now), although I see the community could be interested in.
@eapl.me@eapl.me I -think we’ve gotten use to it somewhat 🤣
@doesnm@doesnm.p.psf.lt whilst technically true, expensive and unnecessary.
@doesnm@doesnm.p.psf.lt I always do 👌
👋👋 Reminders that this weekend our monthly Yarn.social online meetup. Who’s coming? 🤔 Some possible topics:
- Direct Messaging for Twtxt
- @prologic@twtxt.net ’s new EdgeGuard services 🤣
- What’s the weather like? 👍
Details:
- When: 25th Jan 2025 at 12:00PM UTC (midday)
- Where: https://meet.mills.io/call/Yarn.social
twtxt
(for now), although I see the community could be interested in.
@eapl.me@eapl.me@eapl.me@eapl.me But we’re actively discussing on Twtxt 🤣
[0]
). A syntax like the following could help to know what public key you used to encrypt the message, and which private key the client should use to decrypt it:
@eapl.me@eapl.me@eapl.me@eapl.me Agree with the base64 encoding 👌
@eapl.me@eapl.me@eapl.me@eapl.me actually it is easy 🤣 It’s now the standard for SSH keys 😆
@aelaraji@aelaraji.com Hmmm? 🤔
@xuu@txt.sour.is Is this because there’s a bug in persisting trusted peers? 🤔
@lyse@lyse.isobeef.org This is a good point.
@doesnm@doesnm.p.psf.lt That’s actually not true, because you’d have to know the target you’re interested in, in the first place. Inboxes in Salty.IM are deliberately shahed for this reason. So whilst you may know your own inbox address, etc, I (as an arbitrary bad actor) wouldn’t easily be able to guess (let alone brute force) my way to another inbox address of an interested party.
@xuu@txt.sour.is Can you elaborate in textual form for the poor vision impaired developer 🤣 🙏
It would also be great if you put up a PR against twtxt.dev 🙏
@andros@twtxt.andros.dev My only comment so far is to use Ed25519 keys for crypto.
@bender@twtxt.net planning on being around in 10 years 🤔 😅
Multihull of the year Winner: 2024 ILIAD 53F Power Catamaran Yacht Tour - YouTube👈 Really loving this Multihull Power Catamaran 👌 Very nice yacht! 🛥️
@kat@yarn.girlonthemoon.xyz Do you want to stand it up on your own or use it as a service? 🤔🤔
@kat@yarn.girlonthemoon.xyz sounds intriguing 🤔
EdgeGuard Update:
I am now in a position where I’m no longer having any ports open on my firewall at the Mills DC. 🥳 All services (Gopher, SMTP, IRC, SSH, HTTP) are being proxied through my edge network 💪
@xuu@txt.sour.is Speaking of TV Shows, can anyone recommend anything good of late? Hmm 🤔
@doesnm@doesnm.p.psf.lt Hmmm yhe flow doesn’t look right to me hmm 🤔
@doesnm@doesnm.p.psf.lt Is that implementing IndieAuth? 🤔
@bender@twtxt.net Aye aye 🙌
Would anyone object to the feeds.twtxt.net service having auth soon™ ? 🤔 I’m tired of the garbage feeds that it has accumulated over tie (spammers) and I want to a) clean it up b) lock it down somewhat.
The idea would be that you’d login with your Yarn.social account on some pod you control/operate or share with a nice person 🤣 – For those unfamiliar, this is called IndieAuth or IndieLogin. ALL Yarn.social pods are in fact valid (have been for years now) IndieAuth Providers. So I can just ust that. This also technically means you could login with your own domain too (more on that later…)
@hacker-news-newest@feeds.twtxt.net TL;DR:
The author recounts their experience with a “no calls” policy in enterprise sales, finding it surprisingly effective. They attribute this success to addressing common reasons for calls—lack of understanding, onboarding issues, pricing uncertainty, and trust concerns—through clear messaging, self-serve onboarding, transparent pricing, and robust security documentation. While acknowledging potential limitations, the author advocates for a #nocalls approach, emphasizing the benefits of efficiency and alignment with their values.
@lyse@lyse.isobeef.org Who does right 🤣 I wonder if anyone read the ToC(s) of any Yarn pod? 🤔
@news-minimalist@feeds.twtxt.net Ahh now I like to read news like this in my feed. THis is perfect! 🤩 Thank you @bender@twtxt.net and so far this is such a nice quite way to be “informed” without the noise and sensational crappy clickbait shit™
@kat@yarn.girlonthemoon.xyz Evening 👋
@arne@uplegger.eu True! 👌👌
@kat@yarn.girlonthemoon.xyz I also happen to use it to run https://mbox.blue as well as to front SSh access to https://git.mills.io 👌
@arne@uplegger.eu To be honest I don’t really understand why anyone would use Facebook™, X/Twitter™, TikTok™ Instagram™, etc… When it clearly states in their Terms of Conditions that the content you “enter” into their systems, is NOT yours.
@kat@yarn.girlonthemoon.xyz That was https://git.mills.io/prologic/sshbox
@aelaraji@aelaraji.com Fuck sorry!
@andros@twtxt.andros.dev Created. Can you try logging in via Github? I had to take a stab/guess at your Email address, which is very clearly wrong, but hopefully you an just update it when you login 🤣🤣
Actually. it’s probably fine if you just drop your Github username/profile here. They’re all public info anyway 🤣🤣
@andros@twtxt.andros.dev I believe I disabled new registrations by default due to increase in levels of “spam accounts”. If you could email me, or DM me (IRC) your Github username, I’ll add an account for you that matches your Github profile and you can sign-in that way.
Respectfully, I will not move any of my projects back to Github after this blog post; hope you can understand, but I’d prefer to stick to my moral values here as much as I can 😅
@kat@yarn.girlonthemoon.xyz Any ideas of the volume coming out of their RSS feed? 🤔
@kat@yarn.girlonthemoon.xyz Now you just need to front this with sshbox and protect your precious little SSh resource 💪
@xuu@txt.sour.is Haha 🤣🤣🤣
@bender@twtxt.net Yeah I think I follow the Hacker News top N feed already. So taht’s fine.
Well it imported nicely into the feeds service, so I’ll give it a try 👌
@kingdomcome@yarn.girlonthemoon.xyz Hey 👋 Ya know, working, etc 🤣
@bender@twtxt.net What’s the other ?🤔
@bender@twtxt.net And you use this as your primary news sources? 🤔
Hmm I think I’m hitting another false positive rule 😢
@bender@twtxt.net Thanks! 🙏 Will look into it!
@bender@twtxt.net I still haven’t fixed that rendering sorry 🤣
I need an alternative news source… Something I can shove into feeds.twtxt.net that helps me keep up-to-date with Tech and other important news 🗞️ Hmmm 🤔 Suggestions? I can’t stand Slashdot anymore since they’ve decided to come down hard on ad-blockers 🤦♂️
@lime360@lime360.nekoweb.org Down at the moment due to hardware failure of one of my nodes. I have the spare parts to bring it back online, just need to find the time 😅 Sorry for the inconvenience, I just can’t afford to run the search engine right now on the remaining two nodes 😢😢
@bender@twtxt.net Hmmm? 🤔
@xuu@txt.sour.is Not recently, no. Why?
@arne@uplegger.eu Welcome! 🤗
@andros@twtxt.andros.dev How about #yarn.social
🤣
I’ve decided (finally) to unfollow the Slashdot feed and no-longer bother ever visiting the site or read any of it’s content. Why? Because Slashdot in their infinite wisdom have decided to employ tactics that make it difficult to use their site without ad-blokers:
This page could not be loaded properly due to incorrect / bad filtering rule(s) of adblockers in use. Please disable all adblockers to continue using the website. (click OK if you’d like to learn more)
I can respect this; but I can also just as easily choose never to visit your site again.
I just blocked 52.169.40.38/32
an ip from the microsoft asn(network) a single ip responsible for dosing a bunch of really old web servers i used to have about ~15 years or more ago 🤦♂️ ive sent microsofts abuse contact another email. my gawd 🤣
@andros@twtxt.andros.dev Yes! 🙌 https://git.mills.io/yarnsocial/twtxt.dev
@andros@twtxt.andros.dev Reminds me of another low-code platform I came across that is written in Go, but uses Starlark I think as the DSL for writing apps.
@andros@twtxt.andros.dev It’s a Cloud/SaaS thing right? 🤔🤔
@andros@twtxt.andros.dev What is Streamlit? Link?
Morning 🥱
@lyse@lyse.isobeef.org Just watched this too! Not too bad 👌
I am now fully off Cloudflare 🥳
@shreyan@twtxt.net Yeah the guy seems quite mad and hell bent on destroying his reputation and his project 🤦♂️
@shreyan@twtxt.net Hello! 👋 Welcome back! 🤗
@slashdot@feeds.twtxt.net Matt really is a fucking idiot 🤦♂️ Right? 🤔
@slashdot@feeds.twtxt.net Are these guys for realz? 🤔
@slashdot@feeds.twtxt.net And this is why I block all subnets of known “Ai Crawlers” 🤦♂️🤦♂️
@kat@yarn.girlonthemoon.xyz Thinking maybe you’d like to alpha teat EdgeGuard too? 🤔 – My own alternative solution to Clownflare 🤣
@kat@yarn.girlonthemoon.xyz This is so cool!
@slashdot@feeds.twtxt.net Have to agree with the comments on this one 😆 Zuck hasn’t invented shit. Period.
Nooooooooi 😅
@<url>
form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>
.
@bender@twtxt.net Hahahahah 🤣🤣
@bender@twtxt.net That could work aactually…
@kat@yarn.girlonthemoon.xyz pretty much 🤣🤣
@ocdtrekkie@twtxt.net Do you have a copy of his feed in your archive? 🤔🤔
Anyway… Sounds like there is a bug with the version logic. I’ll see if I can fix it.
@kat@yarn.girlonthemoon.xyz Building from source and from the main
branch is totally fine. In fact encouraged. I have a philosophy of main
being stable anyway and making sure backwards compatibility is kept in mind when changing things. i.e: No database migrations to run by hand or what not.
@lyse@lyse.isobeef.org Hmmmm the smell of burning cotton 🤣
@<url>
form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>
.
@lyse@lyse.isobeef.org Hmm you ate right 😆 Also did you volunteer to fix this 🤔🤣
@gallowsgryph@prismdragon.net Sorry to hear that dude 😢 Hope things improve for you! 👌👌
@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 haha 😆
@kat@yarn.girlonthemoon.xyz Haha, that’s why we came up with the name “yarn” and “yarn social”. A yarn is an Australian and Canadian (and a few other places) term that means “to have a friendly conversation”, “to have a chat”. Usually around a campfire 🔥
@kat@yarn.girlonthemoon.xyz The twtxt files for yarnd
are stored under /path/to/data
under the feeds
directory. Oner per user.
@<url>
form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>
.
Was there ever a reason to do that? 🤔
I’m not sure to be honest. I have no idea why you’d ever want to do a “nameless” @-mention@twtxt.net.
As an aside, if we could all agree, I’d personally just say we scrap this whole fragile broken shit and bring out WebMentions and be done with it. And then mentions are always @nick@domain
and looked up, cached and can never be screwed up haha 🤣
@<url>
form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>
.
What’s the motivation for deprecation?
Namely that without the mention having a label (as such) it becomes very hard to render it in any sane/nice way. I think we should just stick to @<label url>
personally. It makes implementations have to worry about far less edge cases.
@lyse@lyse.isobeef.org This could just be a bugger Makefile
or something. I’m not sure what version @kat@yarn.girlonthemoon.xyz built/deployed from? 🤔🤔 – Also I need to release v2.0 soon™
ROFL 🤣
Bahahahah
(You mean like this?)
@doesnm@doesnm.p.psf.lt LOL sorry which client are you using? 🤔 You can of course have a say! There aren’t that many active/used clients at the moment, and I forget which one you’re using 🤣🤣
@<url>
form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>
.
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:
yarnd
@prologic@twtxt.net (me and others)
jenny
@movq@www.uninformativ.de
tt
@lyse@lyse.isobeef.org
Timeline
@darch@neotxt.dk / @eapl.me@eapl.me and others
twtxt-el
? – @andros@twtxt.andros.dev
Full list of supported and widely used clients can be found at https://twtxt.dev/clients.html – which I note a few above are actually missing from this page haha 🤣