I just ran across the blog of André Staltz, Scuttlebutt author and creator of manyver.se/. He's got lots of thoughtful and interesting articles, excerpt:

> And [...] an internet experience that violates my privacy, profits behind my back, silences my voice, steals my attention for ads, and forces me to read and accept regulation banners, [is not] a good enough sales pitch.

staltz.com/eu-copyrights-and-t

Wow, a declarative cross-browser crash, purely in .

(Link goes to explanation, not the payload)

cras.sh/

Ecuador and US plot to have Assange extradited for show trial.

truthdig.com/articles/crucifyi

---

USA und Ecuador planen Assange zur Aufgabe zu zwingen um Schauprozess zu initiieren.

Deutsche Übersetzung: nachdenkseiten.de/?p=47287

Have been chasing a build bug on 28 for several days now.

Turns out it's actually a 8 regression, the one thing I usually expect to be least likely:

gcc.gnu.org/bugzilla/show_bug.

So with 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 .

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.

plus.google.com/+JensGraikowsk

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:

bintray.com/beast-team/nightly

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:
github.com/nextcloud/docker

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.

beast.testbit.org/release-note

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 ;-)

testbit.eu/2013/cpp11-signal-s

@kensanata is
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?

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

about.gitlab.com/2018/07/19/gc

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

testbit.eu/2018/beast-0-12-0-b

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

kevq.uk/how-does-mastodon-work

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

Show more
Mastodon

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