The 20th BSDCan will include tutorials on PF, running your own email, TLS, BGP, and NSH, as well as two days of talks on everything from systems administration, networking, and programming.
When u think u get it, u don't get shit. Good thing I never thought I made it! I'm an eternal jr lookin' to learn somethin' new. Yesterday, I was struggling to run a simple Makefile and nothin' worked. What was the problem?
The platform LOL... on #FreeBSD only #BSD make or #GNU make work. Especially bmake (I'm practicing C to contribute to some projects that always caught my eye). I'm crap!!!
Oh what joy. Seems like #Mail.app on #iOS no longer allows sending uncompressed 2.2 MB JPEGs.
My #SMTP server advertises 250-SIZE 157286400 (accepts messages up to 150 MB) and base64-encoded 2.2 MB binary would weigh roughly ~2.86 MB.
What non-3rd party options are there to transfer pics from #iPhone to #FreeBSD laptop nowadays?
This is interesting: I've installed FreeBSD 14.0-RELEASE on that laptop. However, every time I try to check the system's status with 'top', it crashes. I suspected this was due to the absence of a battery, so I tested this theory with the command sysctl hw.acpi.battery and - boom - experienced the same crash.
It seems that FreeBSD does not function well on a laptop without a battery.
Can anyone suggest a workaround or solution? I'd like to avoid re-inserting the 9-years-old worn-out battery.
(The CMake-related issues include other #FreeBSD ports which want to switch the build to CMake, so there's really only 2 CMake-issues, one of which involves fiddling with OpenCV build flags that I don't understand)
🔹Add a "single instance" mode (configurable)
🔹Add a "tray icon" (configurable behavior)
🔹Add an "About" dialog
🔹Enforce using Qt's "xcb" platform
🔹Fix detaching on startup, add a flag (-d) to prevent it
Pretty usable as it is I hope ... although one could of course improve a lot (but have you heard of the 80-20-rule?) 🫣
Screenshot from #KDE this time, no particular reason, I'm still running #fvwm here 😎
This brings a lot of improvements and fixes, the most relevant being immediate persistence of settings and watching the settings file for external changes. To make this feasible also for restoring the history, a lot of work went into generating static emoji data that can be used efficiently (e.g. containing a hash table to find an emoji quickly).
BTW, this even works on #NFS, so if you have your home shared and you're running qXmoji on two machines as the same user, the history will auto-update in both instances 🥳