Tim Janik ✅ @timj@social.tchncs.de

BAD G++!

Apparently, g++-9.2.1 does *not* const-initialize a `static Class x;` with a constexpr ctor, *if* it also happens to have an uninitialized uint64_t array member. It does not generate a warning either, but surely triggers the "C++ Static Initialization Order Fiasco" at some inconvenient future point.

#cplusplus #cpp

If you use #LetsEncrypt certificates, check your hostname here to see if the cert is going to be revoked tomorrow, and you need immediate renewal: https://unboundtest.com/caaproblem.html

More details:
https://community.letsencrypt.org/t/2020-02-29-caa-rechecking-bug/114591

I just signed a petition to the European Commission:

Demand the Right to Repair your smartphone.

Sign here: https://repair.eu/smartphones/ #RightToRepair

I've written down the details of compatibly selecting modern #SIMD instruction set extensions for the #Beast builds in a blog article.
The crux is avoiding extensions that are Intel only or AMD only.

https://testbit.eu/2020/intersecting-instruction-set-extensions

Web packaging technology is torture.

The last week, I've been fighting webpack, parcel, #rollup, babel and bili, just because vue stopped supporting #browserify and I had to figure what to use as a replacement in #beast.
^^^ If that sentence sounds like it has too many web tech buzzwords, that's *exactly* the problem.

And it's only a fraction of packages I had to deal with...
Most packages have documentation, but only provide tiny puzzles of a much bigger picture that is revealed nowhere...

Yay! Power loss due to some digging work outside.

Hope the BTRFS disks in the main server survived the sudden outage.

The #dehydrated client for #letsencrypt is shell only and really rocks!

But it got way too late again, will have to continue setting up the new Testbit site tomorrow, good n8!

https://github.com/lukas2511/dehydrated

Today, I've implemented per #websocket connection cleanup of remote std::shared_ptr references in #Beast's #Jsonipc layer.

What we *really* need is per Javascript object cleanup of remote references though, but that requires FinalizationGroup support in Javascript:
https://github.com/tc39/proposal-weakrefs

That's still unfinished though, why do I always need bleeding edge features?

Time for bed I guess, maybe the edge looks less bleeding tomorrow... ;-)

Last Tuesday #Beast 0.15.0 was released.

This is most probably the last release that supports the #Gtk+ Beast UI. We have most of the bits and pieces together to move towards the new EBeast UI and a new synthesis core in the upcoming months and will get rid of a lot of legacy code along the way...

https://testbit.eu/2019/rewriting-beast
#electron #linuxaudio

Beast version 0.15.0 is released.

#Beast is an LGPLv2+ music synthesizer and composer (#DAW), for #Linux.
This release supports Jack as PCM driver and the experimental Ebeast frontened got many style updates, play position pointers and supports the Space key.

Full news:
https://beast.testbit.org/#news
#linuxaudio

Now its officieal, #CCC congress (#36c3) is in #Leipzig again:
https://events.ccc.de/2019/10/04/36c3-in-leipzig/

If you use/develop or care about #FOSS / FLOSS, take some time to answer this #EU survey. Feel free to mention #mastodon, seems they only know about FB, Birdsite and Slack.

https://ec.europa.eu/eusurvey/runner/EUFOSSA2-Survey

The Future of #Surveillance with Edward #Snowden - ORGCon 2019 keynote

https://peertube.nomagic.uk/videos/watch/536c0bc0-aecf-4784-9f21-a96fb9aa047f

I keep seeing this really odd interaction, where the second I start google-chrome or a newer #Electron version (>= 4), my currently running #Firefox processes start overloading the CPU.

Firefox becomes unresponsive for several seconds, burning CPU. Yesterday I decided to watch FF in gdb and saw that it's accessing thousands of font files , each causing a "SIGSYS, Bad system call".

Can anyone guess why FF gets SIGSYS, failing to access a world-readable file? Bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1566053

Not being satisfied with the #FontAwesome 5 looks, I've ended up creating an SVG sprite file from the #ForkAwesome project. This includes all icons from Font Awesome 4.

Here are the gory details:
https://testbit.eu/2019/fork-awesome-sprites

So I've been working on "upgrading" the Font Awesome package used by the new #Beast UI from 4.7.0 to 5.9.0.

Just — in the end I found that the icons look way more crispy and professional in the 4.7.0 version.

Is it just me, or did anyone else experience this with #fontawesome ?

Beast version 0.14.0 is released.

#Beast is an LGPLv2+ music synthesizer and composer (#DAW), for #Linux, including a #MIDI #sequencer, real-time #synthesis and support for #Audio Plugins.

The full release announcement is out now:

https://beast.testbit.org/#news
https://mail.gnome.org/archives/beast/2019-July/msg00000.html