Yarns https://search.twtxt.net/twtxt.txt Remove
abucci https://anthony.buc.ci/user/abucci/twtxt.txt Remove
adi https://twtxt.net/user/adi/twtxt.txt Remove
aelaraji@aelaraji.com https://aelaraji.com/twtxt.txt Remove
akkartik http://akkartik.name/twtxt.txt Remove
anth@a.9srv.net http://a.9srv.net/tw.txt Remove
antonio@twtxt.net https://twtxt.net/user/antonio/twtxt.txt Remove
apptester@twtxt.net https://twtxt.net/user/apptester/twtxt.txt Remove
bender https://twtxt.net/user/bender/twtxt.txt Remove
bmallred@staystrong.run https://staystrong.run/user/bmallred/twtxt.txt Remove
cncf https://feeds.twtxt.net/cncf/twtxt.txt Remove
cuaxolotl@sunshinegardens.org https://sunshinegardens.org/~xj9/twtxt/tw.txt Remove
darch@neotxt.dk https://neotxt.dk/user/darch/twtxt.txt Remove
darren@twtxt.net https://twtxt.net/user/darren/twtxt.txt Remove
eapl.me@eapl.me https://eapl.me/twtxt.txt Remove
eldersnake@we.loveprivacy.club https://we.loveprivacy.club/user/eldersnake/twtxt.txt Remove
falsifian@www.falsifian.org https://www.falsifian.org/twtxt.txt Remove
friendlyjordies@feeds.twtxt.net https://feeds.twtxt.net/friendlyjordies/twtxt.txt Remove
github_blog https://feeds.twtxt.net/github_blog/twtxt.txt Remove
golang_news https://feeds.twtxt.net/golang_news/twtxt.txt Remove
hacker-news-newest https://feeds.twtxt.net/hacker-news-newest/twtxt.txt Remove
home_datacenter@twtxt.net https://twtxt.net/user/home_datacenter/twtxt.txt Remove
integza@feeds.twtxt.net https://feeds.twtxt.net/integza/twtxt.txt Remove
james@yarn.mills.io https://yarn.mills.io/user/james/twtxt.txt Remove
jmjl@tilde.green https://tilde.green/~jmjl/twtxt.txt Remove
johanbove@johanbove.info https://johanbove.info/twtxt.txt Remove
justamoment@twtxt.net https://twtxt.net/user/justamoment/twtxt.txt Remove
kt84@twtxt.net https://twtxt.net/user/kt84/twtxt.txt Remove
linux_gizmos https://feeds.twtxt.net/linux_gizmos/twtxt.txt Remove
local_wonders@twtxt.net https://twtxt.net/user/local_wonders/twtxt.txt Remove
lyse https://lyse.isobeef.org/twtxt.txt Remove
lyxal@twtxt.net https://twtxt.net/user/lyxal/twtxt.txt Remove
mckinley https://twtxt.net/user/mckinley/twtxt.txt Remove
mckinley@mckinley.cc https://mckinley.cc/twtxt.txt Remove
mearaj@twtxt.net https://twtxt.net/user/mearaj/twtxt.txt Remove
movq https://www.uninformativ.de/twtxt.txt Remove
news@twtxt.net https://twtxt.net/user/news/twtxt.txt Remove
ocdtrekkie@twtxt.net https://twtxt.net/user/ocdtrekkie/twtxt.txt Remove
oevl@twtxt.net https://twtxt.net/user/oevl/twtxt.txt Remove
off_grid_living@twtxt.net https://twtxt.net/user/off_grid_living/twtxt.txt Remove
prologic https://twtxt.net/user/prologic/twtxt.txt Remove
prx@si3t.ch https://si3t.ch/twtxt.txt Remove
quark@ferengi.one https://ferengi.one/twtxt.txt Remove
recipes@twtxt.net https://twtxt.net/user/recipes/twtxt.txt Remove
rocknswap@twtxt.net https://twtxt.net/user/rocknswap/twtxt.txt Remove
saltyim@twtxt.net https://twtxt.net/user/saltyim/twtxt.txt Remove
shreyan@twtxt.net https://twtxt.net/user/shreyan/twtxt.txt Remove
slashdot@feeds.twtxt.net https://feeds.twtxt.net/slashdot/twtxt.txt Remove
sorenpeter@darch.dk http://darch.dk/twtxt.txt Remove
stigatle@yarn.stigatle.no https://yarn.stigatle.no/user/stigatle/twtxt.txt Remove
support@twtxt.net https://twtxt.net/user/support/twtxt.txt Remove
thecanine@twtxt.net https://twtxt.net/user/thecanine/twtxt.txt Remove
thejuicemedia https://feeds.twtxt.net/thejuicemedia/twtxt.txt Remove
thiegui@twtxt.net https://twtxt.net/user/thiegui/twtxt.txt Remove
tiktok https://feeds.twtxt.net/tiktok/twtxt.txt Remove
tkanos@twtxt.net https://twtxt.net/user/tkanos/twtxt.txt Remove
twilightsparkle@twtxt.net https://twtxt.net/user/twilightsparkle/twtxt.txt Remove
unexplained_mysteries https://feeds.twtxt.net/unexplained_mysteries/twtxt.txt Remove
xkcd https://feeds.twtxt.net/xkcd/twtxt.txt Remove
xuu@txt.sour.is https://txt.sour.is/user/xuu/twtxt.txt Remove
yarn_police@twtxt.net https://twtxt.net/user/yarn_police/twtxt.txt Remove
prologic
Reply to #ku6lzaa
@bender 🤣
3 hours ago
💬 Reply
bender
Reply to #ku6lzaa
Well, we can’t have it both ways! 😅 Should we assume twtxt are read by clients, and not worry about something humans won’t see? 🤭
3 hours ago
💬 Reply
prologic
Reply to #ku6lzaa
@falsifian Yeah that's why we made them short 😅
3 hours ago
💬 Reply
prologic
Reply to #ku6lzaa
@falsifian 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.
5 hours ago
💬 Reply
prologic
Reply to #ku6lzaa
@falsifian 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?
5 hours ago
💬 Reply
prologic
Reply to #ijwxx7q
@off_grid_living Aww thanks! 🤗
7 hours ago
💬 Reply
prologic
Reply to #6shod5q
There are certainly improvements that can be made to this tool.🤞
7 hours ago
💬 Reply
stigatle
Reply to #r3mkxya
@lyse brr, we have the same here. Starting to get cold riding motorcycle to work in the morning.
10 hours ago
💬 Reply
bender
Reply to #6shod5q
The missing context makes it kind of hard to follow.
16 hours ago
💬 Reply
falsifian
Reply to #pvju5cq
@mckinley
> > HTTPS is supposed to do [verification] anyway.
>
> TLS provides verification that nobody is tampering with or snooping on your connection to a server. It doesn't, for example, verify that a file downloaded from server A is from the same entity as the one from server B.
I was confused by this response for a while, but now I think I understand what you're getting at. You are pointing out that with signed feeds, I can verify the authenticity of a feed without accessing the original server, whereas with HTTPS I can't verify a feed unless I download it myself from the origin server. Is that right?
I.e. if the HTTPS origin server is online and I don't mind taking the time and bandwidth to contact it, then perhaps signed feeds offer no advantage, but if the origin server might not be online, or I want to download a big archive of lots of feeds at once without contacting each server individually, then I need signed feeds.
> > feed locations [being] URLs gives some flexibility
>
> It does give flexibility, but perhaps we should have made them URIs instead for even more flexibility. Then, you could use a tag URI, `urn:uuid:*`, or a regular old URL if you wanted to. The spec seems to indicate that the `url` tag should be a working URL that clients can use to find a copy of the feed, optionally at multiple locations. I'm not very familiar with IP{F,N}S but if it ensures you own an identifier forever and that identifier points to a current copy of your feed, it could be a great way to fix it on an individual basis without breaking any specs :)
I'm also not very familiar with IPFS or IPNS.
I haven't been following the other twts about signatures carefully. I just hope whatever you smart people come up with will be backwards-compatible so it still works if I'm too lazy to change how I publish my feed :-)
23 hours ago
💬 Reply
aelaraji
Reply to #6shod5q
edit: [...] have an unjustified* [...]
1 day ago
💬 Reply
aelaraji
Reply to #6shod5q
@prologic 🤯 HOLLY! ... I'm definitely adding this to my Jenny's `publish_command` script!! THANK YOU! Now my website has TWO pages instead of just a boring one 😂
New: Log Page
1 day ago
💬 Reply
bender
Reply to #2dhxnja
@prologic does it renders threads nicely, or is it a straight, flat, timeline.
1 day ago
💬 Reply
aelaraji
Reply to #6shod5q
@prologic Will try it right away!
1 day ago
💬 Reply
prologic
Reply to #bhnihfq
Many thanks!
1 day ago
💬 Reply
prologic
Reply to #6shod5q
@aelaraji Have you considered https://git.mills.io/yarnsocial/twtxt2html
1 day ago
💬 Reply
aelaraji
@sorenpeter !! 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.
1 day ago
💬 Reply
lyse
Reply to #kmopgpq
Ta, @bender! Correct, apart from resizing, no further processing on my end. That's just the Japanese sunset photo engineer's magic. :-) In all it's original glory (3.2 MiB): https://lyse.isobeef.org/abendhimmel-2024-09-13/02.JPG
1 day ago
💬 Reply
lyse
Reply to #nfuyjyq
@off_grid_living Looks like you're describing a captcha. They do not really work. Bots seem to solve them, too.
1 day ago
💬 Reply
lyse
Reply to #r3mkxya
@movq Thanks! Yeah, one week for autumn and spring must be enough. Or so the weather thinks. Looks like there is only on or off.
1 day ago
💬 Reply
bender
Reply to #kmopgpq
Because it needs to be seeing bigger!
1 day ago
💬 Reply
bender
Reply to #kmopgpq
@lyse pretty cool! No processing, those are the colours the camera saw, right? Amazing!
1 day ago
💬 Reply
aelaraji
Reply to #bhnihfq
@prologic Hey, Best wishes! Have fun! 🥳
1 day ago
💬 Reply
lyse
Reply to #bhnihfq
@prologic Oh, that's a lovely campfire! Seeing them always makes me smile. Enjoy your time in nature with your loved ones.
1 day ago
💬 Reply
lyse
Cool sunset when I went to the scouts: https://lyse.isobeef.org/abendhimmel-2024-09-13/
1 day ago
💬 Reply
xuu
Reply to #h7zeenq
you can just have a web address.. i added mine.. though i think they have changed up the protocol so my key doesn't seem to work anymore. https://key.sour.is/id/me@sour.is
1 day ago
💬 Reply
bender
Now the wait starts. 😩😂
1 day ago
💬 Reply
prologic
Reply to #bhnihfq
@bender Thanks! 🤗 -- I know it will 🤣
1 day ago
💬 Reply
bender
Reply to #bhnihfq
@prologic I will ping you on the 15th. Enjoy the weekend, mate! Don't worry, the Mills DC will continue to run 😂. Disconnect, and have fun!
1 day ago
💬 Reply
prologic
Out camping with the family this weekend for my birthday 🥳
1 day ago
💬 Reply
prologic
Reply to #xzyxyva
I think so 😅 Thanks$!🙇♂️
1 day ago
💬 Reply
bender
Reply to #xzyxyva
@prologic you want this, https://key.sour.is/id/me@sour.is?
1 day ago
💬 Reply
prologic
Reply to #rh6gtwq
@aelaraji Hah interesting 🤔
2 days ago
💬 Reply
aelaraji
Reply to #rh6gtwq
@prologic you should see This ! The devs were already trying to figure things out for TWTXT and Yarn.social 😃
2 days ago
💬 Reply
shreyan
been rather uninterested in technology lately for some reason. it's probably the US Election's fault, since I live in the US and all
2 days ago
💬 Reply
aelaraji
Reply to #sfpgcyq
@prologic Thanks! I tried 😅
2 days ago
💬 Reply
aelaraji
Reply to #h7zeenq
@prologic No luck so far and it looks like I have plenty of reading to do tomorrow morning. 😅
2 days ago
💬 Reply
hacker-news-newest
**Notes on OpenAI's new o1 chain-of-thought models**
Article URL: https://simonwillison.net/2024/Sep/12/openai-o1/
Comments URL: https://news.ycombinator.com/item?id=41527143
Points: 503
\# Comments: 424 ⌘ Read more
2 days ago
💬 Reply
prologic
@xuu What's the keyoxide thingy you wrote/built? 🤔 What's your URI/profile? 🤔
2 days ago
💬 Reply
prologic
Reply to #h7zeenq
@aelaraji Sounds like it would work 👌 Though I've not tried or invested anytime into proofs and claims type things so far 🤔
2 days ago
💬 Reply
prologic
Reply to #sfpgcyq
@aelaraji Nice write up!
2 days ago
💬 Reply
aelaraji
Reply to #h7zeenq
@bender Does it have to. To my understanding, all you have to do is to add in a claim to your Twtxt feed link into your key, update your profile and post one of These Identity formats to your Twtxt file/Profile...
Give me a couple of minutes, I'll give it a try myself 😉
2 days ago
💬 Reply
aelaraji
Reply to #sfpgcyq
@prologic well...
> how would that work exactly?
To my limited knowledge, Keyoxide is an open source project offering different tools for verifying one's online persona(s). That's done by either A) creating an Ariande Profile using the web interface, a CLI. or B) Just using your GPG key. Either way, you add in Identity claims to your different profiles, links and whatnot, and finally advertise your profile ... Then there is a second set of Mobile/Web clients and CLI your correspondents can use to check your identity claims. I think of them like the front-ends of GPG Keyservers (which keyoxide leverages for verification when you opt for the GPG Key method), where you verify profiles using links, Key IDs and Fingerprints...
> Who maintains cox site? Is it centralized or decentralized can be relied upon?
- Maintainers? Definitely not me, but here's their Git stuff and OpenCollective page ...
- Both ASP and Keyoxide Webtools can be self-hosted. I don't see a central authority here... + As mentioned on their FAQ page the whole process can be done manually, so you don't have to relay on any one/thing if you don't want to, the whole thing is just another tool for convenience (with a bit of eye candy).
> Does that mean then that every user is required to have a cox side profile?
Nop. But it looks like a nice option to prove that I'm the same person to whom that may concern if I ever change my Twtxt URL, host/join a yarn pod or if I reach out on other platforms to someone I've met in her. Otherwise I'm just happy exchanging GPG keys or confirm the change IRL at a coffee shop or something. 😁
2 days ago
💬 Reply
movq
Reply to #r3mkxya
@lyse Wow, those are some great shots. Fall is finally here! 😍 (Might be a bit exaggerated by my redshift. 😅)
That temperature drop was pretty sudden. Boom, cold, no warning. Give me some time to adapt, man! 😂
2 days ago
💬 Reply
lyse
20° temperature drop in just a hand full of days. Ooof. We went on a stroll at 10°C today. I could have used a beanie, my ears were very cold. The sun was out, but hardly any people. Very nice. Also, no wind.
It was nice to finally hear a few birds singing again, although it was still fairly silent. The sun gave us a nice show. In hindsight, we should have stayed at the summit a bit longer. In the forest, we missed the very best, crazy red sky. We could only see parts shimmering through the tree lines.
https://lyse.isobeef.org/waldspaziergang-2024-09-12/
2 days ago
💬 Reply
off_grid_living
I just received a thought... When you visit a server home page, or any page, why can't the server sent you a page full of images, asking the human to click on three ants, or four ducks, or two trees, or five cars?
Can an AI machine do such a thing? After a few seconds of human time, the page they wish is downloaded for them. Would this work all you computer experts? (I am getting sick of bots reading my content and stealing my copyright)
2 days ago
💬 Reply
xjix
Reply to #mhtocjq
involving public keys get dicey pretty fast, but it does promote the ability to migrate feeds while maintaining a chain of custody, so to speak. something like minisign would be a good simple place to start, but that doesn't even touch on key revocation, rotation, &c. the url as the feed id may not be the best thing, but its relatively simple.
I had written up some idea for using BEP 46 as a source of truth, but it has similar problems. maybe something with btlink as an option to secure your feed based on a key id without baking that functionality into the client logic, but if most clients would just use the http gateway so they wouldn't actually be able to validate anything.
2 days ago
💬 Reply
bender
Reply to #h7zeenq
@aelaraji twtxt isn't one of the available proofs: https://docs.keyoxide.org/
2 days ago
💬 Reply
hacker-news-newest
**OpenAI O1 Model**
Article URL: https://openai.com/index/learning-to-reason-with-llms/
Comments URL: https://news.ycombinator.com/item?id=41523070
Points: 541
\# Comments: 330 ⌘ Read more
2 days ago
💬 Reply
cncf
**What’s new in CRI-O 1.31**
Project post originally published on Github by Sascha Grunert The CRI-O maintainers are happy and proud to announce that CRI-O v1.31.0 has been released! This brand new version contains a large list of cool new features, bug fixes and smaller... ⌘ Read more
2 days ago
💬 Reply