In his 1959 classic, The Sociological Imagination, the great sociologist C. Wright Mills told students of the discipline:

As a social scientist, you have to … capture what you experience and sort it out; only in this way can you hope to use it to guide and test your reflection, and in the process shape yourself as an intellectual craftsman. But how can you do this? One answer is to set up a blog: there is joined personal experience and professional activities, studies underway, and studies planned. In this blog, you … will try to get together what you are doing intellectually and what you are experiencing as a person. here you will not be afraid to relate your experience directly to various works in progress. By serving as a check on repetitious work, your blog also enables you to conserve your energy. It also encourages you to capture ‘fringe thoughts’: various ideas which may be byproducts of everyday life, snatches of conversation overheard in the street, or, for that matter, dreams. Once noted, these may lead to more systematic thinking and lend intellectual relevance to more directed experience.

and a reference to the currently very small Blue Dwarf social network

1. Succeed is a blurry term. How a social network will succeed?
2. Every social network is there for a limited duration and will be useful to a limited niche of people. Even Facebook: there are more people without an account than with one.
3. Everyone live in a small niche (or communities) that uses only some social networks.
4. Our communities are worth a lot more than the underlying tool used at some point in time.

Brackets are allowed in URLs. It makes it hader to handle than first though!

The author propose a regex, but it is still not valid as only the extended ascii is in it.

Yes, it is hard to parse URL correctly.

Par comparaison, Internet ressemble à la rue

If you live with others get a dishwasher: it feels true! Some of the thoughts are indeed, but I disagree with others.

La réflexion est pertinente:

Si votre salaire était aussi attractif, vous vous en serviriez sans hésiter pour attirer.

Si vous jugez bon de ne pas le mettre dans l’offre d’emploi, c’est qu’e vous ne le jugez pas bon, et donc il ne l’est probablement pas non plus.

L'accessibilité universelle est un principe montrant que rendre un service accessible aux personnes porteuses de handicap est bénéfique pour tous les utilisateurs. Par exemple, utiliser une taille de police de 16 pixels minimum est nécessaire pour les personnes qui ont de la difficulté à voir, mais rendra aussi le contenu plus facilement lisible pour tout le monde.

Comme la situation de handicap peut aussi être temporaire, cela profite aux personnes qui sont temporairement handicapées, comme après un accident par exemple.

Simplifier le langage permettra à plus de personnes de profiter du contenu.

Se baser sur les statistiques d'utilisation de l'application peut être trompeur. En effet, seules les personnes qui auront pu surmonter les différentes épreuves pour arriver jusqu'au contenu apparaîtront dans ces statistiques.

Ce n'est pas à la personne qui utilise votre service qu'appartient la responsabilité de formater des données que vous souhaitez enregistrer en base de données. Par exemple, les messages du type "Entrez votre numéro de téléphone sans tirets" devraient être remplacés par un retrait automatique de ces caractères dans le champ.

Utiliser du HTML sémantique.

Il s'ensuit ensuite d'une liste de recommandations que je connais déjà bien personnellement.

I was lucky to learn this lesson very early in my career: there is no silver bullet, any single tool, no matter how good it is, must be evaluated from the engineering point of view of pros and cons. Everything has a cost, and implies compromises. It's a matter of ROI. Which is hard to evaluate without experience.

JS technologies are reinventing the wheel and breaks compatibility often. More examples are provided.

So it is coming back to reason:

• YAGNI is popular again
• Vue, HTMX and unpoly, alpine.js or just vanilla are getting traction.
• There is talk of coming back to using Postgres for most things.

You do need the cloud, containers, nosql, go, rust and js build systems. Modern software requirements, customers’ expectations and incredible new features are not to be ignored.
Just not for everything.

Lemmy et kbin gagne en utilisateurs suite à la mauvaise gestion de Reddit.

RMS was right since the very beginning. Every warning, every prophecy realised. And, worst of all, he had the solution since the start.

The solution has always been there: copyleft. Copyleft as in "Forbidding privatizing the commons". Here's why:

He also foresaw that if we were not the master of our software, we would quickly become the slave of the machines controlled by soulless corporations. He told us that story again and again.

RMS quickly pointed, rightly, that the lack of "freedom" means that people will forget about the concept. Again, he was right. But everybody considered that "Free Software" and "Open Source" were the same because they both focused on the four freedoms.

Pushing GPL and AGPL was not enough, because

all this work was ridiculed. Microsoft, through Github, Google and Apple pushed for MIT/BSD licensed software as the open source standard. This allowed them to use open source components within their proprietary closed products. They managed to make thousands of free software developers work freely for them.

We need more commons, because:

• young student are taught computer with Word and PowerPoint
• young hackers are mostly happy with rooting Android phones or using the API of a trendy JS framework.
• When an industry receives millions in public subsidies then make a patent, that industry is privatising the common.
• When Google is putting the Linux kernel in a phone that cannot be modified easily, Google is privatising the common.

Fighting back?

Well, the first little step I can do myself is to release every future software I develop under the AGPL license. To put my blog under a CC By-SA license. I encourage you to copyleft all the things!

Add a fifth rule to the free software: The obligation to keep those four rights, effectively keeping the software in the commons.

A documentation about FLOSS

The central thesis is that what these villages can’t tolerate is a sustained large influx of strangers. A stranger in this context is nothing more or less than an unfamiliar face.

Interesting

The different levels of portability:

1. Language
2. Standard Library
3. POSIX
4. 3rd party libraries
5. OS

The more features a program needs, the further out it must reach through the layers.#

Avoid – or wrap – compiler language extensions

C though portable is not suitable as much work as to be done to ensures it works on multiple systems.

In order to use OS extras, use an interface to reimplement it in systems that does not support it.

An ode to know HTML

Je sais qu'on a toujours reproché aux GAFAM de ne pas utiliser des standards, et on gueule maintenant que Facebook veut utiliser ActivityPub et se joindre au Fediverse ?
Bien sûr qu'on gueule ! Absolument TOUS les GAFAM qui ont fait mine d'utiliser un standard l'ont détourné, tordu et rendu incompatible, afin de séparer les communautés. Les exemples sont légion.

Chaque fois qu'un GAFAM arrive à avoir la majorité des utilisateurs d'un protocole, il tue la concurrence.

L'exemple est le mail: en respectant tous les standards, vous serez catégorisé comme SPAM par gmail ou Apple.

He basically says that his startup prioritizes developer productivity over performance.

Even if performance is not a reason to use Rust, the author provides some more:

1. If you know the tech already :)
2. Your service interoperates with services that are perf-critical or can be supported in the future
3. The Serde library is awesome. Check the doc and use cases.
4. It is not amazing with databases but it's very good. Diesel deserves a plus-one: it generates all your SQL queries for you, from a typed SQL schema that it generates from your SQL migrations. It is then similar to the feature of Prisma. It is not perfect though, because of error messages: it makes no sense, or are 60 lines long or difficult to factor out common code.
5. It has better modeling of the business domain: enums and unclonable types.
6. Reliability: we already know it.

Ode for free software workers that leverage these awesome tools :D

That's true: that threat doesn’t hold true for personal blogging.

Because we follow a person. That's all