mastodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance, open to everyone, but mainly English and French speaking.

Administered by:

Server stats:

739
active users

#cprogramming

6 posts5 participants2 posts today
Continued thread

After almost 2 days online I can say that Goophy is doing well. I already have my gopherhole with more content online and I made it bilingual English / Spanish but I don't plan to keep 1-1 translations of everything. We will see.

Some screenshots below for showing it up & running. The client used is Lagrange Gemini / Gopher client.

You can visit my gopherhole at gopher://lucio.albenga.es

Continued thread

A new gopher hole and gopher server are born!! 🎉

Finally the first private beta of Goophy is up and running on the Raspberry Pi with NetBSD. You can check it out with your favorite gopher client at:
gopher://lucio.albenga.es

I promise I'll put more content in the following days, but right now I'm excited to have it online 😅 Let me know if you find any bugs.

👉 Neuer Blog: „time_t Cast Away: Bits über Bord und der Y2K38 Bug ist zurück“

Die Umstellung auf 64-Bit-time_t gilt als Lösung für das Year 2038 Problem. Doch Direct Casts machen den Fix schnell unwirksam – und schicken uns zurück ins Jahr 1901.

Auf das Wortspiel bin ich ein bisschen stolz ☺️

🔗 y2k38.ch/time-t-cast-y2k38-bug/

Retro-Poster einer tropischen Insel mit Palmen, im Vordergrund ein Volleyball mit der Aufschrift „Y2K38“ im Sand. Darüber der Titel „Cast Away time_t“. Beschriftung (Caption):
Y2k38 - Das Jahr 2038 Problem · time_t Cast Away: Y2K38 Bug durch Bits über BordDirect time_t Casts werfen Bits über Bord – und holen den Y2K38 Bug zurück. Warum 64-Bit-time_t allein die Epochalypse nicht verhindert.

After writing so much software in C# and TypeScript during the past years, I felt a bit burned out.

- Decided I need a little "OOP detox"
- Dived a little into Rust for a while
- Result: great language, but did not fully click in some aspects

So now I am doing the only sensible thing:

Getting back into C. 😄

#C#Clang#oopDetox
Continued thread

Finally I have a working logging system. Yesterday I had almost completed a first version but today I thought, wouldn’t it be better if…? And I jumped at it 😅

There is room for improvement but I'm quite happy with it right now. I hope to have my private beta ready this week.

Continued thread

Fixed my very first "buffer underflow" since the 90s 😅, refactored and improved code readability, doc comments, etc. I'm quite happy with the current status.

Next step: adding the logging system and removing all the debugging prints. Maybe I'll continue later, who knows... 🤓 😆

Continued thread

You also know you're making progress when valgrind output looks like this:

==32514== All heap blocks were freed -- no leaks are possible
==32514==
==32514== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

Stay tuned, later in the day I'll show you current project status 😉

Continued thread

More progress done. Some code refactor here and there, some security things like avoiding access to not authorized files and paths, gophermaps already supported... not bad at all 🤓

Funny story of the day: I was testing the program and I was excited because everything worked fine. Suddenly I realized a thing was working but it shouldn't. Why was it working? 🤔 Because the data I was using didn't cover that specific use case yet 😅