[47°09′16″S, 126°43′59″W] Reading: 0.70 Sv

@prologic@twtxt.net currently? it wouldnt :D.

we would need to come up with a way of registering with multiple brokers that can i guess forward to a reader broker. something that will retry if needed. need to read into how simplex handles multi brokers

[47°09′29″S, 126°43′58″W] Reading: 0.76000 PPM

Insecure Robot Vacuums From Chinese Company Deebot Collect Photos and Audio to Train Their AI
Long-time Slashdot reader schwit1 shared this report from Australia’s public broadcaster ABC:

Ecovacs robot vacuums, which have been found to suffer from critical cybersecurity flaws, are collecting photos, videos and voice recordings — taken inside customers’ houses — to train the company’ … ⌘ Read more

[47°09′35″S, 126°43′41″W] Reading: 0.91000 PPM

Reading about browser security measures and getting sad we don’t live in a world where cross-site scripting is a feature instead of a bug.

[47°09′51″S, 126°43′01″W] Raw reading: 0x66FE7932, offset +/-1

Did Apple Just Kill Social Apps?
Apple’s iOS 18 update has introduced changes to contact sharing that could significantly impact social app developers. The new feature allows users to selectively share contacts with apps, rather than granting access to their entire address book. While Apple touts this as a privacy enhancement, developers warn it may hinder the growth of new social platforms. Nikita Bier, a start-up founder, called it “the en … ⌘ Read more

[47°09′51″S, 126°43′20″W] Reading: 0.23000 PPM

[47°09′22″S, 126°43′38″W] Reading: 0.29000 PPM

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

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

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

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.

[47°09′36″S, 126°43′42″W] Reading: 0.10 Sv

[47°09′18″S, 126°43′07″W] Reading: 1.32000 PPM

[47°09′32″S, 126°43′12″W] Reading: 0.44000 PPM

(#2024-09-24T12:53:35Z) What does this screenshot show? The resolution it too low for reading the text…

What does this screenshot show? The resolution it too low for reading the text…

(#2024-09-24T12:45:54Z) @prologic@twtxt.net I’m not really buying this one about readability. It’s easy to recognize that this is a URL and a date, so you skim over it like you would we mentions and markdown links and images. If you are not suppose to read the raw file, then we might a well jam everything into JSON like mastodon

Aggred. But reading twtxt in raw form sounds… I can’t do this

Finally pubnix is alive! That’s im missing? Im only reading twtxt.net timeline because twtxt-v2.sh works slowly for displaying timeline…

@prologic@twtxt.net Thanks for writing that up!

I hope it can remain a living document (or sequence of draft revisions) for a good long time while we figure out how this stuff works in practice.

I am not sure how I feel about all this being done at once, vs. letting conventions arise.

For example, even today I could reply to twt abc1234 with “(#abc1234) Edit: …” and I think all you humans would understand it as an edit to (#abc1234). Maybe eventually it would become a common enough convention that clients would start to support it explicitly.

Similarly we could just start using 11-digit hashes. We should iron out whether it’s sha256 or whatever but there’s no need get all the other stuff right at the same time.

I have similar thoughts about how some users could try out location-based replies in a backward-compatible way (append the replyto: stuff after the legacy (#hash) style).

However I recognize that I’m not the one implementing this stuff, and it’s less work to just have everything determined up front.

Misc comments (I haven’t read the whole thing):

• Did you mean to make hashes hexadecimal? You lose 11 bits that way compared to base32. I’d suggest gaining 11 bits with base64 instead.

• “Clients MUST preserve the original hash” — do you mean they MUST preserve the original twt?

• Thanks for phrasing the bit about deletions so neutrally.

• I don’t like the MUST in “Clients MUST follow the chain of reply-to references…”. If someone writes a client as a 40-line shell script that requires the user to piece together the threading themselves, IMO we shouldn’t declare the client non-conforming just because they didn’t get to all the bells and whistles.

• Similarly I don’t like the MUST for user agents. For one thing, you might want to fetch a feed without revealing your identty. Also, it raises the bar for a minimal implementation (I’m again thinking again of the 40-line shell script).

• For “who follows” lists: why must the long, random tokens be only valid for a limited time? Do you have a scenario in mind where they could leak?

• Why can’t feeds be served over HTTP/1.0? Again, thinking about simple software. I recently tried implementing HTTP/1.1 and it wasn’t too bad, but 1.0 would have been slightly simpler.

• Why get into the nitty-gritty about caching headers? This seems like generic advice for HTTP servers and clients.

• I’m a little sad about other protocols being not recommended.

• I don’t know how I feel about including markdown. I don’t mind too much that yarn users emit twts full of markdown, but I’m more of a plain text kind of person. Also it adds to the length. I wonder if putting a separate document would make more sense; that would also help with the length.

[47°09′40″S, 126°43′18″W] Raw reading: 0x66F06931, offset +/-2

[47°09′39″S, 126°43′44″W] Raw reading: 0x66EF17B1, offset +/-5

@movq@www.uninformativ.de @falsifian@www.falsifian.org @prologic@twtxt.net Maybe I don’t know what I’m talking about and You’ve probably already read this: Everything you need to know about the “Right to be forgotten” coming straight out of the EU’s GDPR Website itself. It outlines the specific circumstances under which the right to be forgotten applies as well as reasons that trump the one’s right to erasure …etc.

I’m no lawyer, but my uneducated guess would be that:

A) twts are already publicly available/public knowledge and such… just don’t process children’s personal data and MAYBE you’re good? Since there’s this:

… an organization’s right to process someone’s data might override their right to be forgotten. Here are the reasons cited in the GDPR that trump the right to erasure:

• The data is being used to exercise the right of freedom of expression and information.
  
• The data is being used to perform a task that is being carried out in the public interest or when exercising an organization’s official authority.
  
• The data represents important information that serves the public interest, scientific research, historical research, or statistical purposes and where erasure of the data would likely to impair or halt progress towards the achievement that was the goal of the processing.
  

B) What I love about the TWTXT sphere is it’s Human/Humane element! No deceptive algorithms, no Corpo B.S …etc. Just Humans. So maybe … If we thought about it in this way, it wouldn’t heart to be even nicer to others/offering strangers an even safer space.
I could already imagine a couple of extreme cases where, somewhere, in this peaceful world one’s exercise of freedom of speech could get them in Real trouble (if not danger) if found out, it wouldn’t necessarily have to involve something to do with Law or legal authorities. So, If someone asks, and maybe fearing fearing for… let’s just say ‘Their well being’, would it heart if a pod just purged their content if it’s serving it publicly (maybe relay the info to other pods) and call it a day? It doesn’t have to be about some law/convention somewhere … 🤷 I know! Too extreme, but I’ve seen news of people who’d gone to jail or got their lives ruined for as little as a silly joke. And it doesn’t even have to be about any of this.

P.S: Maybe make X tool check out robots.txt? Or maybe make long-term archives Opt-in? Opt-out?
P.P.S: Already Way too many MAYBE’s in a single twt! So I’ll just shut up. 😅

[47°09′46″S, 126°43′19″W] Raw reading: 0x66ED55B1, offset +/-5

[47°09′20″S, 126°43′29″W] Reading: 1.71000 PPM

[47°09′21″S, 126°43′56″W] Raw reading: 0x66EC4A81, offset +/-5

@prologic@twtxt.net I read it. I understand it. Hopefully a solution can be agreed upon that solves the editing issue, whilst maintaining the cryptographic hash.

Apple A16 SoC Now Manufactured In Arizona
“Apple has begun manufacturing its A16 SoC at the newly-opened TSCM Fab 21 in Arizona,” writes Slashdot reader NoMoreACs. AppleInsider reports: According to sources of Tim Culpan, Phase 1 of TSMC’s Fab 21 in Arizona is making the A16 SoC of the iPhone 14 Pro in “small, but significant, numbers. The production is largely a test for the facility at this stage, but more production is expected … ⌘ Read more

Could someone knowledgable reply with the steps a grandpa will take to calculate the hash of a twtxt from the CLI, using out-of-the-box tools? I swear I read about it somewhere, but can’t find it.

[47°09′10″S, 126°43′41″W] Reading: 1.51 Sv

[47°09′25″S, 126°43′13″W] Raw reading: 0x66E928F1, offset +/-5

[47°09′11″S, 126°43′57″W] Reading: 0.63000 PPM

@sorenpeter@darch.dk

1. (replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)
   

I think I like this a lot. 🤔

The problem with using hashes always was that they’re “one-directional”: You can construct a hash from URL + timestamp + twt, but you cannot do the inverse. When I see “, I have no idea what that could possibly refer to.

But of course something like (replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z) has all the information you need. This could simplify twt/feed discovery quite a bit, couldn’t it? 🤔 That thing that I just implemented – jenny asking some Yarn pod for some twt hash – would not be necessary anymore. Clients could easily and automatically fetch complete threads instead of requiring the user to follow all relevant feeds.

Only using the timestamp to identify a twt also solves the edit problem.

It even is better for non-Yarn clients, because you now don’t have to read, understand, and implement a “twt hash specification” before you can reply to someone.

The only problem, really, is that (replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z) is so long. Clients would have to try harder to hide this. 😅

More:

Subject: The [tag URI scheme](https://en.wikipedia.org/wiki/Tag_URI_scheme) looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be
        somewhat trivial to parse. But there are still the issue with what the name/id should be... Maybe it doesn't have to bee that stick? Instead of using `tag:` as the prefix/protocol, it would more it clear
        what we are talking about by using `in-reply-to:` (https://indieweb.org/in-reply-to) or `replyto:` similar to `mailto:` 1. `(reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)' 2.
        `(in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)' 2. `(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)' I know it's longer that 7-11 characters, but it's self-explaining when looking at the
        twtxt.txt in the raw, and the cases above can all be caught with this regex: `\([\w-]*reply[\w-]*\:` Is this something that would work?

Subject: The [tag URI scheme](https://en.wikipedia.org/wiki/Tag_URI_scheme) looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be
        somewhat trivial to parse. But there are still the issue with what the name/id should be... Maybe it doesn't have to bee that stick? Instead of using `tag:` as the prefix/protocol, it would more it clear
        what we are talking about by using `in-reply-to:` (https://indieweb.org/in-reply-to) or `replyto:` similar to `mailto:` 1. `(reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)` 2.
        `(in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)` 3. `(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)` I know it's longer that 7-11 characters, but it's self-explaining when looking at the
        twtxt.txt in the raw, and the cases above can all be caught with this regex: `\([\w-]*reply[\w-]*\:` Is this something that would work?

Notice the difference? Soren edited, and broke everything.

@mckinley@twtxt.net Thanks for the feedback.

1. Yeah I agrees that nick sound not be part of syntax. Any valid URL to a twtxt.txt-file should be enough and is more clear, so it is not confused with a email (one of the the issues with webfinger and fedivese handles)
   
2. I think any valid URL would work, since we are not bound to look for exact matches. Accepting both http and https as well as a gemni and gophe could all work as long as the path to the twtxt.txt is the same.
   
3. My idea is that you quote the timestamp as it is in the original twtxt.txt that you are referring to, so you can do it by simply copy/pasting. Also what are the change that the same human will make two different posts within the same second?!
   

Regarding the whole cryptographic keys for identity, to me it seems like an unnecessary layer of complexity. If you move to a new house or city you tell people that you moved - you can do the same in a twtxt.txt. Just post something like “I move to this new URL, please follow me there!” I did that with my feeds at least twice, and you guys still seem to read my posts:)

The tag URI scheme looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be somewhat trivial to parse. But there are still the issue with what the name/id should be… Maybe it doesn’t have to bee that stick?

Instead of using tag: as the prefix/protocol, it would more it clear what we are talking about by using in-reply-to: (https://indieweb.org/in-reply-to) or replyto: similar to mailto:

1. (reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)
   
2. (in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)
   
3. (replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)
   

I know it’s longer that 7-11 characters, but it’s self-explaining when looking at the twtxt.txt in the raw, and the cases above can all be caught with this regex: \([\w-]*reply[\w-]*\:

Is this something that would work?

@prologic@twtxt.net Brute force. I just hashed a bunch of versions of both tweets until I found a collision.

I mostly just wanted an excuse to write the program. I don’t know how I feel about actually using super-long hashes; could make the twts annoying to read if you prefer to view them untransformed.

@prologic@twtxt.net

They’re in Section 6:

• Receiver should adopt UDP GRO. (Something about saving CPU processing UDP packets; I’m a but fuzzy about it.) And they have suggestions for making GRO more useful for QUIC.

• Some other receiver-side suggestions: “sending delayed QUICK ACKs”; “using recvmsg to read multiple UDF packets in a single system call”.

• Use multiple threads when receiving large files.

[47°09′20″S, 126°43′53″W] Reading: 0.55 Sv

[47°09′34″S, 126°43′34″W] Reading: 1.06000 PPM

@sorenpeter@darch.dk !! I freaking love your Timeline … I kind of have an justified PHP phobia 😅 but, I’m definitely thinking about giving it a try!

/ME wondering if it’s possible to use it locally just to read and manage my feed at first and then maybe make it publicly accessible later.

[47°09′43″S, 126°43′59″W] Raw reading: 0x66E17831, offset +/-5

[47°09′21″S, 126°43′09″W] Reading: 1.65000 PPM

[47°09′58″S, 126°43′15″W] Reading: 0.66000 PPM

[47°09′27″S, 126°43′47″W] Reading: 0.31000 PPM

[47°09′31″S, 126°43′39″W] Reading: 0.31 Sv

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

[47°09′30″S, 126°43′00″W] Reading: 1.62000 PPM

@prologic@twtxt.net I believe you when you say registries as designed today do not crawl. But when I first read the spec, it conjured in my mind a search engine. Now I don’t know how things work out in practice, but just based on reading, I don’t see why it can’t be an API for a crawling search engine. (In fact I don’t see anything in the spec indicating registry servers shouldn’t crawl.)

(I also noticed that https://twtxt.readthedocs.io/en/latest/user/registry.html recommends “The registries should sync each others user list by using the users endpoint”. If I understood that right, registering with one should be enough to appear on others, even if they don’t crawl.)

Does yarnd provide an API for finding twts? Is it similar?

[47°09′58″S, 126°43′39″W] Raw reading: 0x66D75CB2, offset +/-3

[47°09′54″S, 126°43′44″W] Reading: 0.40 Sv

Google’s James Manyika: ‘The Productivity Gains From AI Are Not Guaranteed’
Google executive James Manyika has warned that AI’s impact on productivity is not guaranteed [Editor’s note: the link may be paywalled], despite predictions of trillion-dollar economic potential. From the report: “Right now, everyone from my old colleagues at McKinsey Global Institute to Goldman Sachs are putting out these extra … ⌘ Read more

[47°09′27″S, 126°43′24″W] Reading: 0.87 Sv

[47°09′26″S, 126°43′24″W] Raw reading: 0x66D59AB1, offset +/-2

[47°09′12″S, 126°43′25″W] Raw reading: 0x66D56271, offset +/-2

[47°09′24″S, 126°43′03″W] Reading: 1.43 Sv

[47°09′27″S, 126°43′12″W] Reading: 0.80000 PPM

Falling satellite will give clues to how objects burn up on re-entry
A chance to observe the high-speed re-entry of a falling satellite will give researchers important insights on how debris burns up in our atmosphere ⌘ Read more

[47°09′03″S, 126°43′56″W] Reading: 1.61 Sv

[47°09′07″S, 126°43′23″W] Reading: 0.01 Sv

[47°09′00″S, 126°43′57″W] Reading: 0.09000 PPM

@mckinley@twtxt.net Wow, I was not aware, that there are different kinds of blackberries. But of course there are. Everything has all sorts of different species, why would it be different with these tasty guys? :-)

I just read up on them and – surprise, surprise – it turns out, the Himalayans are not native to most of Europe either. Doh! It gets even more interesting, their origin is unclear. Maybe Armenia and the Caucasus region. Fascinating!

[47°09′22″S, 126°43′31″W] Raw reading: 0x66CC27F1, offset +/-5

Telegram founder Pavel Durov arrested at French airport
Article URL: https://www.theguardian.com/media/article/2024/aug/24/telegram-app-founder-pavel-durov-arrested-at-french-airport

Comments URL: https://news.ycombinator.com/item?id=41341353

Points: 508

# Comments: 460 ⌘ Read more

[47°09′38″S, 126°43′20″W] Raw reading: 0x66C9BD31, offset +/-5

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

[47°09′58″S, 126°43′55″W] Reading: 0.72000 PPM

Correct, @bender@twtxt.net. Since the very beginning, my twtxt flow is very flawed. But it turns out to be an advantage for this sort of problem. :-) I still use the official (but patched) twtxt client by buckket to actually fetch and fill the cache. I think one of of the patches played around with the error reporting. This way, any problems with fetching or parsing feeds show up immediately. Once I think, I’ve seen enough errors, I unsubscribe.

tt is just a viewer into the cache. The read statuses are stored in a separate database file.

It also happened a few times, that I thought some feed was permanently dead and removed it from my list. But then, others mentioned it, so I resubscribed.

@movq@www.uninformativ.de, that would be a nice addition. :-) I would also love the ability to hide/not show the hash when reading twtxts (after all, that’s on the header on each “email”). Could that be added as a user configurable toggle?

[47°09′37″S, 126°43′38″W] Reading: 1.85 Sv

[47°09′50″S, 126°43′56″W] Reading: 1.90000 PPM

[47°09′23″S, 126°43′11″W] Reading: 1.52000 PPM

[47°09′32″S, 126°43′19″W] Raw reading: 0x66BCFEB1, offset +/-2

[47°09′29″S, 126°43′02″W] Raw reading: 0x66BCD481, offset +/-1

New Research Reveals AI Lacks Independent Learning, Poses No Existential Threat
ZipNada writes: New research reveals that large language models (LLMs) like ChatGPT cannot learn independently or acquire new skills without explicit instructions, making them predictable and controllable. The study dispels fears of these models developing complex reasoning abilities, emphasizing that while LLMs can genera … ⌘ Read more

Morphotrophic by Greg Egan is built around an idea for how life on Earth could have worked out differently. It gets increasingly strange and interesting as the story progresses. My partner and I finished it last night and thoroughly enjoyed it. The beginning is free online: https://gregegan.net/MORPHOTROPHIC/00/MorphotrophicExcerpt.html #scifi #reading

[47°09′36″S, 126°43′12″W] Raw reading: 0x66B31B71, offset +/-5

[47°09′29″S, 126°43′26″W] Raw reading: 0x66B0F701, offset +/-1

[47°09′05″S, 126°43′11″W] Reading: 0.56 Sv

[47°09′09″S, 126°43′08″W] Reading: 0.04 Sv

[47°09′48″S, 126°43′00″W] Reading: 0.94 Sv

[47°09′45″S, 126°43′52″W] Raw reading: 0x66A9C4D1, offset +/-1

[47°09′18″S, 126°43′35″W] Reading: 1.92000 PPM

O meu novo salva-vidas na hora de montar um novo site #vuejs sem as tretas dos build systems: Vue3 Tiny Template, da inimitável @b0rk@b0rk

Every time I start a Vue project, I get confused and waste 15 minutes reading the documentation and remembering how to set up Vue.

So this is a tiny template I made for myself so that I can avoid that next time. I don’t use a build process, instead it uses the CDN version of Vue and a single HTML / JS file.

https://github.com/jvns/vue3-tiny-template

[47°09′38″S, 126°43′36″W] Raw reading: 0x66A66B02, offset +/-5

[47°09′47″S, 126°43′25″W] Reading: 1.34 Sv

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

[47°09′51″S, 126°43′10″W] Raw reading: 0x669FD381, offset +/-3

[47°09′51″S, 126°43′18″W] Reading: 0.52000 PPM

[47°09′55″S, 126°43′24″W] Raw reading: 0x669B98B2, offset +/-2

[47°09′04″S, 126°43′03″W] Reading: 0.13 Sv

Microsoft Outage Hits Users Worldwide, Leading To Canceled Flights
Microsoft grappled with a major service outage, leaving users across the world unable to access its cloud computing platforms and causing airlines to cancel flights. From a report: Thousands of users across the world reported problems with Microsoft 365 apps and services to Downdetector.com, a website that tracks service disruptions. “We’re inve … ⌘ Read more

[47°09′55″S, 126°43′42″W] Raw reading: 0x66996631, offset +/-3

[47°09′11″S, 126°43′58″W] Reading: 0.67 Sv

[47°09′52″S, 126°43′57″W] Reading: 0.00000 PPM

[47°09′09″S, 126°43′51″W] Raw reading: 0x66950131, offset +/-2

So updated. Seems to duplicate here in the ui. And what is this “Read More” on every twt now?