Show more

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.

Just figured it is really easy to setup and test a instance with :

docker pull nextcloud
docker run -p 8080:80 nextcloud
firefox http://localhost:8080/

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.

More details:

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 based UI. This is the first release that features a preview of the new UI.

Hm, my travis-ci jobs seem to fail due to network errors, not code changes...

It'd be great if you could switch instances but take all your toots, follows and followers with you. I'd more inclined to move to another instance to lessen the server load on this main one if I didn't have to start over.

@cblte Dein Profil sagt: "- randon ramblings - " -- "randon" oder "random" ? ;-)

Mit diesem Bild will ich euch dann mal in die Nacht lassen. Bis morgen!

Today I got my first article via , since the static blog went live (it features email-links for comments).

Which means: I had to *actually* *implement* the email -> blog-comment rendering that I had been planning for ;-)

@kensanata is experiencing problems? I fail to follow you or anyone else on today.

Mastodon gives the "We're sorry, but something went wrong on our end." page. Care to ping your admin?

going dark in Crimea, Cuba, Iran, North Korea, Sudan and Syria after August 11th:

After a good sleep, the blog post about the new release is out as well:

Waiting for the regression tickets to come in - or not ;-)

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

With my account I can easily browse and the timeline of e.g. can be found on their website.

But for, 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.

async(); await();
async(); await();
async(); await();
async(); await();
In the System()
// the mighty System()
The process.sleep()s tonight~

Just uploaded a new release of the , the first version that ships a pre-alpha Electronjs based user interface:

And there's a cool new security paper!

basically all Unicode strings need to be typechecked at runtime now I guess

My new statically generated Testbit just went online. There's not much content there yet, I'll migrate posts bit by bit in the following days.

We just took the group photo at Native Space, but I'm not sure I'm on it. It's just way too many people this year.
I'll post a link once it's up.

Arrived in Berlin, -base for . Looking forward to Stefan's talk tomorrow morning at 10:30 about SpectMorph:

Show more

One of the first Mastodon instances, there is no specific topic we're into, just enjoy your time!