Turns out it's actually a #gcc 8 regression, the one thing I usually expect to be least likely:
So with #Google closing down G+ and the new Birdsite terms (that I've never accepted so I can't login to my account anymore), I've started asking my remaining contacts to consider moving to #Mastodon.
Interestingly enough, the non-conglomerate, non-monopoly, but community powered and decentralized technologies have started to look a lot more robust, attractive and reliable than the rest in recent years.
It must be 2 or 3 weeks now that I've been working on
a) static code checks for Beast;
b) making libbse fully relocatable to build an AppImage.
Travis-ci has finally completed the newest builds which produces a single .x64 executable for Beast, reports from cppcheck, scan-build and clang-tidy.
It all gets built from a single Dockerfile and is automatically uploaded to a bintray file area:
Today's lessons learned from debugging an evasive CI segfault:
- Docker run needs --cap-add=SYS_PTRACE to support gdb.
- Docker stack size is limited to 8MB by default.
- A clang++ compiled program may need vastly more stack space than a g++ compiled one.
- A clang++ -O1 compiled program using 6MB stack size may need around 12MB if compiled with -O2.
When I got up this morning, I would have expected none of these points to be true.
docker pull nextcloud
docker run -p 8080:80 nextcloud
Also the Android "nextcloud" app is easily installed and can be pointed to the dockerized nextcloud instance if you know what the hostname or IP of "localhost" is in the local WLAN.
Just released Beast-0.12.0.
We fixed a couple regressions since the last beta, got rid of some intricate dependencies since the last stable release and we are developing a new #electronjs based UI. This is the first release that features a preview of the new UI.
@cblte Dein Profil sagt: "- randon ramblings - " -- "randon" oder "random" ? ;-)
Which means: I had to *actually* *implement* the email -> blog-comment rendering that I had been planning for ;-)
octodon.social experiencing problems? I fail to follow you or anyone else on octodon.social today.
Mastodon gives the "We're sorry, but something went wrong on our end." page. Care to ping your admin?
#Gitlab going dark in Crimea, Cuba, Iran, North Korea, Sudan and Syria after August 11th:
Hey @gargron, reading @kev's writeup got me thinking how much I'd like to peek at the local timelines of other instances.
I.e. I wish I'd have an easy way to check out the people & timeline on fostodon.org.
With my account I can easily browse @social.tchncs.de and the timeline of e.g. qoto.org can be found on their website.
But for fostodon.org, it seems the only way I have is to create an account.
Would if be possible to create a column / search to browse a particular instance's timeline?
A couple of people from various instances have mentioned that #Mastodon is confusing at first. So I decided to write a comprehensive guide on how to get started with Mastodon.
Hopefully this helps new users to Mastodon. Please do Boost if you feel it could be useful to others.
And there's a cool new security paper!
basically all Unicode strings need to be typechecked at runtime now I guess
DSP + UI developer on the Beast DAW, Free Software author + advocate, contributor to ALSA/GNOME/procps/LibreOffice/Mediawiki.
One of the first Mastodon instances, there is no specific topic we're into, just enjoy your time!