Show more

It took a while but we finally have an Internet connection that makes me smile :)

(That’s over 5Ghz WiFi with the freakin’ amazing Asus AC88U router.)

The beauty of Mastodon is not only that it is free and open but that it’s federated. You can fork it without losing access to the network or your social graph. There’s no reason a hundred forks couldn’t exist.

Also, when did forking become an insult? As far as I’m concerned, it’s the biggest compliment you can pay a project. And if you fork and stay federated, you’re actually helping to strengthen the fediverse!

What you can’t do is force people to build what you want out of entitlement.

Anyway, the thing about something like this is that no permission is required. Anyone can start experimenting with adding semantics to the content of messages and any client can start adopting representations of those semantics.

So the idea’s out there. Have fun. Make lovely things :)

I’d suggested a similar thing for Twitter ages ago when they were thinking of coming out with their “annotations” feature to add extensible metadata to tweets. Back then I called it Twitterformats. Maybe what we need are Mastodonformats.

The beauty of such an approach is you don’t need to keep bloating the core protocols. You can add protocols in a decentralised manner. Clients, including the official one, can pave the cow paths & start supporting the most popular by default/others via plugins.

I hope ActivityPub will be kept as simple as possible (think TCP/IP for federation) and semantic extensions will occur in message space.

Markdown is one extension. (If enough people start using it, clients can pave the cow paths.)

Another might be editable toots.

Imagine a toot:

/update replace "hint, hint" with "hint, hint, hint"

A human reading that can understand it. If a client supports it, they can actually update the toot.

Editable toots, anyone?

CC @Gargron

PS. Don’t ask me why I’m using Markdown in my toot. Ask, rather, why your Mastodon client of choice does not support it… *hint, hint* ;)

Just got bitten by the no-semicolon before self-invoking function issue with JavaScript Standard Style:

// All good
;(async function () {})()

// The sky will fall
(async function () {})()

The second will give you the wonderfully cryptic error:

TypeError: obj.method() is not a function. (In 'obj.method() (function () {})', 'obj.method() ' is undefined)

Maybe JavaScript Standard Style should enforce ;(function(){})()


@Riley @Chocobozzz

It should be easy to add a point in the FAQ section

I think the main issue is that we want to reach non-french speaking people, but we don't have a good network outside France (where we're well known and, considered as one of the biggest Free Software non-profit).

I think that excepted @aral and the message of @valvin we didn't had a lot of boosts/retweets/messages directed to non french-speaking people.

Developers, do not embed Google’s products on your sites & compromise the privacy of your visitors.

#CleanUpTheWeb & strip your site of tracking devices by Google, Facebook, etc. to make the web safer. Yes, that includes Google Fonts loaded from Google’s servers.



#FuckOffGoogle @aral

In #Ubuntu 18.04, I can't opt out of the system info upload without a mouse. The tab doesn't go to the selection.

Please boost or tell someone you know in Ubuntu Accessibility. This is so wrong.

In the gradient descent of human progress, religions are local minima.

Decided to go with Dexie and to handle any issue there might be with IndexedDBShim on the Node side of things.

I’m just not smart enough to navigate the minefield of undocumented and semi-abandoned projects that is the Node/LevelDB/übergeek playgrounds right now. Worst case scenario, I will have to bite the bullet and write a LevelDB adapter for Dexie at some point.

A good first step would be to get the Dexie tests running in Node with IndexedDBShim to see where we stand… :)

‘Facebook, Google face first GDPR complaints over ‘forced consent’’

“Schrems argues that the companies are using a strategy of “forced consent” to continue processing the individuals’ personal data — when in fact the law requires that users be given a free choice unless a consent is strictly necessary for provision of the service.”

Also on our radar:

Right, so I’ve narrowed down the isomorphic JavaScript database options for Indie Site to three candidates:

1. Dexie.js with IndexedDBShim in Node
2. nanoSQL (uses LevelDB adapter in Node)
3. LevelUp (with level.js in browser and leveldown in Node)

Not considering: PouchDB (will be implementing my own replication/CRDT)

Any other possibilities I’m missing? Basically, although a “web site”, the Web client and server will act very much like a node in a p2p network.

Bug with auto-incrementing primary keys under Node with the LevelDB adapter fixed in nanoSQL (thanks Scott).

Very much looking forward to taking part in Waag’s Public Stack Summit in June.

“We’ll set our sails for open water to fix the broken internet. An unconference with over 50 public stack pioneers, during We Make The City festival in Amsterdam

With recent attention on the dark side of surveillance capitalism and data extractivism it has become inevitable to invest in open, fair and inclusive internet … the internet needs to be fixed.”

I’ve fallen down the rabbit hole of Conflict-Free Replicated Data Types (CRDTs)…

Show more
Aral’s Mastodon

This is my personal Mastodon.