No, im just crazy (joke)

@off_grid_living@twtxt.net mind sharing the PDF, to take a look? Some PDF containing text as images, which makes it more difficult to complete the task you want to perform.

[47°09′28″S, 126°43′12″W] Re-taking samples

Gentlemen, I have a pdf file (1.5MB) which I want to be able to block and copy text writing out of it, but it’s locked, preventing this. All I used to do was write it out by hand, or screen shot the text as an image.
Is there any software that opens pdf format for copying and pasting of the text?

@doesnm@doesnm.p.psf.lt am I understanding correctly that you do not have a desktop/laptop computer, but a pocket Android based one?

@doesnm@doesnm.p.psf.lt that was a quick and dirty thing I wanted to try 😄 but of course, you can point it wherever you believe it should.

Lol, good but why why not /data/data/com.termux/files/usr/tmp?

[47°09′47″S, 126°43′15″W] Reading: 0.72 Sv

I believe I’d missed an f:

~/src/jenny $ git diff
diff --git a/jenny b/jenny
index ada8da2..8ae9a06 100755
--- a/jenny
+++ b/jenny
@@ -1194,7 +1194,7 @@ if __name__ == '__main__':
     if args.edit:
	edit_twt_file(app)
     elif args.fetch:
-        with DirectoryLock(f'/tmp/jenny-{getuser()}.run'):
+        with DirectoryLock(expanduser(f'~/tmp/jenny-{getuser()}.run')):
             retrieve_all(app)
     elif args.last_seen:
	 print('Feeds last seen at (times are local time), oldest first:')

@doesnm@doesnm.p.psf.lt I’ve just given it a try on android/termux and got it to work, I can’t promise it won’t break something else (because i definitely don’t know what I’m doing) but here’s what I broke 😅:

~/src/jenny $ git diff
diff --git a/jenny b/jenny
index ada8da2..8ae9a06 100755
--- a/jenny
+++ b/jenny
@@ -1194,7 +1194,7 @@ if __name__ == '__main__':
     if args.edit:
	edit_twt_file(app)
     elif args.fetch:
-        with DirectoryLock(f'/tmp/jenny-{getuser()}.run'):
+        with DirectoryLock(expanduser('~/tmp/jenny-{getuser()}.run')):
             retrieve_all(app)
     elif args.last_seen:
	 print('Feeds last seen at (times are local time), oldest first:')

and of course make sure you mkdir ~/tmp

Rightfully so, @xuu pod has it on cache: https://txt.sour.is/twt/v6eemvq. This pod (twtxt.net), knows nothing about it, so it seems.

I don’t see it on the client (Yarn), but as you can see it is on the raw feed. 🧐

@prologic@twtxt.net I wonder where did this one went to:

2024-09-29T12:08:15Z	 @<lyse https://lyse.isobeef.org/twtxt.txt> love 27! Is that your town as seeing from the mountain, or some other town? From 395 to 40 is quite some picking! I figure that’s the most difficult part, right?

Ah, 16°C… what dreams are made of! 😍

@movq@www.uninformativ.de Hmmm 🤔 Intuitively I say “No they’re not the same”; but let me sleep on it 🙏😴

@bender@twtxt.net Just once I tell ya:

Ah, 16°C… what dreams are made of! 😍

I’d like it to be a nice cool 16°C here 🤣

@lyse@lyse.isobeef.org love 27! Is that your town as seeing from the mountain, or some other town? From 395 to 40 is quite some picking! I figure that’s the most difficult part, right?

Ah, 16°C… what dreams are made of! 😍

Personally I don’t see it as a problem. I didn’t even really see edits as a problem either tbh, but this is just an incremental improvement I think.

It’s no worse than what we have now, it’s better. But yes caveats still apply.

@movq@www.uninformativ.de Yup.

@slashdot@feeds.twtxt.net No 😅

Are AI Coding Assistants Really Saving Developers Time?
Uplevel provides insights from coding and collaboration data, according to a recent report from CIO magazine — and recently they measured “the time to merge code into a repository

@doesnm@doesnm.p.psf.lt I think it’s a good idea to fork twet and continue to improve it. It’s an “okay” Twtxt cli client, but it needs a bit more work 👌

@doesnm@doesnm.p.psf.lt Sorry I meant twet 🤦‍♂️

@lyse@lyse.isobeef.org See @movq@www.uninformativ.de ’s undersanding. Now this had some edge cases that we agreed probably aren’t worth solving for.

@movq@www.uninformativ.de Yes 👍

[47°09′10″S, 126°43′38″W] Transfer aborted

It has twts cache which used if timeline is set to jew. Maybe i.should fork twet to make wishes like newlines (i see two squares), showing conversations, showing twts if not found in cache and parsing medata to configure url, nick and followers (currenly it duplicated in config and twtxt file)

@lyse@lyse.isobeef.org Pretty nice views 👌 I enjoyed reading this. It was though I were there in the morning walking with you guys up to the summit man those mushrooms really are quite some aren’t they? 🙃

@movq@www.uninformativ.de Yes! Basically @david@collantes.us points out that if we mandate that authors should retain the original timestamp in their feed when adjusting content, making fixes, etc, that they retain the original timestamp and leave it unaltered. We already do this anyway, we just need to say so.

Now we have a situation where folks participating in a “conversation” (thread) with appropriate clients can automatically detect edits with almost 100% accuracy by mere fact that the next time they fetch a feed that contains an edit, they now see two versions of the Twt with two different hashes, but identical timestamps.

You can use the fetch time to approximate a “version number” and deal with the display (UX) appropriately.

I can’t believe I didn’t think of this before 🤦‍♂️

There we go!

=> twtxt.dev

🥳

@doesnm@doesnm.p.psf.lt I will have something up soon™ 🤞

@doesnm@doesnm.p.psf.lt twt probably isn’t the best client I’m afraid. It doesn’t really cache twts by their key (hash) to display threads properly. Jenny however does 👌

[47°09′50″S, 126°43′37″W] Bad satellite signal – switching to analog communication

Only with dovecot xD. For mail im use android native mail client and not mutt. And jenny display some errors with found some files and /tmp dir (android dont have /tmp)

twet display twts in raw format with some formatting (sadly no newlines). And for reply messages i just seen (#hash). But which text hidden on hash? currenly im open twtxt.net/twt/hash to see this

Yes, im also do not like Hugo so rewrite theme above to Jekyll (with some changes)

Here’s what I’ve got so far…

@doesnm@doesnm.p.psf.lt Thanks! I’ve almost come up with my own theme already 🤣 I actually don’t really want to use Hugo at all, I find it too complicated. But it is pretty popular so I thought maybe I’d rip-off a nice theme… Hmmm 🧐

Anyway, What I really normally use for a lot of my static sites is zs

https://git.dc09.ru/DarkCat09/dc09-hugo

[47°09′59″S, 126°43′02″W] Non-significative results – sampling finished

I’m looking to develop a static site for twtxt.dev – A domain I own and have wanted to use for developer and specification docs for Twtxt.

Can anyone recommend a few Hugo themes you like?

All of the dev.twtxt.net content would move over as well.

@doesnm@doesnm.p.psf.lt see jenny.

@doesnm@doesnm.p.psf.lt I am not sure I am understanding what you mean. Can you explain?

[47°09′48″S, 126°43′01″W] Taking samples

How to read twts without browser? I dont understand context in reply messages

I shall be there (here?). LOL.

Lol, im just join for several minutes. Wait, Merkle Trees in twtxt?

Cya y’all again next month (2nd Sat in Oct) 🤞

👋 Thanks for joining us on our Sept monthly Yarn.social meetup today y’all 🙇‍♂️ We had @david@collantes.us @sorenpeter@darch.dk @doesnm@doesnm.p.psf.lt @falsifian@www.falsifian.org and @xuu@txt.sour.is 💪 Nice turn out! (not all at once of course, as we normally run this over 4 hours as we span many time zones!)

Things we talked about:

• Decentralised vs. Distributed
  
• Use of SHA256 for Twt Hash(es)
  
• We solved Edits! 🥳
  
• UUID(s) probably won’t work! (susceptible to sppofing)
  
• Helped @sorenpeter@darch.dk write some PHP to process/parse User-Agent and service his feed via a custom PHP script 😅
  
• @falsifian@www.falsifian.org introduced himself 👌
  
• Talked about Merkle Trees 🌳
  

Did I miss anything? 🤔

[47°09′57″S, 126°43′31″W] –white noise–

And here’s a dashy of the no. of notify requests (from WebSub)

yarnd and WebSub

@bender@twtxt.net The display is very very good 😊

Very nice setup, @prologic@twtxt.net! I envy that display! 😍

@aelaraji@aelaraji.com come! @movq@www.uninformativ.de come! @xuu come! @abucci@anthony.buc.ci come!

The lottery is open for everyone, and the pool is small, so chances are you will (might?) be the winner. Come check, and see if you are the winner!

Come join us!

Happening now: https://meet.mills.io/call/Yarn.social

[47°09′14″S, 126°43′29″W] 4181 days without news from Herve

@sorenpeter@darch.dk well edits can be detected with either approach really

Summary of Discussions (as best I can):

• @lyse@lyse.isobeef.org and @sorenpeter@darch.dk express simplicity. Both Lyse and Sorenpeter support location-based addressing.
  
• @falsifian@www.falsifian.org believes we should continue to develop ideas and extensions progressively over time like we’ve always done.
  
• @david@collantes.us @quark@ferengi.one and @bender@twtxt.net would like a better user experience, especially when threads break due to edits, deletions or feed location changes.
  
• @anth@a.9srv.net would like to see utf-8 mandated, and the threading model remain largely the same as it is today, which is primarily based on the convention of a Twt Subject anyway, Twt Hash(es) just make the threading “more precise”. Anth also states that format, client and server specification/recommendations should be kept separate.
  
• @movq@www.uninformativ.de @xuu@txt.sour.is sorry you two haven’t said too much really, so I’m not too sure?
  

Overall, the 22 votes we’ve had on the poll from the community (if you can call it a community?) have clearly shown that:

• We continue to support content-based addressing. (65/35)
  
• We think about formally supporting edits/deletes (60/40)
  
• We do not increase the use of cryptography (thworing things like authenticity and identity out the window) (70/30)
  

And overall the NPS (net promoter score) of “Would I recommend Twtxt to a friend” is a whopping 7/10 (which is crazy! 🤯)

Let’s have our monthly catch up soon™ (1hr) and discuss together. My own take on the direction we should take at this point is as follows:

• We continue to use hashing for the threading model.
  
  • We think about changing this to SHA-256 for simplicity.
    
• We either adopt @anth@a.9srv.net’s UUID approach or @lyse@lyse.isobeef.org Dynamic URL approach.
  
• We continue to incrementally/progressively improve things over time as @falsifian@www.falsifian.org suggested.
  
• We think about mandating utf-8 as @anth@a.9srv.net suggests which makes things so much easier for everyone.
  
• We further discuss the merits/ideas of supporting formal Edit/Delete requests or other ways to better support this in some way.

@lyse@lyse.isobeef.org Got time now before you head off?

Happy Gopher, fridayspace :)

@prologic@twtxt.net YES James, it should be up to the client to deal with changes like edits and deletions. And putting this load on the clients, location-addressing with make this a lot easier since what is says it: Look in this file at this timestamp, did anything change or went missing? (And then threading will not break;)

facilitated a qiudanz technique workshop in a merveilles.town meetup | https://compudanzas.net/qiudanz_devlog.html

facilitated a qiudanz technique workshop in a merveilles.town meetup | gemini://compudanzas.net/qiudanz_devlog.gmi

[47°09′34″S, 126°43′21″W] Reading: 1.75 Sv

@xuu@txt.sour.is Oh geez! Is this anywhere near you?

[47°09′08″S, 126°43′26″W] Dosimeter fixed

People stranded on the roof of a hospital in Tennessee after hurricane Helene

Wild flooding in Ashville, NC due to Hurricane Helene

@falsifian@www.falsifian.org Thank you! 🙏

If we want this though (or some of us do) I will probably have to make the hard decision here to just fork from Twtxt entirely and define a completely new spec. If we care about the UX we need a few properties (some of which we have, some of which we don’t have and some of which are “weak”):

• Authenticity
  
• Integrity
  
• Precision Versioning
  

The last one involves actually supporting the notion of “Edits” and “Deletes” IMO more formally. Without this it would be quite hard to support a strong/good UX. Another way to think about this is “Versioned Twts”.

I think the only legit way of preventing this kind of “spoofing attack” would be:

Digitally Sign Twts: Each Twt could be digitally signed using a private key associated with the UUID. The signature would be calculated over the concatenation of the UUID, timestamp, and content. The public key could be published along with the feed so anyone can verify the authenticity of the Twt by checking the signature. This approach ensures that only the true owner of the UUID (and the corresponding private key) can produce valid hashes.

Which leads us to more Cryptography. Something which y’all voted against.

@bender@twtxt.net This is sadly where you need two things:

• A /twtxt.txt.sig (detached signauture)
  
• Or a way to sign the # uuid = with a key that can be verified.
  

Hmmm and as I write this actually, I think this doesn’t work either, because you can still just copy it regardless. Hmmm @xuu@txt.sour.is help me out here? How do we prevent “spoofing”? 🤔

Diving into mblaze, I think I’ve nearly* reached peek email geek.

Just a bunch of shell commands I can pipe together to search, list, view and reply to email (after syncing it to a local Maildir).

EXAMPLES at https://git.vuxu.org/mblaze/tree/README

So far I’m using most of the tools directly from the command line, but I might take inspiration from https://sr.ht/~rakoo/omail/ to make my workflow a bit more efficient.

*To get any closer, I think I’d have to hand-craft my own SMTP client or something.

That page says “For the best experience your client should also support some of the Twtxt Extensions…” but it is clear you don’t need to. I would like it to stay that way, and publishing a big long spec and calling it “twtxt v2” feels like a departure from that. (I think the content of the document is valuable; I’m just carping about how it’s being presented.)

It’s for this reason I’d like to try changing the Twt Hash extension to use SHA-256 which is a far more common tool available pretty much everywhere. I think the effort involved in “precise threading” (using content addressing) becomes much easier to “author” (note that participating in an existing thread has always been trivial, just copy the Twt Subject in your Twt).

Again, I like this existing simplicity. (I would even argue you don’t need the metadata.)

I argue you do. It’s nice to have a “@nick@domain` a feed author prefers to be called by, rather than you just making shit™ up haha 😝

It’s also quite nice to have a visual representation of the feed too. description can be optional.

Without this, feeds are a bit too “bland” IMO.`

@falsifian@www.falsifian.org Yeah I agree with this actually (introducing too many changes at once is often a bad idead):

but IMO that shouldn’t be done at the same time as introducing new untested ideas

@bender@twtxt.net Bahahahahahahaha 🤣

This is why we need “authenticity” 🤣 Yes if you copied my feed’s UUID, then you’d end up generating identical hashes to me if we posted at identical times with identical timestamps. Not good 😌

Also, was the dot after the timestamp intended?

No, sorry.

@bender@twtxt.net It’s the experience of an ordinary person in a strange place where memories are disappearing with the help of the Memory Police. The setting feels contemporary (to the book’s 1994 publication date) rather than futuristic, except for some unexplained stuff about memories.

@prologic@twtxt.net what if I copy your uuid, and use it on my feed? What happens then? Also, was the dot after the timestamp intended?

@prologic@twtxt.net

See https://dev.twtxt.net

Yes, that is exactly what I meant. I like that collection and “twtxt v2” feels like a departure.

Maybe there’s an advantage to grouping it into one spec, but IMO that shouldn’t be done at the same time as introducing new untested ideas.

See https://yarn.social (especially this section: https://yarn.social/#self-host) – It really doesn’t get much simpler than this 🤣

Again, I like this existing simplicity. (I would even argue you don’t need the metadata.)

That page says “For the best experience your client should also support some of the Twtxt Extensions…” but it is clear you don’t need to. I would like it to stay that way, and publishing a big long spec and calling it “twtxt v2” feels like a departure from that. (I think the content of the document is valuable; I’m just carping about how it’s being presented.)

@falsifian@www.falsifian.org “The Memory Police” sounds like an interesting title. What is it about, if you don’t mind? Even a brief sentence would suffice. Thanks!

For example a v2 spec might just simply mandate the following as a starting point:

cat <<EOF
# nick = $USER
# avatar = https://example.com/$USER.png
# description = Hi 👋 I'm Bob!
# uuid = 7E9BC039-4969-4296-9920-4BACDBA8ED5C

2024-09-28T11:19:25+10:00   Hello World!
EOF > ~/public_html/twtxt.txt

And:

• Serve your file with Content-type: text/plain; charset=utf-8

@falsifian@www.falsifian.org I don’t have a problem with continuing the way we have been for the past ~4 years, little extensions and improvements that we try along the way. That has worked quite well 💪 As a blind person myself, I can totally empathise with reading a full (lots of text) spec. Even if we decide to combine all the ideas into a full fleshed out v2 spec, it might be worthwhile having a cut-down version that is as simple as it can be a no less.

Recent #fiction #scifi #reading:

• The Memory Police by Yōko Ogawa. Lovely writing. Very understated; reminded me of Kazuo Ishiguro. Sort of like Nineteen Eighty-Four but not. (I first heard it recommended in comparison to that work.)

• Subcutanean by Aaron Reed; https://subcutanean.textories.com/ . Every copy of the book is different, which is a cool idea. I read two of them (one from the library, actually not different from the other printed copies, and one personalized e-book). I don’t read much horror so managed to be a little creeped out by it, which was fun.

• The Wind from Nowhere, a 1962 novel by J. G. Ballard. A random pick from the sci-fi section; I think I picked it up because it made me imagine some weird 4-dimensional effect (“from nowhere” meaning not in a normal direction) but actually (spoiler) it was just about a lot of wind for no reason. The book was moderately entertaining but there was nothing special about it.

Currently reading Scale by Greg Egan and Inversion by Aric McBay.

Deprecating non-UTC times seems reasonable to me, though.) Having a big long “twtxt v2” document seems less inviting to people looking for something simple. (@prologic@twtxt.net you mentioned an anonymous comment “you’ve ruined twtxt” and while I don’t completely agree with that commenter’s sentiment, I would feel like twtxt had lost something if it moved away from having a super-simple core

See https://yarn.social (especially this section: https://yarn.social/#self-host) – It really doesn’t get much simpler than this 🤣

@falsifian@www.falsifian.org We’ve been doing this for years:

There are lots of great ideas here! Is there a benefit to putting them all into one document? Seems to me this could more easily be a bunch of separate efforts that can progress at their own pace:

See https://dev.twtxt.net

More thoughts about changes to twtxt (as if we haven’t had enough thoughts):

1. There are lots of great ideas here! Is there a benefit to putting them all into one document? Seems to me this could more easily be a bunch of separate efforts that can progress at their own pace:
   

1a. Better and longer hashes.

1b. New possibly-controversial ideas like edit: and delete: and location-based references as an alternative to hashes.

1c. Best practices, e.g. Content-Type: text/plain; charset=utf-8

1d. Stuff already described at dev.twtxt.net that doesn’t need any changes.

1. We won’t know what will and won’t work until we try them. So I’m inclined to think of this as a bunch of draft ideas. Maybe later when we’ve seen it play out it could make sense to define a group of recommended twtxt extensions and give them a name.

2. Another reason for 1 (above) is: I like the current situation where all you need to get started is these two short and simple documents:
   https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html
   https://twtxt.readthedocs.io/en/latest/user/discoverability.html
   and everything else is an extension for anyone interested. (Deprecating non-UTC times seems reasonable to me, though.) Having a big long “twtxt v2” document seems less inviting to people looking for something simple. (@prologic@twtxt.net you mentioned an anonymous comment “you’ve ruined twtxt” and while I don’t completely agree with that commenter’s sentiment, I would feel like twtxt had lost something if it moved away from having a super-simple core.)

3. All that being said, these are just my opinions, and I’m not doing the work of writing software or drafting proposals. Maybe I will at some point, but until then, if you’re actually implementing things, you’re in charge of what you decide to make, and I’m grateful for the work.

@bender@twtxt.net I’m not following it, but someone on my pod is 🤣 And yes based on statistical evidence, I doubt you’ll see a reply either 🤣

@prologic@twtxt.net it was discovered because aelaraji engaged with it. I don’t think you will see a reply. 😩

@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 🤦‍♂️)