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.

#Goophy #gopher #GopherProtocol #cprogramming #c #programming #devlog #selfhosted #gopherhole #NetBSD

“There are many good things in the world of #C and #UNIX, but #time handling is not one of them.”

The surprising struggle to get a UNIX Epoch time from a UTC string in C or C++ by @bert_hubert

https://berthub.eu/articles/posts/how-to-get-a-unix-epoch-from-a-utc-date-time-string/

C++ library update in -current https://www.undeadly.org/cgi?action=article;sid=20250822171538 #openbsd #cplusplus #c++ #programming #development #library #clang #freesoftware #libresoftware

#Goophy DevLog 🧵
---------------------------------
First steps of a pet project of mine. A Gopher server in C called Goophy. I'm making it for educational purposes and to use it myself in the (near?) future.

The test client is elpher a gopher / gemini client for emacs.

#gopher #GopherProtocol #cprogramming #c #elpher #SmallWeb

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 😅

#gopher #GopherProtocol #cprogramming #c #SmallWeb #selfhosted

You know you're not making any progress if you don't get a Segmentation Fault once in a while 😅 😂

#c #programming #cprogramming

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 😉

#c #programming #cprogramming #valgrind

As promised, here we go: #Goophy in action. As you can see it's approaching an usable status.

Next steps: refactor more code, add a logging system and start my own gopherhole to test it in a real case scenario.

#gopher #GopherProtocol #cprogramming #c #Internet #selfhosted

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... 🤓 😆

#Goophy #gopher #GopherProtocol #cprogramming #c #programming #devlog #selfhosted

First version of the logging system almost finished. I have to fix a few formatting things but I have a working logfile. Almost all of the debug printf have disappeared 😉

#Goophy #gopher #GopherProtocol #cprogramming #c #programming #devlog #selfhosted

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.

#Goophy #gopher #GopherProtocol #cprogramming #c #programming #devlog #selfhosted

Alt...

Screenshot of the output of Goophy's log file. It shows info messages, warning messages and error messages for different requests.

Today I'm working on a config file system for the server. We will see how it goes 🤓

#Goophy #gopher #GopherProtocol #cprogramming #c #programming #devlog

Mission accomplished!
Config file works as expected and with this I'm ready for a first private beta 🥳

Next step: installing NetBSD on my Raspberry Pi 2 for putting this online and see what happens 😉

#Goophy #gopher #GopherProtocol #cprogramming #c #programming #devlog #selfhosted #NetBSD #RaspberryPi

#introduction ― I decided to create an alt account here to allow me
to connect more easily with SDF community.

My primary focus will be on tech-related things I like:
#pkgsrc on #netbsd #illumos and #slackware
#unix #sdf #gopher #smolnet #usenet #dos #c #lisp
#selfhosting #homeserver #permacomputing #lowtech
#hamradio #progrock #progmetal #ambient #postrock
#90s #scifi #cyberpunk #novels #seinen #manga

Message in a bottle time again #GetFediHired (not a peep from anyone yet).

Growing desperate in search for (remote) software developer work in the #Ottawa #Montreal areas. #C C# #Erlang #Java #NodeJS #Shell #SQL #BSD #Linux #English #French and more. Very versatile, adaptable, experienced.

http://www.snert.com/resume/

Hey! If its remote, its possible to work world wide too!

I am so stuck in making this C/OpenBSD based website.

It's funny how much work it is to do things that are like trivial in
Flask/PHP/Django etc.

But I don't mind at all. I'm pretty confident I could run this on
any low level hardware. Like I keep wanting a 486 or pentium 1
and it would probably run just fine. I guess the https might be
the real expensive part :)

Anywho, I added email sending:
https://alive.d34d.net/emailtest/

Again you won't see anything, it sends it to me.
I am afraid to put an email form on a public page that did
anything more than email me.

If you notice I put ?r=12312312-123123 url params on all of
links that would have dynamic content. That is because I am using
#links2 to an it will otherwise cache the pages.

#OpenBSD #C #links2

Just to give you an idea of how much software GCC 14's default of -Werror=implicit-function-declaration breaks, here are two pkgsrc bulk build results:

GCC 13.3.0: 24835/28450
GCC 14.3.0: 2589/28450

https://reports.pkgci.org/SmartOS/upstream/trunk/20250630.2248/meta/report.html

https://reports.pkgci.org/SmartOS/upstream/trunk/20250701.2248/meta/report.html

I also had to fix up a bunch of things before the build would even start.

This could take a while. And then the fun starts all over again with GCC 15's changes...

#pkgsrc #c

I am building gcc-15.1.0 on my iMac G4 (Tiger) machine. It is on stage2, which is a good sign.

It will include C, C++, Fortran, Modula-2, Objective C, and Objective C++ compilers.

It will depend on my new PowerPC Mac OS X modernization library, libpcc: https://github.com/ibara/libppc

I'll write a blog post about how to use it once it is all compiled; my goal is to produce a turnkey solution that just works(TM), including assembler, linker, and other utilities, as recent as possible for PowerPC.

And libppc can be instantly extendable to incorporate more C11 and later features. Hopefully others in the retro Mac community are interested in building that up with me.

My ultimate goal is to build some flavor of WebKit some day and have a modern web experience (even if slow, and possibly using X11). But in the meantime we will probably build a lot of excellent modern software to keep these machines going.

#gcc #compiler #compilers #c #unix #linux #macos #macosx #osx #apple #powerpc #retro #retrocomputing #bsd #mac #macintosh

@iris_meredith to write the same piece of functionality in #C as in #Lisp, you'll use exactly the same number of bracket ({[]}) characters; plus in C you will additionally have to use many other punctuation characters that you wouldn't have to use in Lisp. You will also, typically, have to write many more lines of actual code.

But of course Lisp syntax is much more complex.

I'd boost it (the blog is federated - @ltning), but @writefreely doesn't render nicely for some reason.
#Fail #DOS #C #Retrocomputing

(Also @obsoletemediauk - got any new updates lately? :)