>LLMs don't have an understanding of anything. They can only regurgitate derivations of what they've been trained on and can't apply that to something new in the same ways that humans or even other animals can. The models are just so large that the illusion is impressive.
So true.
fun long run while we were at universal studios for a friends birthday. google maps thought there were some cut-throughs but was obviously wrong so just kind of winged it. was able to run around some of the "pioneer village" which was a good change in scenery.
#running
fun long run while we were at universal studios for a friends birthday. google maps thought there were some cut-throughs but was obviously wrong so just kind of winged it. was able to run around some of the "pioneer village" which was a good change in scenery.
#running
fun long run while we were at universal studios for a friends birthday. google maps thought there were some cut-throughs but was obviously wrong so just kind of winged it. was able to run around some of the "pioneer village" which was a good change in scenery.
#running
* https://upload.wikimedia.org/wikipedia/commons/a/a9/Nebelbank_in_der_W%C3%BCste_Namib_bei_Aus_%282018%29.jpg
* https://upload.wikimedia.org/wikipedia/commons/1/17/Space_Shuttle_Challenger_moving_through_fog.jpg
* https://upload.wikimedia.org/wikipedia/commons/9/96/Fog_Bow_%2819440790708%29.jpg
* https://upload.wikimedia.org/wikipedia/commons/a/ac/360_degrees_fogbow.jpg
> HTTP caching headers
Yes, absolutely, this should be mentioned in the spec. I’m guilty – when I first wrote my twtxt client, I forgot that
If-Modified-Since is a thing. 🤦
> HTTP caching headers
Yes, absolutely, this should be mentioned in the spec. I’m guilty – when I first wrote my twtxt client, I forgot that
If-Modified-Since is a thing. 🤦
> HTTP caching headers
Yes, absolutely, this should be mentioned in the spec. I’m guilty – when I first wrote my twtxt client, I forgot that
If-Modified-Since is a thing. 🤦
> HTTP caching headers
Yes, absolutely, this should be mentioned in the spec. I’m guilty – when I first wrote my twtxt client, I forgot that
If-Modified-Since is a thing. 🤦
> Regarding section 4 about feed discovery: Yeah, non-HTTP transport protocols are an issue as they do not have
User-Agent headers. How exactly do you envision the discovery_url to work, though?This is from a twt of mine from January 2022:
https://www.uninformativ.de/files/twtxt/2022%2D01%2D22%2D%2Dfollow%2Dendpoint.md
(This idea gets lost all the time, so I put it into a file now. 😅)
Not sure if this is what @eapl.me had in mind, obviously.
> Regarding section 4 about feed discovery: Yeah, non-HTTP transport protocols are an issue as they do not have
User-Agent headers. How exactly do you envision the discovery_url to work, though?This is from a twt of mine from January 2022:
https://www.uninformativ.de/files/twtxt/2022%2D01%2D22%2D%2Dfollow%2Dendpoint.md
(This idea gets lost all the time, so I put it into a file now. 😅)
Not sure if this is what @eapl.me had in mind, obviously.
> Regarding section 4 about feed discovery: Yeah, non-HTTP transport protocols are an issue as they do not have
User-Agent headers. How exactly do you envision the discovery_url to work, though?This is from a twt of mine from January 2022:
https://www.uninformativ.de/files/twtxt/2022%2D01%2D22%2D%2Dfollow%2Dendpoint.md
(This idea gets lost all the time, so I put it into a file now. 😅)
Not sure if this is what @eapl.me had in mind, obviously.
> Regarding section 4 about feed discovery: Yeah, non-HTTP transport protocols are an issue as they do not have
User-Agent headers. How exactly do you envision the discovery_url to work, though?This is from a twt of mine from January 2022:
https://www.uninformativ.de/files/twtxt/2022%2D01%2D22%2D%2Dfollow%2Dendpoint.md
(This idea gets lost all the time, so I put it into a file now. 😅)
Not sure if this is what @eapl.me had in mind, obviously.
How am I suppose to know whether stuff like this (_sound serious_) is for realz or not? 😅
How am I suppose to know whether stuff like this (_sound serious_) is for realz or not? 😅
Hmmm 🧐
Hmmm 🧐
Emoji not showing
Quando o gov corta na educação, não é porque não sabe gerir a sociedade.
Quando o gov corta nos programas sociais, não é porque não reconhece o seu papel social.
É agenda: este gov de direita, tal como qualquer outro, tem como base programática o desmantelamento do estado social e da coisa pública. E nisso tem sido extremamente eficaz e competente.
Uma esquerda que denuncia a suposta incompetência ou burrice das pessoas no poder dá-lhes o crédito de estarem empenhados numa sociedade melhor pra todes, e que ao falhar nisso é uma questão de incompetência.
E quando essa denúncia é feita através de comentários sarcásticos e apontamentos de "hipocrisia", servindo mais para afirmar superioridade intelectual do que realmente denunciar e avançar alternativas, é uma trágica forma de clicktivismo que continua extremamente em voga -- e a direita agradece.
tl;dr: tratar as medidas opressivas/autoritárias/securitárias de qualquer direita como fruto de burrice ou incompetência não é só um erro, é alimentar e até legitimar o seu discurso
Quando o gov corta na educação, não é porque não sabe gerir a sociedade.
Quando o gov corta nos programas sociais, não é porque não reconhece o seu papel social.
É agenda: este gov de direita, tal como qualquer outro, tem como base programática o desmantelamento do estado social e da coisa pública. E nisso tem sido extremamente eficaz e competente.
Uma esquerda que denuncia a suposta incompetência ou burrice das pessoas no poder dá-lhes o crédito de estarem empenhados numa sociedade melhor pra todes, e que ao falhar nisso é uma questão de incompetência.
E quando essa denúncia é feita através de comentários sarcásticos e apontamentos de "hipocrisia", servindo mais para afirmar superioridade intelectual do que realmente denunciar e avançar alternativas, é uma trágica forma de clicktivismo que continua extremamente em voga -- e a direita agradece.
tl;dr: tratar as medidas opressivas/autoritárias/securitárias de qualquer direita como fruto de burrice ou incompetência não é só um erro, é alimentar e até legitimar o seu discurso
/https://baldo.cat/media/photos/IMG_2562.jpeg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
Section 3: I'm a bit on the fence regarding documenting the HTTP caching headers. It's a very general HTTP thing, so there is nothing special about them for twtxt. No need for the Twtxt Specification to actually redo it. But on the other hand, a short hint could certainly help client developers and feed authors. Maybe it's thanks to my distro's Ngninx maintainer, but I did not configure anything for the
Last-Modified and ETag headers to be included in the response, the web server just already did it automatically.The more that I think about it while typing this reply, the more I think your recommendation suggestion is actually really great. It will definitely beneficial for client developers. In almost all client implementation cases I'd say one has to actually do something specifically in the code to send the
If-Modified-Since and/or If-None-Match request headers. There is no magic that will do it automatically, as one has to combine data from the last response with the new request.But I also came across feeds that serve zero response headers that make caching possible at all. So, an explicit recommendation enables feed authors to check their server setups. Yeah, let's absolutely do this! :-)
Regarding section 4 about feed discovery: Yeah, non-HTTP transport protocols are an issue as they do not have
User-Agent headers. How exactly do you envision the discovery_url to work, though? I wouldn't limit the transports to HTTP(S) in the Twtxt Specification, though. It's up to the client to decide which protocols it wants to support.Since I currently rely on buckket's
twtxt client to fetch the feeds, I can only follow http(s):// (and file://) feeds. But in tt2 I will certainly add some gopher:// and gemini:// at some point in time.Some time ago, @movq found out that some Gopher/Gemini users prefer to just get an e-mail from people following them: https://twtxt.net/twt/dikni6q So, it might not even be something to be solved as there is no problem in the first place.
Section 5 on protocol support: You're right, announcing the different transports in the
url metadata would certainly help. :-)Section 7 on emojis: Your idea of TUI/CLI avatars is really intriguing I have to say. Maybe I will pick this up in
tt2 some day. :-)
So for twt metadata the lextwt parser currently supports values in the form
[key=value]https://git.mills.io/yarnsocial/go-lextwt/src/branch/main/parser_test.go#L692-L698
So for twt metadata the lextwt parser currently supports values in the form
[key=value]https://git.mills.io/yarnsocial/go-lextwt/src/branch/main/parser_test.go#L692-L698