Like any other major network incumbent, Discord cannot simply be side-stepped altogether; appropriate off-ramps are required.

#Matrix bridging enables an incremental, non-disruptive transition from the old to the new.

We invite anyone interested in the development of #CommuneApp to join our newly opened space: https://matrix.to/#/#home:commune.sh

The first half of our product rollout starts next month, as we begin publicly testing our uniquely community-oriented Matrix client.

Microblog link: https://writing.exchange/@erlend/112141665369480242

This article shows the overview of the development process of the Fish Folly game using Fyrox Game Engine.

Rauthy is an OpenID Connect (OIDC) Provider and Single Sign-On solution written in Rust.

Cyber is an embeddable language for fast, efficient, and concurrent scripting, ideal for rapid iteration in games and app development. Made with Zig.

At a glance:

• Easy to learn.
• Dynamic and static types.
• Concurrency with fibers.
• Memory safe.
• FFI and Embeddable.
• Fast VM and JIT.
• Cross platform.

Some excerpts:

What comes out of Big Corp’s ASS

When you hook up your mind to a cloud-controlled Artificial Synthesizer (ASS), you plainly receive their fully digested discharge.

You don’t get to see what happened further up in the synthetic digestive tract of the ASS, where copious amounts of data grub were initially ingested and processed by a divine black-box entity.

You don’t have any insight into where and who those morsels of data came from, and you certainly don’t get any say in which of them the entity should or should not consume for processing and output, delivered to you through the ASS-as-a-Service.

All you’re supposed to do is open your mind’s mouth wide and say “please” and “thank you” for the grossly diluted information bits you’re about to receive.

They’ve already laid claim to our collective land, labor and attention. With AI, they want to own our thoughts and the last shred of agency that comes with them. If we fail to defend our personal sovereignty at this juncture, a dark age of the corporate singularity awaits us."

To land a real blow, look for where the machines are at their most materialized. Take aim at their massive bodies of data and strike there with conviction."

With the now accepted RSA signatures for DPoP tokens, the ephemeral, dynamic clients and the basic serving of webid documents for each user, Rauthy should now fully support. Solid OIDC. This feature just needs some more real world testing with already existing applications though.

EVENT_MATRIX_ERROR_NO_PANIC This new config variable solves a possible chicken and egg problem, if you use a self-hosted Matrix server and Rauthy as its OIDC provider at the same time. If both services are offline, for instance because of a server reboot, you would not be able to start them.

One of the best features of Lemmy is that it supports a combination of image and text. I wish including the source link of a comic would be a standard practice on the fediverse, just like alt-text already is.

Source links are great for:

• Properly crediting and driving traffic to artists
• Checking authenticity
• Preventing image degradation for re-shares

p.s. I was thinking of posting this as a meta-post in /c/comicstrips but I only saw guidelines for how to post comics there.

There’s a major convergence of OAuth/OIDC support across fediverse applications, Matrix is going all-in on it as its root default, and other social web protocols are tagging along as well.

Like the separation of church and state, it seems prudent to keep the management of our digital identities separate from our social network servers.

Domain-based OIDC accounts, especially when self-hosted, serve the function of a minimum-viable ‘nomadic identity’.

With the emergence of Rauthy, being a self-hosted OIDC provider is suddenly viable. All that’s missing is web sign-in (IndieAuth lite) as single sign-on for the masses.

Mastodon post: https://writing.exchange/@erlend/111376285042429865

Oxide is a personal project that takes inspiration from the principles discussed in "Notes on a Smaller Rust" and its follow-up, "Revisiting a 'smaller Rust'". It aims to explore a new language design that simplifies and optimizes the development process while inheriting Rust's best qualities.

Secure by default

It tries to be as secure as possible by default while still providing all the options needed to be compatible with older systems. For instance, if you create a new OIDC client, it activates ed25519 as the default algorithm for token signing and S256 PKCE flow. This will not work with old clients, which do not support it, but you can of course deactivate this to your liking.

MFA and Passwordless Login

Rauthy provides FIDO 2 / Webauthn login flows. If you once logged in on a new client with your username + password, you will get an encrypted cookie which will allow you to log in without a password from that moment on. You only need to have a FIDO compliant Passkey being registered for your account.

Fast and efficient

The main goal was to provide an SSO solution like Keycloak and others while using a way lower footprint and being more efficient with resources. For instance, Rauthy can easily run a fully blown SSO provider on just a Raspberry Pi. It makes extensive use of caching to be as fast as possible in cases where your database is further away or just a bit slower, because it is maybe running on an SBC from an SD card. Most things are even cached for several hours (config options will come in the future) and special care has been taken into account in case of cache eviction and invalidation.

Highly Available

Even though it makes extensive use of caching, you can run it in HA mode. It uses its own embedded distributed HA cache called redhac, which cares about cache eviction on remote hosts. You can choose between a SQLite for single instance deployments and a Postgres, if you need HA. MySQL support might come in the future.

Client Branding

You have a simple way to create some kind of branding or stylized look for the Login page for each client. The whole color theme can be changed and each client can have its own custom logo. Additionally, if you modify the branding for the default rauthyclient, it will not only change the look for the Login page, but also for the Account and Admin page.

Already in production

Rauthy is already being used in production, and it works with all typical OIDC clients (so far). It was just not an open source project for quite some time. Keycloak was a rough inspiration in certain places and if something is working with Keycloak, it does with rauthy too (again, so far).

Really fast post parser, notifications, OpenTelemetry, dedicated job runner, and more!

Now with pre-built binaries for Windows, MacOS, and Linux with install scripts for PowerShell and Bash!

https://corteximplant.com/@0x0/111297237963021572

On Marc Andreessen's "techno-optimist manifesto"

It has been thirty years. The Internet isn’t just the realm of the future anymore. It is also our present and has a substantial past. It is worth examining how the past promises of those 90s techno-optimists worked out.

They promised that technology would solve our environmental problems. And there has, just recently, been some real progress in clean tech. But the trend lines are somewhere between bad and cataclysmic. We do not inhabit the future they insisted they were building. For Andreessen, in 2023, to declare that “there is no material problem – whether created by nature or by technology – that cannot be solved with more technology” is an act of willful self-deception. Just how long are we supposed to clap-and-wait while Andreessen’s investment portfolio tries to science the shit out of the climate crisis?