@firstname.lastname@example.org Very nice! I just didn’t want to trade that enormous heat, no way. I’m happy with the 2-8°C here. Nobody in close proximity is awesome. And you have one of these iconic iconog foldup caravans. The tall tent is the outhouse I reckon? Do you have a solar panel on the car’s roof? Enjoy!
I found a Foosball with a digital scoreboard.
In college I wanted to make one of these with electronics and PICs, but it was a bit expensive as a student, so never I finished that.
Later I made one with a tablet and an online ranking system.
I wanted to build one for table tennis, inspired by one I say online which recognizes a RFID chip in your racket 🏓
@email@example.com hehe, agreed!
At least we only have an UV index of 5 😜
I signed the open letter/
@firstname.lastname@example.org hehe, I’m just envying your weather… 🥶And having friends in the other half of the world living the opposite season, it’s so weird!
@email@example.com summer and the morning? it’s winter and dark night here!
@firstname.lastname@example.org I haven’t touched the goroutines yet (I played with these like 10 years ago), but I haven’t found a case where I need these.
About the modules, those were very non-intuitive to me, coming from Python, C#, and JS. I think the official documentation from Go is not clear enough and has no simple examples…
After a few searches, I reached Stack Overflow and blogs with tips for Modules and subdirectories. Now, I can replicate an MVC model with templates.
This project helped a lot: https://github.com/J7mbo/go-subdirectories-with-modules
@email@example.com Well, those are for a private university in México, so won’t be publicly available.
And they told me that the format is gonna be different from what I recorded previously, so next week I’ll have to make new shots. 😅
In fact, I don’t have videos in English, so I guess I’ll have to practice recording a few 🤔
Good Morning 😴
I’ve started playing with Go today, just understood the basics and still a bit confused about the module and goroutine parts.
I’ll try to make something interesting soon.
I finally got my stats script into a usable state.
I’ve just signed the @fsfe open letter:
The universal right to install any software on any device
You can also do it here:
@firstname.lastname@example.org Oh, I see. It’s been a while that I touched these bible paper thin phone books. But now I remember. Maybe you have to build multi layer planes. And hope that they don’t separate mid air.
@email@example.com Cool, cool! Definitly keep on going, mate.
@firstname.lastname@example.org Maybe I’m a bot. Who knows?
Ah git-bug! Ive chatted with the creator when he was working on the graphql parts. Its working with git objects directly sorta like how git-repo does code reviews. Its a pretty neat idea for storing data along side the branches. I believe they don’t add a disconnected branch to avoid data getting corrupted by merging branches or something like that.
Twitter is 4channing fast. Letting the worst of the previously-banned far right back on, suspending or permanently banning activists and journalists.
Huh, just noticed that my client currently holds 51839 twts (28 MB). Way more than I expected. 😅 (I’m not following any bots.)
@email@example.com That’s right. 🤔 Those sheets are not exactly A4. And they’re super thin, very little stability – that’s the main problem, I guess.
Playing upright bass is so much fun. 😊 I struggled a lot in the beginning and that shit is still super hard, but it’s getting better every day. 🥳 Been at it for about half a year now …
(Backing track is https://www.youtube.com/watch?v=Tn5P88OOJkc with the bass cut out.)
@firstname.lastname@example.org I’d say your wings are too small. The body is too high in comparison. Using an A4 paper I usually go with around 2-3 cm high bodies, then the wing is about 7-8 cm wide at the largest section at the tail.
@email@example.com Oh, you mean the license plate! Completely forgot about that one. Yeah, I had some data protection fun this time. Just blurring stranger’s number plates is getting boring. :-)
@firstname.lastname@example.org No edits apart from rotating a bunch of photos by 1-2° to fix my crooked camera angle. @email@example.com Thanks! We were lucky that the sun came out and five trains went by in just three minutes. Both unpredictable forces of nature.
@firstname.lastname@example.org Right, hence a disconnected branch that you’d never interact with. 🤔 But really, no idea, I’ll have to take a closer look at the project first. 👌
@email@example.com very nice!
@firstname.lastname@example.org 20.jpg and the train pics are 👌!
@email@example.com I think I like that choice? Not sure yet since I haven’t tried using it for anything real. I do like the fact that it doesn’t introduce a bunch of weird files to your repository that you then have to worry about managing.
@firstname.lastname@example.org it’s hilarious that it’s called “semantic” web when nobody knows what it really means (“semantic” being the word for “meaning”)
Interesting indeed. I’m curious why they didn’t chose a dedicated branch with regular files instead of working with Git objects directly. 🤔 Might be an interesting project for a gloomy weekend.
@email@example.com Sneaky edit. 😏 I had to look up if it could be real. 😅
I was about to throw away some “Gelbe Seiten”, then I remembered this twt. It kind of … works … a bit … nah, it doesn’t.
@firstname.lastname@example.org @email@example.com @firstname.lastname@example.org Some mates and I also started twice to build our own git based bugtracker several years ago. At the time there was nothing out there that really worked great. We failed to complete ours, because we wanted to have too many features and flexibility for small and large projects. So we ended up in the same useless state as all the other ones. I have to check this one out.
Winter is here ❄
It was a cold and misty November day. Just like November is supposed to be. It rained in the forest a little bit, but on the way back the sun came out for a short time. And then it turned very cloudy and dull for the rest of the day. Mixed with rain time after time. Looking outside now, it’s very dark and foggy again. Closing the shutters at 16:30.
remote: Updating references: 100% (1/1) To $REPO remote: Updating references: 100% (1/1) 19cf0dc6b52363cf5b8032755b16a5 -> refs/identities/af97ed38e619cf0dc6b52363cf5b8032755b16a5remote: Updating references: 100% (1/1) To $REPO * [new reference] refs/bugs/00fd29b9f50294a64ad72c039a7340b5863d7907 -> refs/bugs/00fd29b9f50294a64ad72c039a7340b5863d7907
So it puts stuff in
$DIR/.git/refs. It creates a cache directory too.
I have to say, it’s surprisingly full-featured given that it’s pre 1.0 and the main author warns that there be dragons here (though not so surprising given that there are over 2,000 commits!). You can do the entire create/label/comment on/push/pull/clear bug workflow entirely on the CLI with
git subcommands, which is how I’d probably use it were I to adopt this. The webui looks remarkably like github/gitea/etc if you’re into that.