Carina Nebula
Colors over colors in the sky!
Colorful clouds in the sunset, it looks like the cloud god was a bit lazy and just used copy & paste
To be fair, when I started all the hiking a few years back, my endurance was really low, too. I couldn't have done that back then in this time. I went out for half an hour to an hour, then I was whacked. Nothing comes from nothing.
But we had the paths mostly for us, there were only very few other people around. So that was cool.
It was my first time on that particular terrain. We went through some beautiful and quaint forest paths with scenic views. I forgot to put my SD card back into my camera, so no photos until my mate will send me his.
Now my feet a cooling off in a bucket of cold water. Superb.
#<hash url>), the simplified version without the URL (#hash) is enough.The hash tag extension specification is kind of missing the same. However, I'm not sure if that short form is considered supported in general (as opposed to be a special case for subjects only) by the majority of the twtxt/yarn community.
Now the question arises, in order to keep things simple, should we even only allow the simplified twt hash tag for subjects and forbid the long version? This would also save quite a bit of space. The URL is probably not shown anyways in most clients. And if so, clients might rewrite URLs to their own instances. On the other hand, there's technically nothing wrong with the long version in current parser implementations. And deprecating stuff without very good reason isn't cool.
About 15-20 minutes the rain stopped and the thunder and lighning rolled past. So we continued our journey and I finally filled my two one liter bottles successfully. Every now and then it drizzled a little bit through the forest. We reached our homes and a couple minutes later rain hit again. Thunder and lighning went crazy. The sky lit up every few seconds and this continued through half of the night.
Right after I hung up to meet my mate, another mate called and reported a few villages north of us they experienced hail sized a bit under golf balls. But he luckily managed to get the car in the underground carpark in time.
Today, it rained the whole morning. This was great since the temperatures stayed below 20°C, so my walk was a real joy. It's going to get close to 30°C tomorrow, though, gnarf, örks, bwäh. :-(
Sunset, once again
* into the trash? ]:-> And why the heck does it take time for new rules to take effect? Not confidence-inspiring at all.
Other than that I don't have a good strategy either. Since I don't use 2FA and have some hard passwords memorized, I might be able to recover some data/accounts, but definitely not all. Have to come up with a suitable battle plan in the future.
Today, I decided to take some photos again on my way in the woods. Couldn't be bothered the last two days. It was too humid and I leaked like crazy. Surprisingly, I went outside, though.
Sunset
Today, I decided to take some photos again on my way in the woods. Couldn't be bothered the last two days. It was too humid and I leaked like crazy. Surprisingly, I went outside, though.
Sunset
Sunset
My workday didn't went so smoothly for me. When implementing tests for a hotfix I refactored some test helpers and then found out that a mock structure was wrongly implemented for ages. After fixing it, three tests failed. Two could be solved by fixing the test setups. But the third test failure turned out to be even another severe bug in one of our production code functions. Good old nil pointer dereference panics. Somebody thought it's a good idea to rewrite
(nil, ErrNotFound) of type (*Data, error) to (nil, nil). After handling the returned error in the caller (in this case, there was no error anymore) nobody had the possible nil pointer on their radar. Bad design. To be reworked in the future after bringing the hotfix on its way.I then also found another inconsistency of our storage implementations. When removing something that does not exist, some return
nil, some ErrNotFound instead. Oh dear. This will cause some aftermath, I tell you.At least all of those side quests didn't happen in the wild yet.
First encountered slow worm heading into safetyThe tadpole pond was nearly empty. When approaching it, hundreds of not even fingernail sized frogs or toads were jumping towards me. I knew, that there are larger fish in the pond, but I've only heard them so far, never seen them. Until today. At least five large individuals about 30-40 centimeters in length. One might have been even half a meter long.
Banning dragonflies on film is nearly impossible. 11 is the "best" result, not only can you see its shadow, but also its head at the very top. When going home I saw six deer in total at the woodland margins. Spending two hours at the pond was absolutely worth it.
Not too shabby sunset
DATE only, but in fact a complete timestamp including time and timezone was written instead (DTSTART;VALUE=DATE:20230106T000000Z rather than DTSTART;VALUE=DATE:20230106). This parser didn't like that. To my defense, the validator did not report anything and approved of my ical file, though.
1. I'm sure
go fmt would add a space after the comment marker //.2. Go doc strings are supposed to start with the name of the variable etc (I'm not a fan of this, either).
3. Sometimes
log.SetPrefix(…) ends with a space, sometimes not.4. Some messages start capital, some don't.
5. Typo:
occurred with double r.6. On lots of errors no appropriate status code is set.
7. Some
err can be scoped in the if like that: if err := foo(); err != nil { … }8. The
<title>s could be improved.9. I have no idea about redis, but
rclient.Set("user:"+username, …) looks suspicious to me and reminds me of SQL injections.10.
o
cookie, err := r.Cookie("session_token")
if err != nil {
if err == http.ErrNoCookie { … return }
}
doesn't look complete. Also handle other errors? Or simplify without nil check.
Deer in the distance at the woodland margin looking at you!The sunset started really lame but quickly turned into a pretty colorful spectacle. At least three quarter of the photos turned out utterly useless, since the auto-focus totally fucked up again. That's almost never the case with the old camera (unless lighting sucks). Observed this quite a lot with this one, even happens every now and then in superb lighing conditions. :-(
Not a crash, hot-air balloon gets deflated after landingIt's crazy how loud these mowers can be. The noises resounded from 1.5 km away to the summit like they were only a few meters away.
As it turns out, the tree in question covered in ivy from a few weeks or even months back is a cherry (34 & 35).