So I went up and down a couple hills and then decided to check on the foxes. At home I noticed that the “fox” in the grass was actually the cat I came across a couple of minutes later. That’s a bit bit disappointing, but oh well. I made myself a quick stool in 21 to enjoy the scenery. https://lyse.isobeef.org/wanderung-zu-den-schurrenhoffuechsen-2021-10-17/

@movq@www.uninformativ.de (#zy6zfva) Ach herrjeh, das war mir auch überhaupt nicht klar. Sehr, sehr schade. :‘-(

@movq@www.uninformativ.de (#wkjlotq) Looking good.

@stigatle @prologic (#ujbz2ga) Me too! Looks amazing. :-) Seeing these shots makes me go for a hike today, too.

@prologic (#qdr4n4q) That’s some nice blue color! I’m very glad temperatures aren’t so hot here anymore.

@stigatle (#jfnzaca) Oh my goodness, how scenic, I absolutely love it! Cooking over the campfire is really awesome. I’m looking forward to more photos from up there. :-)

@movq@www.uninformativ.de (#wkjlotq) Exactly, @prologic told me in IRC about this the other day, so I adjusted tt. Prior to that I just generated twtxt.net/conv URLs for the subject hash link. If I feel like it tomorrow, I’ll send a MR. But please, you can go for it as well. :-)

@movq@www.uninformativ.de (#ec3zmsa) According to my knowledge, they are.

@eldersnake@yarn.andrewjvpowell.com (#2tuhezq) I have vim aliased to v and it annoys the hell out of me, whenever I have to use a system or shell, where this alias is not present.

@quark@ferengi.one (#m5qrhfa) Hahahhaaaa, what!? A password manager in the cloud? O_o

@quark@ferengi.one @fastidious @prologic (#wkjlotq) Yeah, jenny’s subject hash links seem to be off in regards to the URL.

@quark@ferengi.one (#lhi6wda) Sure. I’m currently just supporting Markdown links to include them in the URLs view so I can operate on them. Media still show the bang in front of them. But it’s good enough for now. ;-)

@adi@f.adi.onl (#lm5w55a) Never heard of vis before. Have to give it a closer look some time.

@adi@f.adi.onl (#wzpr6cq) Syntax highlighting alone is worth everything.

@adi@f.adi.onl (#wzpr6cq) So is it on most Linux distros I believe.

Quick visit to the bridge: https://lyse.isobeef.org/waldspaziergang-2021-10-15/

@movq@www.uninformativ.de @prologic @quark@ferengi.one (#3meufzq) I haven’t implemented much of the markdown syntax in tt: https://lyse.isobeef.org/tmp/newlines.png

@movq@www.uninformativ.de @prologic @quark@ferengi.one (#nhx5laa) Hahaha, classics!

@prologic (#lmg6spq) She’s probably not following anybody of us.

@prologic (#zrxztvq) It fits a bit better in my opinion.

@eldersnake@yarn.andrewjvpowell.com (#eqcx57q) Haha, yeah! So glad no server side processing is required on most of my stuff.

@prologic (#ovplvpa) But it looks rather nice.

@jlj@twt.nfld.uk @quark@ferengi.one @prologic (#ql6hxia) Ta! No, these aren’t my goats. Just came across them when I tried to walk a never walked path before to get a good view on the sunset. They’re quite young and very adorable indeed.

@movq@www.uninformativ.de (#fuu267a) Ah, yeah.

Had a nice sunset today. https://lyse.isobeef.org/waldspaziergang-2021-10-14/

@movq@www.uninformativ.de @quark@ferengi.one (#eqcx57q) I remember when I first heard about SQL injections back in the days and tried this on my self written PHP CMS’ login form. Surprisingly I successfully managed to break in. Absolutely not surprising at all in hindsight. I immediatly shut down everything – deny from all in the .htaccess.

@movq@www.uninformativ.de (#adlmy7a) Absolutely! \o/

@quark@ferengi.one (#kgpn6ya) Agreed! :-)

@movq@www.uninformativ.de (#65k6uvq) At least both our clients handle these trees really well. ;-)

Oh yeah, I just see Jupiter and Staturn next to the moon and Venus a bit further west (although it is hidden behind houses here at home). This looks really, really, really great, but my camera won’t cooperate in these light conditions. I’m totally flashed right now. Never experienced this in my life before.

@quark@ferengi.one (#2nstk3q) Yep. ;-)

@movq@www.uninformativ.de (#pe5ymoa) Ah! Didn’t look at the parsing stage. :-)

@prologic (#zrxztvq) Just curious, why not dev.yarn.social?

@quark@ferengi.one (#uhjnvba) Btw, you can just use LANG=en_US.UTF-8 jenny -f to set environment variables for a specific command.

@quark@ferengi.one (#uhjnvba) Yup, exactly. LANG is usually not defined in cronjobs (as aren’t most other environment variables neither). And then some weird fallbacks are gonna show their effects. Not sure whether LANG or other locale-related LC_* environment variables will be used in this case.

@quark@ferengi.one (#wmks6ra) I reckon you need to explicitly set it in your cronjob as well. Because cronjobs don’t inherit the same environment as one would expect.

@prologic I reckon if the “Show my followings publicly” setting in yarnd is turned off, there should not be any # following = line in the twtxt.txt. The value is empty, but in my opinion the whole metadata field should be omitted entirely.

@quark@ferengi.one (#mxago7a) The legacy charset ISO 8859-15 is used in Western Europe. It appears that some Unicode character is tried to be interpreted in this other encoding, which then fails. Sounds like something with LANG, LC_CTYPE or friends. Any chance you’ve set this to en_US.UTF-8 or something similar in your interactive shell? Try env|grep -i utf-8. Your cronjob probably hasn’t set that.

@quark@ferengi.one (#xdtgxva) Working now.

@quark@ferengi.one (#dr2jfzq) This screenshot doesn’t load for me. I’m getting HTTP 504 Gateway Timeout.

@prologic (#pe5ymoa) Maybe her -00:00 timezones throws off a parser? I think I tried this edge case when coming up with the twt hash spec, but can’t tell anymore for sure. At least I’ve written this (2020-12-13T07:45:23-00:00 → 2020-12-13T07:45:23Z) explicitly down. The thing is, I just documented Go’s behavior to make sure I don’t break anything. Maybe add a test similar to this one and see what’s happening. :-?

@movq@www.uninformativ.de @prologic (#pe5ymoa) Ok, there you go: https://git.mills.io/yarnsocial/yarn/pulls/459 However, I mixed something up. The bug I found two weeks ago in my implementation was something different regarding seconds precision. Go will always invent UTC for time.Time objects (if I’m not mistaken it’s impossible to have a timestamp without a timezone), Python does not.

(#2nstk3q) Exactly right, @movq@www.uninformativ.de! :-D Take a closer look at 17, @prologic.

@movq@www.uninformativ.de (#pe5ymoa) It might be timestamps which are missing a timezone. In this case the spec says UTC must be assumed: if twt_date.tzinfo is None: twt_date = twt_date.replace(tzinfo=datetime.timezone.utc). I had to fix this in my implementation recently, too. Let me quickly provide a fix for the Python reference implementation in the spec.

@movq@www.uninformativ.de (#yc6iika) That was quick!

@movq@www.uninformativ.de (#2nstk3q) Ta! Yeah, I reckon the driver was too careless and slit off the road into the ditch. Maybe when giving way to oncoming traffic. Not sure, though. No, not shoes, croc as in crocodile. ;-)

Where’s the croc? https://lyse.isobeef.org/waldspaziergang-2021-10-13/

@prologic (#aiug42q) Nice! My problem was that I tried to open None with the browser and not the generated URL.

@prologic (#kutrrnq) Currently I just have to come up with a free nick. Usually I just suffix the second, third and so on feed with an underscore and a shortend domain. I reckon it would make sense to render mentions in the user’s preferred nick. That of the viewing user that is. The mention of @<foo https://example.com/twtxt.txt> might for one user be shown as “@foo”, but “@foo_expl” for the other and “@[email protected]” for the next. So mentions would always be “rewritten” by what’s configured. That sounds great. I have to implement that in tt, at the moment it just renders the original nick from the mention itself.

@off_grid_living (#3miihxq) ;-)