Lol. “Lighty Encrypted” https://www.pcmag.com/news/hot-topic-breach-confirmed-millions-of-credit-cards-email-addresses-exposed
Numbers are hard. I just almost accidentally sent 33k€ to someone via bank transfer, because the banking website interpreted 334.90
as 33490,00
. 😬 This is germany, so it wants a comma, not a dot …
I love Al and his bass: https://www.youtube.com/watch?v=IwnDKcoVHmY
@prologic@twtxt.net He is a Norwegian singer who has solo work and has collaborated with Anywhen and the Exit North project.
@wbknl@twtxt.net Tell us more! Who is Thomas Feiner? 🤔
Thinking about how underrated is Thomas Feiner!
@xuu direwolf is not hard. It takes just a bit of manual reading :)
You need to figure out what it means to have “free thought”, “to reason”, “have deep understanding” and be able to apply knowledge in unfamiliar environments or scenarios. You have to figure out what it means to “dream”. You have to figure out what it means to hold “ethics”, “morals” and even “beleifs”.
@slashdot@feeds.twtxt.net When are we going to resign ourselves to a position of not achieving AGI and so-called AI in the first place? Hmmm 🧐 Fundamentally I don’t think we understand how the human brain works or what it means to be a “conscious free thinking being” – I’m not convinced we’ll figure this out to be honest.
@xuu must be extremely unlucky, as it picks a random pod in the peering list 🤣 – Oh but wait… @xuu have you updated recently? @lyse@lyse.isobeef.org did add some new feature that means you have to go to Settings -> Poderator settings and trust the peers you have there, including my pod 😅
@bender@twtxt.net True I just wanted to make sure 👍
@prologic@twtxt.net using Yarn he isn’t supposed to follow it, it should show as context, no?
They are however pretty good at auto-complete though. If you wire up Continue.dev with VSCode and a local Ollama powered codeastral model, it’s pretty decent. Or if you use the open source friendly Codeium.
@eldersnake@we.loveprivacy.club With enough data and enough computing power you can simulate anything right or create grand illusions that appear to real they’re hard to tell 😅 – But yes, at the end of the day LLM(s) today are just large probabilistic models, stochastic parrots.
@xuu You don’t follow the Slashdot feed? 🤔
@prologic@twtxt.net I never got the root for this
@wbknl@twtxt.net I have thought of getting one. I wish there were easier tools for it than direwolf
🤑😜
@bender@twtxt.net Linux and Android. I would never iOS my friend.
@bender@twtxt.net Ull Twt to find the references later. But my memory is quite good 🤣
I’ve been testing our new APRS digipeater, that allows us to report our geographic position via radio.
@prologic@twtxt.net sorry, tried looking for the points you mentioned, but couldn’t find them. Got a link?
@bender@twtxt.net Fair point, could be. I probably have to implement it first or create some kind of a mockup to spare me the effort of some feature that I rip out again. :-)
@xuu Yep!
@movq@www.uninformativ.de Riiiight, I now remember reading that a long time ago. :-)
@bender@twtxt.net I now read the German Wikipedia article on fog. These are some really beautiful pictures:
- 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
To @anth@a.9srv.net’s points, I think this should be written as “Client recommendations” and “Serve recommendations”. Separate from the “Twtxt format” spec.
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 thediscovery_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@eapl.me had in mind, obviously.
@bender@twtxt.net Agreed 👍
@lyse@lyse.isobeef.org agree on the HTTP stuff. I mean we could mention that for optimization see RFC yadda yadda should be followed for caching. but not have it part of the spec proper.
@prologic@twtxt.net lies, and scams aside, there is plenty of need in the world. Yet, you can’t help everyone. Best way to do it is to donate to a worthy cause, and ignore one offs.
@bender@twtxt.net I’ve worked with this guy before. Paid him to do some freelance work. Not very good IMO. So haven’t hired him ever again. But he keeps saying hi every now and then on Signal. And then every few months or so asking stuff like this ☝️ – Last time it was money for private school fees for his child.
How am I suppose to know whether stuff like this (sound serious) is for realz or not? 😅
@prologic@twtxt.net “here, have 2 rupees.”
I need money for my mother’s heart surgery, there is a shortfall of about 2 million rupiah from a total of 40 million, can you help me with any amount?
Hmmm 🧐
😜
😜😜😜 well, now I can. This is beyond weird.
@xuu that’s on iOS? I can’t (running 18.1).
First one on the third row, for example. There are more, though.
@prologic@twtxt.net how could I show you what I can’t type? 😂 Let’s see, a second.
@bender@twtxt.net such as?
I have noticed that Yarn (here) will not take some emoji. At least, will not take some under iOS.
@lyse@lyse.isobeef.org precisely. The fog itself doesn’t smell. It simply carries the smell of its surroundings. Find what those surroundings are, and the credit will go to the right thing. 😊
Making some amateur radio experiments!
@lyse@lyse.isobeef.org I think it would make the interface look too busy, I would pass on that one.
@sorenpeter@darch.dk Section 7 on emojis: Exactly that, it’s an avatar for text interfaces. The metadata name needs tweaking, but that’s a cool idea. If I implemented this in my client, I’d make the text avatar overridable by the user, though. Otherwise I’d probably only see boxes for everbody in my terminal. :-D
Thank you, @eapl.me@eapl.me! No need to apologize in the introduction, all good. :-)
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@www.uninformativ.de 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. :-)