Import et Export of software forges (issues, PR/MR, milestones, release assets, etc...)

Ou comment tous les monde se trompe entre la cour d'appel, la cour de cassation et la partie plaignante.

Un témoignage d'une personne qui a tout appris sur le tas

Continuant Scribouilli, Ardoise "va télécharger le dépôt fourni, l'analyser et générer le site. Puis, Ardoise publie le site à une adresse correspondant au nom du dépôt. Par exemple, si le dépôt s'appelle "citron", le site sera disponible à l'adresse : https://citron.ardoise.net/"

Ardoise est un outil libre permettant à tout un chacun de publier un site statique en ligne.

Ardoise est un projet né suite au constat qu'énormément de personnes utilisent les outils privateurs Github de Microsoft pour publier des blogs personnels, de la documentation de projets open-source et d'autres choses encore.

Suite à ce constat, le besoin de permettre à ces personnes de s'émanciper de cette nasse logicielle a grandi et les idées parfois floues ont abouties à un projet concret.

Un service d'hébergement simple à prendre en main (pour des non-initiés)

(via PSES 2024 https://video.passageenseine.fr/w/73BkMhTGTRzHrTiSeZQ5yT)

Great for many usages.

Numeric IDs take up a lot less space though. ULIDs are a bit long, which is inconvenient for URLs and sometimes, it's undesirable to expose when an ID was created.

(via https://sebsauvage.net/links/?XLKraA)

divergent meetings: goal is to generate idea

convergent meeting: goal is to come to a decision

chemistry meeting: there is no tangible output. The goal is to get to know one another.

These three should cover 90% of the possible meetings.

And if you’re trying to categorise a meeting and you find yourself thinking, “This meeting is mostly so I can deliver information” …that meeting should be an email.

• gen blocks: similar to python generators as far as I understand. They are lightweight compared to the classic Iterator pattern
• default field values (and avoid new() for it)
• inner structs
• never type
• try expressions

The ability to run scripts is also a great feature imho.

Create a type similar to another existing type :O

Some interesting statistics.

Rust interact with other parts of the codebase through

1. Rest API (56%)
2. Language interop (44%)
3. RPC (21%)
4. WebAssembly /WASI (19%)

Projects developed in Rust are:

1. CLI tools (40%)
2. Systems programming (38%)
3. Web development (35%)
4. Desktop / GUI applications (21%)
5. Network programming (17%)
6. Embedded / IoT (12%)
7. Academic /Scientific / Numeric (9%)
   and more games, databases, DevOps, Security, data science / ML / AI, Blockchain, ...

As for why: write safer code, build high-performance applications, iterest or fun, improve skills and career opportunities (stay competitive in the industry), handle concurrency or multithreading safely, ...

How to learn?

• official rust documentation (95%)
• books (32%)
• video or podcasts (19%)
• online courses (12%)
• University or academic coursework (5%)
  and employer-provided training, rust training companies, ...

• the engine of application state (instead of deferring it to the server), when possible
• web apps AND desktop apps: all in one
• a universal binary format
• reuse other tools in the browser such as @ffmpeg/ffmpeg

Tauri reuses the system web view instaed of shipping the entirety of Chromium.

[...] If that scares you, remember that Figma, a ui design tool, took over the market with an app built on web technologies. Same for Visual Studio Code, Slack, Discord, Microsoft Teams, and an increasing number of apps nowadays. Always bet on the web!

This is how they build https://nemastudio.app/

The paper in question: https://aclanthology.org/2023.findings-acl.426.pdf

Gzip output could be used as input for LLMs. They won't be "Large" in this case and this is a perfect fit for less ressource consumption.

(via https://nicolas-delsaux.hd.free.fr/Shaarli/shaare/kyvTdw)

CryptPad is a great tool and I can only be relieved that the United Nations start to use it.

The project runs mainly thanks to research grants. Only 20% comes from donations or suscriptions.

The main selling poitn is it's easy for users to share encryption keys for sharing documents.

The first method — for those without accounts — works like this: When you create a document, a key is generated in your browser and stored locally in your computer or your encrypted drive. When you share this document with a user without a CryptPad account, a URL with a long string after the “#” is sent, containing both the address of the document and the encryption key. What is important is that all content in the URL after the “#” is never transmitted to the server, which means the encryption key stays private.

If you and the person with whom you are sharing both have accounts with CryptPad, you have the additional option to share content using CryptPad’s internal sharing mechanism. This allows sending the document keys in a public-key encrypted box that only designated recipients can open. [...] Also, CryptPad is even more private, because an important feature is that anyone who hosts your data will never have access to the encryption keys.

Another thing to remember is CryptPad will only be as secure as your computer and browser.

Also be careful with browser extensions, because these can snoop in your URLs.