@doesnm@doesnm.p.psf.lt The useragent tool now natively supports the Caddy (JSON) logfile format. 🥳

@prologic@twtxt.net Done. Also, I went ahead and made two changes: changed hexadecimal to base64 for hashes (wasn’t sure if anyone objected), and changed “MUST follow the chain” to “SHOULD follow the chain.

This is a 1-way feed by the looks 🤣 Maybe someone can figure out how to reach out to this person and see if they’re aware and interested in something a bit more “social” (albeit slow) 🤣

@falsifian@www.falsifian.org Sorry I didn’t make that super clear 🤦‍♂️ Be happy to see you there and some new folks 🙇‍♂️

🥳 NEW FEED: @3r1c@3r1c.net

@prologic@twtxt.net Thanks for pointing out it lasts four hours. That’s a big window! I wonder when most people will be on. I might aim for halfway through unless I hear otherwise. (12:00Z is a bit early for me.)

This Facebook/Meta story on storing passwords in plain text it just wow 😮 – Like how da fuq does a company, or anyone for that matter in the business of software / technology even do this?! Like at least base64 encode the fuckers right?! (oh wait 🤦‍♂️)

@xuu@txt.sour.is If you have time, could you help me pinpoint this bug? 🐛

@lyse@lyse.isobeef.org It’s from 12pm to 4pm UTC so if you can make it at all, that’d be great 👍

@xuu@txt.sour.is Do you think we should just detect edits at the client-level then? 🤔

Probably the best idea I’ve heard/seen si far is @anth@a.9srv.net’s idea of a feed having a uuid # uuid = (if present) otherwise just falling back to the URL you fetched it from and dropping the idea of a feed # url = entirely.

@lyse@lyse.isobeef.org Yup you’re right, it’s s terrible idea 💡

Well the poll clearly shows:

• ~65/35 in favor of Content Addressing
  
• ~60/40 in favor of supporting Edit/Delete
  
• ~70/30 against more cryptograph
  

And an NPS score of 7/10 🤣

O #fridayreads desta semana é o “Privacidade 404” do @psenough@psenough !

Image

@bender@twtxt.net Zero technical issues 🤣 I never claims otherwise 😅

Definitely NOT editing that Oupsie… + It looks all the same in terminal, so I can live with it.🤣

Happy Friday, gopherspace!

On my blog: Toots 🦣 from 09/23 to 09/27 https://john.colagioia.net/blog/2024/09/27/week.html #linkdump #socialmedia #quotes #week

On my blog: Toots 🦣 from 09/23 to 09/27 #linkdump #socialmedia #quotes #week

On my blog: Toots 🦣 from 09/23 to 09/27 https://john.colagioia.net/blog/2024/09/27/week.html #linkdump #socialmedia #quotes #week

@bender@twtxt.net So…

(#sbmynna) @xuu@txt.sour.is wrote:

”@bender I am also in camp no edit signals. deletes only breaks the head of a thread. all the replies are unaffected.”

I figure I could also answer every single twtxt like this, so that if the original gets edited, or deleted, at least I don’t sound foolish without knowing exactly what I replied to. 🤭

It Sounds like a good idea! should that be limited to just direct replays or can it be extended to replays to other replays, that way and With just the right amount of chain-replays, we’ll be RRrrrrrevolutionizing the way people Mailing Lists like, in no time! xD

P.S: Just a reminder! I’ve already told you not to mind my twts for the next couple of hours, right!

@bender@twtxt.net HAHA I’ve just bookmarked that Repo to go through it tomorrow 👌

@bender@twtxt.net I am also in camp no edit signals. deletes only breaks the head of a thread. all the replies are unaffected.

See!? Even Meta/Facebook uses plain text, not just Twtxt! 🤣

Meta fined $102 million for storing passwords in plain text

@3r1c@3r1c.net Woa! I love this blog’s format! _ it’s just perfect for reading from terminal…

https://renecoignard.com/

@lyse@lyse.isobeef.org that sounds truly idyllic! 🤭

@lyse@lyse.isobeef.org HAHA Nice one!

@bender@twtxt.net Well Matt should definitely get better Lawyers/PR people who could slap em’ on the wrest and tell “NO!” before he does something childish and effs things up. As for WPE, I believe a billion dollar company should be able to afford investing in their own infrastructure, hosting their resources, deploying their own CDNs and what not instead of leaching on Wordpress (’s infrastructure) for free (as in free coffee) + The Stripe thing they did is so disgusting given the circumstances, I don’t even want to talk about it.

Things could/should’ve been handled better, now it’s just another sh…rimp show.

@stigatle@yarn.stigatle.no You too buddy, have a good one!

@prologic@twtxt.net here… Get the same impression about the dude as everyone else and then (get the other side of the story, although it is a mess)[https://invidious.privacyredirect.com/watch?v=Gd8h_6vYPJ8] … Theeeeen, don’t give an Eff’ about any of it. 🤣

@david@collantes.us and WPE are saints, right? 🤣

Finally weekend. Time to relax a bit. And today I finally have some time for my computer in my free time. Wish you all a great weekend! Take care of your self and those around you :)

@bender@twtxt.net yeah, that’s what I said, and linked. Want more?

@bender@twtxt.net Yes but you’ve got me curious now 😅

Okay, co-founder of Wordpress and CEO of Automation.

What has the poor guy done? 🤣

@david@collantes.us Who’s Matt Mullenweg? 🤔

Matt Mullenweg is an asshole. That’s all; that’s the message.

“First world” countries problem number x:

More than 3,600 chemicals approved for food contact in packaging, kitchenware or food processing equipment have been found in humans, new peer-reviewed research has found, highlighting a little-regulated exposure risk to toxic substances.

Like really tbh, it’s just a matter of abstracting out the “fetching” part of your client. There are zero issues with fetching Gopher/Gemini hosted feeds. They just lack any mechanisms for Discovery and Caching.

@doesnm@doesnm.p.psf.lt Still haven’t received it. Did you send to james at mills dot io? 🤔

@movq@www.uninformativ.de I don’t think I intend to either tbh for yarnd. If there was any poorly worded “things”, it was just merely pointing out lacking capabilities for caching and discovery.

@doesnm@doesnm.p.psf.lt nah man! you’re not tricking me into answering that one 🤣🤣🤣

huh? im send. currently send twice

@bender@twtxt.net Oh so what you’re saying is “we” (royal we) ruined Twtxt 🤣

@doesnm@doesnm.p.psf.lt Are you sure? Not seen the mail yet…

@aelaraji@aelaraji.com LOL 😂 Here’s one for you:

You can take IRC out of my cold 🥶 dead 😵 hands 🙌

Lol, Discord is centralized. Did you mean Salty.IM? (want groups)

Done!

“Fu*** IRC maaan, all the cool kids are on Discord! IRC sucks”

LOL, Now substitute IRC and Discord with Gopher/Gemini and Web.
I hope you get the joke 😅

Anyway I’ve setup an alias now 🤣

@doesnm@doesnm.p.psf.lt Ooops you might want to re-send that to james instead 🤣

@aelaraji@aelaraji.com It sadly does not it seems. 🤣 Seems like the search engine has come across mentions of your feed via its other two protocols 🤣

$ inspect-db yarns.db | jq -r '.Value.URL' | grep 'aelaraji.com'
https://aelaraji.com/test_feed.txt
https://aelaraji.com/twtxt.txt

i’m sent to prologic@mills.io

@prologic@twtxt.net does that include mine? otherwise it would make them 8 and 5, maybe even throw off your maths by 0.00001% 😆 … and, come on! 1.04% seems like a good ratio considering how many gopher holes and gem capsules compared to how many Web servers out there in the world 😂

The damn wind is ignoring my complaint?

@doesnm@doesnm.p.psf.lt My Salty public key is:

kex1fhxntuc0av7q48hlfj970ve297dzzghn82wp5cahr9r92y8rlrqqtwp983

this log can contain ips so im place it in secret path and send link via salty

@xuu@txt.sour.is they can take 2% of your disk space/bandwidth and rent it to the highest bidder 🤥

awesome that this exists

@doesnm@doesnm.p.psf.lt Do you have a sample Caddy log file you can supply? I’ll see if we can improve the tool 👌

Official yarn.social tool: git.mills.io/yarnsocial/useragent

@doesnm@doesnm.p.psf.lt Fot a sample access log? Which tool are you using?

how to parse caddy access log with useragent tool? seems it dont detect anything in json

@doesnm@doesnm.p.psf.lt I don’t think it does. I think it’s completely different to what you’re thinking.

@doesnm@doesnm.p.psf.lt Yeah just move your feet. It’s totally fine. Don’t worry about it.

Found this: https://notabug.org/tinyrabbit/gemini-antenna. Maybe it have some user-agent alternative?

Yes. I have only twtxt and scp hook in twet and it enough

@doesnm@doesnm.p.psf.lt I couldn’t find any references to this anywhere either.

@doesnm@doesnm.p.psf.lt Like now?

Wait, webfinger? Mandate this ruin philosophy “twtxt is just text file”

Can i change identify without ruining federation? it is important because i can change server and want migrate all my data

@doesnm@doesnm.p.psf.lt I have no idea to be honest 🤣 I’m actually not really sure how you can ruin something be improving it 🤦‍♂️

I dont think that is ruined twtxt. Twtxt v2 is just standartize twtxt and yarn extensions. What is bad?

We:

• Drop # url= from the spec.
  
• We don’t adopt # uuid = – Something @anth@a.9srv.net also mentioned (see below)
  

We instead use the @nick@domain to identify your feed in the first place and use that as the identify when calculating Twt hashes <id> + <timestamp> + <content>. Now in an ideal world I also agree, use WebFinger for this and expect that for the most part you’ll be doing a WebFinger lookup of @user@domain to fetch someone’s feed in the first place.

The only problem with WebFinger is should this be mandated or a recommendation?

Something @anth@a.9srv.net said on ITC

17:42 I should also note in there that it doesn’t address the two things i really want it to: mandate utf-8 (which should be easy to fit in) and something for better @ mentions.

I actually agree with in both counts and it got me thinking…

I hear about Gemini Antenna as User Agent alternative but cant find any information

you’ve ruined twtxt

Not sure what to say here. 🤔

Thank you for all the hard work put into the project.

Thank you to whomever said this! 🙇‍♂️

Many of the faces go hand in hand or depend on the selected protocol a feed is published with or client features. I’m pretty sure people interpret different things into these terms.

See previous. Sorry 😞

Not sure what to think about the stack ranking question. I care that it’s a simple text file i can just stick on my server. Security, identity, &c come out of how I manage the server.

See previous.

I don’t know what all the facets mean. E.g. what’s the difference between “Integrity” and “Authenticity”?

Yes, I totally get where you’re coming from. However after ~22 results, I think y’all have figured out how to rank them appropriately anyway 🤣

Sharing the comments of the poll (anonymous so I have no idea whom the comments are from):

your poll should include questions about markdown. personally i think inline bits like style, links, images are yes. block quotes, code blocks, bullet lists are mid. but tables and footnotes are no.

Yes sorry about this, I wasn’t able to change much after publishing the poll 😅

@slashdot@feeds.twtxt.net GTFO 🤣

HP Is Adding AI To Its Printers
An anonymous reader quotes a report from PCWorld, written by Michael Crider: The latest perpetrator of questionable AI branding? HP. The company is introducing “Print AI,” what it calls the “industry’s first intelligent print experience for home, office, and large format printing.” What does that mean? It’s essentially a new beta software driver package for some HP printers. According to the press release, … ⌘ Read more

cc @xuu@txt.sour.is

@bender@twtxt.net I believe it is Unix-Unix Copy Protocol. Not Unix Copy-Copy Protocol.

83(4) GDPR sets forth fines of up to 10 million euros, or, in the case of an undertaking, up to 2% of its entire global turnover of the preceding fiscal year, whichever is higher.

Though I suppose it has to be the greater of the two. But I don’t even have one euro to start with.

Wind’s picking up. The guys are busy; you’re in charge. Ya know what? You’re a goddamn swordboat captain! Is there anything better in the world?

@bender@twtxt.net Well as you’ve pointed out in the past, both protocol suffer from Discovery (as I’ve stated as well) and more often than not, users that publish Twtxt feeds over these protocols tend to just “point into the void” and it’s next to impossible to have any kind of “social interaction” (ignoring personal choices of course, if one’s feed is intended for 1-way …)

I think there’s a bug in yarnd hwoever:

$ yarnc debug https://sunshinegardens.org/~xjix/twtxt/tw.txt
...
bqor23a 2024-09-26T11:09:28-07:00	if twtxt 2 is dropping gemini support, i will probably move on and spend more time on my gemini social zine protocol instead. i think the direction of the protocol is probably fine, but for me web is a tier 2 publishing channel. if the choice is between gemini and http i'm always going to pick gemini. its been a fun ride, but i guess this is where i get off.

The yarnc CLI tool and the lextwt parser we use in yarnd correctly parses the feed and sets the Twter.HashingURI to the latest # url = found in the feed. However my pod hasn’t picked this up 😢 I follow @cuaxolotl@sunshinegardens.org as https://sunshinegardens.org/~xjix/twtxt/tw.txt

Gemini/Gopher Twtxt feeds account for less than 1% in existence:

$ total=$(inspect-db yarns.db | jq -r '.Value.URL' | awk -F'//' '{if ($1 ~ /^https?/) print "http/https:"; else print $1}' | sort | uniq -c | awk '{sum+=$1} END {print sum}'); inspect-db yarns.db | jq -r '.Value.URL' | awk -F'//' '{if ($1 ~ /^https?/) print "http/https:"; else print $1}' | sort | uniq -c | awk -v total="$total" '{printf "%d %s %.2f%%\n", $1, $2, ($1/total)*100}' | sort -r
7 gemini: 0.66%
4 gopher: 0.38%
1046 http/https: 98.96%

LILYGO T-Embed CC1101: Enabling Sub-GHz and NFC/RFID Communication
LILYGO launched the T-Embed CC1101, built around the ESP32-S3 Dual-core LX7. It supports Wi-Fi, BLE 5, and Sub-GHz wireless communication, targeting remote and low-power IoT projects. The ESP32-S3 microcontroller is paired with 16MB of Flash memory and 8MB of PSRAM. The CC1101 chip operates across frequency bands of 300-348 MHz, 387-464 MHz, and 779-928 MHz,

Note however this doesn’t solve the problem of Caching at all. It just works around it and with enough clients fetching a Gopher/Gemini feed, this # refresh becomes useless anyway at a certain point of scale.

@bender@twtxt.net Well this is the thing really. Gopher and Gemini are very broken ways to distributed content. Broken in the sense that for Twtxt either support a) caching in any way shape or form b) discovery in any way shape or form.

This is a bit of a problem because if a Feed author complains (nad they have in the past) that their Gopher/Gemini feeds are being hit “too hard”, well that’s really kind of on them for choosing to host their feed on an ill advised protocol thatc cannot possibly support Caching at all.

This is primarily one of the reasons we introduced the idea of a “feed advised refresh interval” that clients SHOULD respect.

See: https://dev.twtxt.net/doc/metadataextension.html#refresh

refresh
This optional field is used by feed authors as a hint to clients to control how often they should fetch or update this feed.

The value of this field is seconds represented by an integer.

NOTE: An empty, bad, or unparsable value is ignored.