/https://baldo.cat/media/photos/IMG_1890.jpeg) #catsoftwtxt
/https://baldo.cat/media/photos/IMG_1890.jpeg) #catsoftwtxt
> How do we identify a feed?
It cannot be the URL, because the author _could_ change where they serve it from. This was as "good" as we could get it, but time and time again this has proven to be problematic for, well, a few folks that change their mind, which frankly should be allowed 😅
> How do we identify a feed?
It cannot be the URL, because the author _could_ change where they serve it from. This was as "good" as we could get it, but time and time again this has proven to be problematic for, well, a few folks that change their mind, which frankly should be allowed 😅
2024-09-05T13:37:40Z (edit:mp6ox4a) Hello world!
2024-09-05T13:37:40Z (edit:mp6ox4a) Hello world!
2024-09-05T13:37:40+00:00 (edit:mp6ox4a) Hello world!
2024-09-05T13:37:40+00:00 (edit:mp6ox4a) Hello world!
# url = metadata field, which is what I _believe_ @cuaxolotl has just done, though I'm not 100% certain, I'm like 98% sure haha 😝
# url = metadata field, which is what I _believe_ @cuaxolotl has just done, though I'm not 100% certain, I'm like 98% sure haha 😝
Yes, I'm all for dedicated message IDs. That would be a whole new format then. But I would be fine with it. The only thing is that all our clients have to be touched. At the moment, I do not worry about spoofing (however, I definitely should).
But the great thing about the current system is that nobody can spoof message IDs. 🤔 When you think about it, message IDs in e-mails only work because (almost) everybody plays fair. Nothing stops me from using the same
Message-ID header in *each and every mail*, that would break e-mail threading all the time.In Yarn, twt hashes are *derived* from twt content and feed metadata. That is pretty elegant and I’d hate see us lose that property.
If we wanted to allow editing twts, we could do something like this:
2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello world!
Here,
mp6ox4a would be a “partial hash”: To get the actual hash of this twt, you’d concatenate the feed’s URL and mp6ox4a and get, say, hlnw5ha. (Pretty similar to the current system.) When people reply to this twt, they would have to do this:2024-09-05T14:57:14+00:00 (~bpt74ka) (#hlnw5ha) Yes, hello!
That second twt has a partial hash of
bpt74ka and is a reply to the full hash hlnw5ha. The author of the “Hello world!” twt could then edit their twt and change it to 2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello friends! or whatever. Threading wouldn’t break.Would this be worth it? It’s certainly not backwards-compatible. 😂
But the great thing about the current system is that nobody can spoof message IDs. 🤔 When you think about it, message IDs in e-mails only work because (almost) everybody plays fair. Nothing stops me from using the same
Message-ID header in *each and every mail*, that would break e-mail threading all the time.In Yarn, twt hashes are *derived* from twt content and feed metadata. That is pretty elegant and I’d hate see us lose that property.
If we wanted to allow editing twts, we could do something like this:
2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello world!
Here,
mp6ox4a would be a “partial hash”: To get the actual hash of this twt, you’d concatenate the feed’s URL and mp6ox4a and get, say, hlnw5ha. (Pretty similar to the current system.) When people reply to this twt, they would have to do this:2024-09-05T14:57:14+00:00 (~bpt74ka) (#hlnw5ha) Yes, hello!
That second twt has a partial hash of
bpt74ka and is a reply to the full hash hlnw5ha. The author of the “Hello world!” twt could then edit their twt and change it to 2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello friends! or whatever. Threading wouldn’t break.Would this be worth it? It’s certainly not backwards-compatible. 😂
But the great thing about the current system is that nobody can spoof message IDs. 🤔 When you think about it, message IDs in e-mails only work because (almost) everybody plays fair. Nothing stops me from using the same
Message-ID header in *each and every mail*, that would break e-mail threading all the time.In Yarn, twt hashes are *derived* from twt content and feed metadata. That is pretty elegant and I’d hate see us lose that property.
If we wanted to allow editing twts, we could do something like this:
2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello world!
Here,
mp6ox4a would be a “partial hash”: To get the actual hash of this twt, you’d concatenate the feed’s URL and mp6ox4a and get, say, hlnw5ha. (Pretty similar to the current system.) When people reply to this twt, they would have to do this:2024-09-05T14:57:14+00:00 (~bpt74ka) (#hlnw5ha) Yes, hello!
That second twt has a partial hash of
bpt74ka and is a reply to the full hash hlnw5ha. The author of the “Hello world!” twt could then edit their twt and change it to 2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello friends! or whatever. Threading wouldn’t break.Would this be worth it? It’s certainly not backwards-compatible. 😂
But the great thing about the current system is that nobody can spoof message IDs. 🤔 When you think about it, message IDs in e-mails only work because (almost) everybody plays fair. Nothing stops me from using the same
Message-ID header in *each and every mail*, that would break e-mail threading all the time.In Yarn, twt hashes are *derived* from twt content and feed metadata. That is pretty elegant and I’d hate see us lose that property.
If we wanted to allow editing twts, we could do something like this:
2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello world!
Here,
mp6ox4a would be a “partial hash”: To get the actual hash of this twt, you’d concatenate the feed’s URL and mp6ox4a and get, say, hlnw5ha. (Pretty similar to the current system.) When people reply to this twt, they would have to do this:2024-09-05T14:57:14+00:00\t(~bpt74ka) (#hlnw5ha) Yes, hello!
That second twt has a partial hash of
bpt74ka and is a reply to the full hash hlnw5ha. The author of the “Hello world!” twt could then edit their twt and change it to 2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello friends! or whatever. Threading wouldn’t break.Would this be worth it? It’s certainly not backwards-compatible. 😂
url metdata key of your feed?
# url = https://sunshinegardens.org/~xj9/twtxt/tw.txt
Was this at one point
# url = https://sunshinegardens.org/users/xj9/twtxt/tw.txt?
url metdata key of your feed?
# url = https://sunshinegardens.org/~xj9/twtxt/tw.txt
Was this at one point
# url = https://sunshinegardens.org/users/xj9/twtxt/tw.txt?
Which links to https://github.com/musingstudio/go-subclub> A Go (golang) library for interacting with the sub.club API.
So I got curious and had a peek 👀
> Let's fund the Fediverse
>> Posting or hosting on the open social networks no longer means you have to do it for free. Developer Preview now available.
And further down:
> Monetize your feeds
>> If you post quality content and you've developed a loyal audience, you should be able to ask your most passionate followers to support you with a premium subscription.
>>
>> That's a promise not available on the Fediverse ...until now.
Hmmm 🤔
Which links to https://github.com/musingstudio/go-subclub> A Go (golang) library for interacting with the sub.club API.
So I got curious and had a peek 👀
> Let's fund the Fediverse
>> Posting or hosting on the open social networks no longer means you have to do it for free. Developer Preview now available.
And further down:
> Monetize your feeds
>> If you post quality content and you've developed a loyal audience, you should be able to ask your most passionate followers to support you with a premium subscription.
>>
>> That's a promise not available on the Fediverse ...until now.
Hmmm 🤔
quick run around the park. boy was it hot!
#running
quick run around the park. boy was it hot!
#running
quick run around the park. boy was it hot!
#running
#catsoftwtxt
#catsoftwtxt
/https://duque-terron.cat/media/photos/RR3dbmtHyW7NLxA6GvCXYS.jpeg) #catsoftwtxt
/https://baldo.cat/media/photos/2MVL3rM6FXUSawBTvzsu6A.jpg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
Screenshot of an email, allegedly from Sendgrid The first give away is the sender,
sendgrid@autovitalsinc.com. Not Sengrid. Now, check the URL on the link provided to check the account activity:
https://u906946.ct.sendgrid.net/ls/click?upn=u001.eXk7eIEvNT22LuyWQ0fseoc5VY1jItvxPoavh2wfNVs292YMzvTAPj5D6nek1U6K7UfW_AsM5Hq3TBeAGlZrT-2F3g23iWCcJRPGZ-2B58DJxpgMgOTjgWklNQiAdGiHqmR6FFVhfWZJhnu1PSRslMuKGg1XNZs5e1lGu8kmdKhv7otlghl6qLMXiiXYZcvaUB5NruWwSBFcLdvi31NY-2Fru5oyrcrugm2iLYA0u5TiufyvA7SNTo3sDHx6WtS-2FmfEyN2svb9k1S4QGRFhuDseidMiFm0f9Q-3D-3D
I was curious, so I follow it on my dedicated VM for these kind of things. It took me to a page looking exactly like a Sendgrid login, with a
sendgrid.net URL. Upon entering yourmotherisahamster@gmail.com, as username, and yourfathersmellsofelderberries as password, it sent me to https://screenprank.com/gandalf/.It was well done. This morning the same link renders a blank page with a "Not found" link that takes you to a
404. Hmm...
Los viernes son lunes al revés. ⌘ Read more****
Esto es así ⌘ Read more****