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
@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.
@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
@prologic@twtxt.net I will not be following anyone on those two protocols. Can’t care less.
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%
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.
@bender@twtxt.net To be fair, this has never been a problem for folks that have/use stable Feed URI(s) 🤣
(#bqor23a). Its the same one. My pod doesn't have the Root Twt: https://twtxt.net/twt/bqor23a => 404 Not Found.
Oh, and I think I said this before, but just in case, fuck Gemini. Hell, fuck Gopher too. Bring on telnet, and UCCP. 😈
(#bqor23a). Its the same one. My pod doesn't have the Root Twt: https://twtxt.net/twt/bqor23a => 404 Not Found.
This is confirmed to be the case:
$ for url in gemini://sunshinegardens.org/~xjix/twtxt/tw.txt https://sunshinegardens.org/~xjix/twtxt/tw.txt //sunshinegardens.org/~xjix/twtxt/tw.txt; do yarnc hash -t '2024-09-26T11:09:28-07:00' -u "$url" "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."; done
fk2af7q
7kvnpaq
bqor23a
(#bqor23a). Its the same one. My pod doesn't have the Root Twt: https://twtxt.net/twt/bqor23a => 404 Not Found.
Either way, it is the last time I do something like this. It turns on my fastidiousness, and kind of makes me feel uneasy. Will pause a bit longer from now on.
(#bqor23a). Its the same one. My pod doesn't have the Root Twt: https://twtxt.net/twt/bqor23a => 404 Not Found.
Yup confirmed!
# url = //sunshinegardens.org/~xjix/twtxt/tw.txt
# url = https://sunshinegardens.org/~xjix/twtxt/tw.txt
# url = gemini://sunshinegardens.org/~xjix/twtxt/tw.txt
@cuaxolotl@sunshinegardens.org has changed the url of their feed (yet again) and changed every hash in their feed.
@antonio@twtxt.net is right to call this out. We should drop the reliance on the # url metadata field and in fact we should probably just drop this entirely from the spec and go with # uuid as the basis of a feed’s identity.
Even though this happens very rarely (feeds moving to new locations) it more frequently happens with folks that try to serve their feed from Gopher, HTTP and Gemini.
(#bqor23a). Its the same one. My pod doesn't have the Root Twt: https://twtxt.net/twt/bqor23a => 404 Not Found.
@bender@twtxt.net Hmm I think I know why…
2024-09-27T01:28:53+00:00 (#bqor23a) @<cuaxolotl https://sunshinegardens.org/~xj9/twtxt/tw.txt> Wait, what!? We're dropping Gemini support!?
From @aelaraji@aelaraji.com’s feed. I think @cuaxolotl@sunshinegardens.org doesn’t do threading properly, I’ve run into this once before. I’m not sure what client they use? 🤔
(#bqor23a). Its the same one. My pod doesn't have the Root Twt: https://twtxt.net/twt/bqor23a => 404 Not Found.
@prologic@twtxt.net yes, it has gotten kind of messy. Someone deleted/edited. That’s the only explanation.
(#bqor23a). Its the same one. My pod doesn't have the Root Twt: https://twtxt.net/twt/bqor23a => 404 Not Found.
Search engine doesn’t know about it either: https://search.twtxt.net/twt/bqor23a
@bender@twtxt.net Re that broken thread (#bqor23a). Its the same one. My pod doesn’t have the Root Twt: https://twtxt.net/twt/bqor23a => 404 Not Found.
How in the hell did you even reply to this in the first place?
@prologic@twtxt.net and this one? It’s madness!
@prologic@twtxt.net what was this in reply to? 🤭
Hmmm https://twtxt.net/twt/bqor23a => 404 Not Found 🤣
@bender@twtxt.net What was this in reply to? 🤔
@aelaraji@aelaraji.com Probably not.
@cuaxolotl@sunshinegardens.org Context?
(#bqor23a) @aelaraji@aelaraji.com
@cuaxolotl@sunshinegardens.org We probably won’t in fairness. i only called it out because discovery is made much harder with Gopher and Gemini. Caching is also impossible too.
@cuaxolotl@sunshinegardens.org We probably won’t in fairness. I only called it out because discovery is made much harder with Gopher and Gemini. Caching is also impossible too.
Last chance to have your say before tomorrow’s meetup:
@aelaraji@aelaraji.com it is not.
@cuaxolotl@sunshinegardens.org Wait, what!? We’re dropping Gemini support!?
@aelaraji@aelaraji.com ooooh! It’s that kind mission! /me stands, salutes, turns around, and exits the room. LOL.
FIN?
@aelaraji@aelaraji.com why, having a party with lots of libations? LOL.
@aelaraji@aelaraji.com not missing it at all!
as a matter of fact! don’t mind anything I do/say for the next 72 hours xD
Don’t mind this twt!
What does this image means?
That board is really… something (really can’t explain it with words). Also found interesting that’s a board for a single five-stars user, “Admin”. 😳
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.
@mckinley@twtxt.net dogecoin or nothing. Dogecoin is life! 😅
-P is a life saver when running rsync over spotty connections. In my very illiterate opinion, it should always be a default.
@mckinley@twtxt.net I could have sworn that it resumed even a partial file the other week. But maybe that was because the first attempt used scp when the connection broke. And then rsync detected that only the last part of that file was incomplete and transferred the missing bits. So, lucky by accident. In any case, I will always include -P from now on. :-)
Ah, I see! Thanks, @bender@twtxt.net.
@david@collantes.us Sounds lovely. :-)
We had rain all day long and my mate and I still went for a walk with our umbrellas. It was a bit wet. But now I can send my drying rack over the tub on its maiden voyage. Should have built a second rod for more capacity.
-P is a life saver when running rsync over spotty connections. In my very illiterate opinion, it should always be a default.
@lyse@lyse.isobeef.org If rsync is interrupted, it doesn’t delete any files that were transferred completely so it will “resume” from that last complete transfer. However, it does delete any partially transferred file. --partial keeps that partial file around on the destination machine so it can continue right where it left off.
rsync(1) but, whenever I Tab for completion and get this:
I usually end up using -rtz because I’m usually not 100% sure all the permissions and ownership information are right and I hate littering directories with inconsistent permissions. For a big transfer, I’ll start with -rtvz --stats --dry-run and make sure it’s only transferring the files it should, then I’ll do -rtz --stats --info=progress2 --no-i-r to get one progress bar to watch for the whole transfer.
@slashdot@feeds.twtxt.net This is exciting news! Two of the most important privacy tools joining forces. Now, if we could get a Monero wallet included in Tails alongside Electrum, we’d really have something. :)
Tor Project Merges With Tails
The Tor Project: Today the Tor Project, a global non-profit developing tools for online privacy and anonymity, and Tails, a portable operating system that uses Tor to protect users from digital surveillance, have joined forces and merged operations. Incorporating Tails into the Tor Project’s structure allows for easier collaboration, better sustainability, reduced overhead, and expanded training and outreach program … ⌘ Read more
@prologic@twtxt.net that “little database that could” is simply amazing, isn’t it? I run Conduwuit (nevermind, this one is RocksDB), and GoToSocial using it as a backend, no issues. And, of course, sqlite is the database of choice for a lot of things under iOS.