prologic
twtxt.net"Problems are Solved by Method" 🇦🇺👨💻👨🦯🏹♔ 🏓⚯ 👨👩👧👧🛥 -- James Mills (operator of twtxt.net / creator of Yarn.social 🧶)
↳
In-reply-to
»
Happy Birthday my Son, I guess you are still camping and celebrating your special day with family.
You were born on a Wednesday on 15 September 1982 at Belmont Hospital, which is a lovely low set place outside Newcastle, as you were brought home to live with my Mum and Dad at Sunshine in our first few months as a married couple, at Sunshine near Morriset NSW. Enjoy your special day.
⤋ Read More
@lyse@lyse.isobeef.org Thanks!
↳
In-reply-to
»
@prologic Some criticisms and a possible alternative direction:
⤋ Read More
@falsifian@www.falsifian.org One of the nice things I think is that you can almost assuredly trust that the hash is a correct representation of the thread because it was computed via our content, addressing in the first place, so all you need to do yes copy it 👌
↳
In-reply-to
»
@prologic earlier you suggested extending hashes to 11 characters, but here's an argument that they should be even longer than that.
⤋ Read More
↳
In-reply-to
»
@prologic earlier you suggested extending hashes to 11 characters, but here's an argument that they should be even longer than that.
⤋ Read More
@falsifian@www.falsifian.org Yeah that’s why we made them short 😅
↳
In-reply-to
»
@prologic earlier you suggested extending hashes to 11 characters, but here's an argument that they should be even longer than that.
⤋ Read More
@falsifian@www.falsifian.org I think I wrote a very similar program and go myself actually and you’re right we do have to change the way we encode hashes.
↳
In-reply-to
»
@prologic earlier you suggested extending hashes to 11 characters, but here's an argument that they should be even longer than that.
⤋ Read More
@falsifian@www.falsifian.org All very good points 👌 by the way, how did you find two pieces of content that hash the same when taking the last N characters of the base32 and coded hash?
↳
In-reply-to
»
Happy Birthday my Son, I guess you are still camping and celebrating your special day with family.
You were born on a Wednesday on 15 September 1982 at Belmont Hospital, which is a lovely low set place outside Newcastle, as you were brought home to live with my Mum and Dad at Sunshine in our first few months as a married couple. If you subtract 9 months and a bit, the term of your pregnancy, that makes your conception date a few days after our marriage, and the first time both of us had sexual intercourse together, sometime around Friday Saturday or Sunday beginning on 4th December 1981. We were married at Gosford and arrived in the Sydney Hilton Hotel on that evening Thursday 3rd December, it was such a quiet place so far above the street level, the tiny cars below looked like ants. Because you were the first child, we have special sessions each week to attend to learn how to be parents after your birth, and care for the Mum during your delivery. If I remember yours was a breech birth, the doctor had to turn you around somewhat before the normal course of action took place. Karen was brave, being only on gas. Enjoy your special day.
⤋ Read More
@off_grid_living@twtxt.net Aww thanks! 🤗
↳
In-reply-to
»
@sorenpeter !! I freaking love your Timeline ... I kind of have an justified PHP phobia 😅 but, I'm definitely thinking about giving it a try!
⤋ Read More
There are certainly improvements that can be made to this tool.🤞
↳
In-reply-to
»
@sorenpeter !! I freaking love your Timeline ... I kind of have an justified PHP phobia 😅 but, I'm definitely thinking about giving it a try!
⤋ Read More
@aelaraji@aelaraji.com Have you considered https://git.mills.io/yarnsocial/twtxt2html
↳
In-reply-to
»
Out camping with the family this weekend for my birthday 🥳 Media
⤋ Read More
@bender@twtxt.net Thanks! 🤗 – I know it will 🤣
Out camping with the family this weekend for my birthday 🥳 
↳
In-reply-to
»
@xuu What's the keyoxide thingy you wrote/built? 🤔 What's your URI/profile? 🤔
⤋ Read More
I think so 😅 Thanks$!🙇♂️
@xuu@txt.sour.is What’s the keyoxide thingy you wrote/built? 🤔 What’s your URI/profile? 🤔
↳
In-reply-to
»
@prologic can't one just link to a keyoxide profile with a link to their Twtxt feed for identity or something?
⤋ Read More
@aelaraji@aelaraji.com Sounds like it would work 👌 Though I’ve not tried or invested anytime into proofs and claims type things so far 🤔
↳
In-reply-to
»
@aelaraji how would that work exactly? Does that mean then that every user is required to have a cox side profile? Who maintains cox site? Is it centralized or decentralized can be relied upon?
⤋ Read More
@aelaraji@aelaraji.com Nice write up!
↳
In-reply-to
»
@lyse This looks like a nice way to do it.
⤋ Read More
@aelaraji@aelaraji.com how would that work exactly? Does that mean then that every user is required to have a cox side profile? Who maintains cox site? Is it centralized or decentralized can be relied upon?
↳
In-reply-to
»
Ford Seeks Patent For Tech That Listens To Driver Conversations To Serve Ads
Ford is seeking a patent for technology that would allow it to tailor in-car advertising by listening to conversations among vehicle occupants, as well as by analyzing a car's historical location and other data, according to a patent application published late last month. The Record: "In one example, the controller may moni ... ⌘ Read more
⤋ Read More
Ford, the company can honestly go fuck themselves! No one ever asked or even thought to themselves:
Gee I wish my car would listen to my in-car conversations and serve me ads.
↳
In-reply-to
»
Ford Seeks Patent For Tech That Listens To Driver Conversations To Serve Ads
Ford is seeking a patent for technology that would allow it to tailor in-car advertising by listening to conversations among vehicle occupants, as well as by analyzing a car's historical location and other data, according to a patent application published late last month. The Record: "In one example, the controller may moni ... ⌘ Read more
⤋ Read More
@slashdot@feeds.twtxt.net i’ll get fucked! The US patent office should ban this immediately.
↳
In-reply-to
»
@bender Yes, they do 🤣 Implicitly, or threading would never work at all 😅 Nor lookups 🤣 They are used as keys. Think of them like a primary key in a database or index. I totally get where you're coming from, but there are trade-offs with using Message/Thread Ids as opposed to Content Addressing (like we do) and I believe we would just encounter other problems by doing so.
⤋ Read More
@xuu@txt.sour.is True 😅 I guess it comes down to our risk appetite and the attack vectors we’re trying to solve for 🤔
↳
In-reply-to
»
IMO we just have to fix the identity problem and figure out how to detect or support edits.
⤋ Read More
@bender@twtxt.net yes I agree.
↳
In-reply-to
»
@falsifian In my opinion it was a mistake that we defined the first
⤋ Read More
url field in the feed to define the URL for hashing. It should have been the last encountered one. Then, assuming append-style feeds, you could override the old URL with a new one from a certain point on:
@bender@twtxt.net there is a certain simplicity to that. 😅
↳
In-reply-to
»
@bender Yes, they do 🤣 Implicitly, or threading would never work at all 😅 Nor lookups 🤣 They are used as keys. Think of them like a primary key in a database or index. I totally get where you're coming from, but there are trade-offs with using Message/Thread Ids as opposed to Content Addressing (like we do) and I believe we would just encounter other problems by doing so.
⤋ Read More
@xuu@txt.sour.is it’s not really strictly required if we’re just talking about identity though right? If we’re talking about encryption then yes I agree rotate and keys becomes very important if you want to have attributes like perfect forward secrecy.
↳
In-reply-to
»
the right way to solve this is to use public/private key(s) where you actually have a public key fingerprint as your feed’s unique identity that never changes.
⤋ Read More
@xuu@txt.sour.is that could work too, but that requires a random value, a set of keys and signature verification of the value, which I don’t really have a problem with.
↳
In-reply-to
»
IMO we just have to fix the identity problem and figure out how to detect or support edits.
⤋ Read More
@xuu@txt.sour.is yes I’m less concerned about solving the integrity part of the problem of whether we can trust that the content of a feed is actually written by certain author, however, that’s not to say that we shouldn’t think about also leveraging keys to be able to do that maybe it’s an optional feature?
↳
In-reply-to
»
Interesting.. QUIC isn't very quick over fast internet.
⤋ Read More
What were the recommended mitigations?
↳
In-reply-to
»
@lyse This looks like a nice way to do it.
⤋ Read More
IMO we just have to fix the identity problem and figure out how to detect or support edits.
↳
In-reply-to
»
@lyse This looks like a nice way to do it.
⤋ Read More
@sorenpeter@darch.dk No, this is what I want to avoid. For many reasons I stated before, content addressing or hashing is far better here for threading in a decentralized way.
↳
In-reply-to
»
@lyse This looks like a nice way to do it.
⤋ Read More
@lyse@lyse.isobeef.org I personally think that we just go with a magic timestamp approach. It’s simpler and easier to implement across the major clients that are still actively developed.
The question is how much time do we give ourselves as we’re all a bit time poor and I can’t imagine we would do this quickly.
↳
In-reply-to
»
It’s one of those days.
⤋ Read More
@movq@www.uninformativ.de if you do win the lottery, don’t forget to include us so we can all join in and share the things that we like to tinker with instead of this whole rat race. 🤣
↳
In-reply-to
»
Getting ready for the Apple Event. Are you watching it live, @prologic, or afterwards? :-P
⤋ Read More
@bender@twtxt.net Big photo capability upgrade?
↳
In-reply-to
»
@cuaxolotl Ah, thanks for reporting back! Okay, so you’re basically manually “crawling” feeds right now. 🤔 What do you think about the idea of adding something like
⤋ Read More
# follow_notify = gemini://foo/bar to your feed’s metadata, so that clients who follow you can ping that URL every now and then? How would you even notice that, do you regularly read your gemini logs? 🤔
@aelaraji@aelaraji.com Nice hack! 👌
↳
In-reply-to
»
Getting ready for the Apple Event. Are you watching it live, @prologic, or afterwards? :-P
⤋ Read More
@bender@twtxt.net I doubt I’ll be able to watch it live 🤣 But by all means, please Yarns all the goodies 😅
↳
In-reply-to
»
@bender Ahh yeah sorry about that 🤣 You were getting confused between salty.im and salty. The later of which salty.im actually uses and formed the basis of everything else. It's a simple robust library and command-line tools with good test coverage. The lowest building block 😅
⤋ Read More
@bender@twtxt.net Kind of mirrored the ssh and ssh-keygen utilities. No reason really.
↳
In-reply-to
»
For example:
⤋ Read More
$ echo 'hello world' | ./salty -i ./test_ed25519 --ssh-key --sign
↳
In-reply-to
»
For example:
⤋ Read More
@bender@twtxt.net Ahh yeah sorry about that 🤣 You were getting confused between salty.im and salty. The later of which salty.im actually uses and formed the basis of everything else. It’s a simple robust library and command-line tools with good test coverage. The lowest building block 😅
↳
In-reply-to
»
It’s one of those days.
⤋ Read More
@movq@www.uninformativ.de That bad eh? 😅
↳
In-reply-to
»
@mckinley To answer some of your questions:
⤋ Read More
For example:
$ echo 'hello world' | ./salty -i ./test.key -s | ./salty -i ./test.key -v
# signed by: kex1yfzzthmsdlqhgwzafy9zpjze6a0asxf6y552dp4yhvq66a4jje0qxqapvd
hello world
↳
In-reply-to
»
@mckinley To answer some of your questions:
⤋ Read More
@bender@twtxt.net Yes of course it can 😅 Sorry I missed your question on IRC 😢
↳
In-reply-to
»
On the Subject of Feed Identities; I propose the following:
⤋ Read More
@mckinley@twtxt.net To answer some of your questions:
Are SSH signatures standardized and are there robust software libraries that can handle them? We’ll need a library in at least Python and Go to provide verified feed support with the currently used clients.
We already have this. Ed25519 libraries exist for all major languages. Aside from using ssh-keygen -Y sign and ssh-keygen -Y verify, you can also use the salty CLI itself (https://git.mills.io/prologic/salty), and I’m sure there are other command-line tools that could be used too.
If we all implemented this, every twt hash would suddenly change and every conversation thread we’ve ever had would at least lose its opening post.
Yes. This would happen, so we’d have to make a decision around this, either a) a cut-off point or b) some way to progressively transition.
↳
In-reply-to
»
🧮 USERS:1 FEEDS:2 TWTS:1087 ARCHIVED:78676 CACHE:2491 FOLLOWERS:17 FOLLOWING:14
⤋ Read More
@bender@twtxt.net Holy shit that pod is still alive?! 🤔
↳
In-reply-to
»
@falsifian In my opinion it was a mistake that we defined the first
⤋ Read More
url field in the feed to define the URL for hashing. It should have been the last encountered one. Then, assuming append-style feeds, you could override the old URL with a new one from a certain point on:
@sorenpeter@darch.dk WebFinger requires additional setup that whilsts helps to solve the “identity” problem in an “abstract” way, that extra infra that needs to be setup a) isn’t trivial and b) hard to support on “shared hosting”.
Sharing hosting is also the reason why you can’t just use part of a URL really.
↳
In-reply-to
»
@falsifian In my opinion it was a mistake that we defined the first
⤋ Read More
url field in the feed to define the URL for hashing. It should have been the last encountered one. Then, assuming append-style feeds, you could override the old URL with a new one from a certain point on:
@movq@www.uninformativ.de Peobably not and I wouldn’t expect them to either 😅
↳
In-reply-to
»
@prologic No, it’s all just speculation and I don’t like spreading rumors. 😅 It would be more interesting to hear from the twtxt folks themselves why they stopped working on the original twtxt.
⤋ Read More
But in all seriousness I’ve only ever wanted to improve Twtxt without sacrificing its simplicity too much.
↳
In-reply-to
»
@prologic No, it’s all just speculation and I don’t like spreading rumors. 😅 It would be more interesting to hear from the twtxt folks themselves why they stopped working on the original twtxt.
⤋ Read More
@movq@www.uninformativ.de Sorry haha I didn’t mean for it to sound like that 🤣
↳
In-reply-to
»
In fact, maybe your public key idea is compatible with my last point. Just come up with a url scheme that means "this feed's primary URL is actually a public key", and then feed authors can optionally switch to that.
⤋ Read More
@mckinley@twtxt.net Hmmm? Care to elaborate? 🤣
↳
In-reply-to
»
@movq Another idea: just hash the feed url and time, without the message content. And don't twt more than once per second.
⤋ Read More
@movq@www.uninformativ.de True 👌
↳
In-reply-to
»
@prologic No, it’s all just speculation and I don’t like spreading rumors. 😅 It would be more interesting to hear from the twtxt folks themselves why they stopped working on the original twtxt.
⤋ Read More
@movq@www.uninformativ.de Tbey all hate me for stomping on their precious dear twtxt 🤣
↳
In-reply-to
»
@falsifian In my opinion it was a mistake that we defined the first
⤋ Read More
url field in the feed to define the URL for hashing. It should have been the last encountered one. Then, assuming append-style feeds, you could override the old URL with a new one from a certain point on:
@lyse@lyse.isobeef.org Hmmm interesting idea 🤔