https://sprocketfox.io/xssfox/2021/12/02/xrandr/
Edit: someone already posted it somewhere is in the thread lmao
https://sprocketfox.io/xssfox/2021/12/02/xrandr/
Edit: someone already posted it somewhere is in the thread lmao
Hmmm. What about converting epubs to audio files and then speeding them up? You could do this process on a computer, or probably in termux on the android device.
You should probably migrate now, forgejo is currently a soft fork that is fully compatible, but in the future they are planning to hard fork and not be compatible. Well, they are in the process of doing so right now.
Second comment, but also check out midpoint by evoloum: https://docs.evolveum.com/iam/
It is a modern web frontend on top of Active Directory.
Use an Identity Provider (IDP)*. Other people have mentioned LDAP, which can play this role.
Use groups within the IDP to declare who has what privileges.
Apps using the IDP for auth can read the groups and allow/deny permissions based on groups.
*Or Identity and Access Management if you are in the cloud ig.
For open source solutions, I would recommend:
These three solutions all have invites, ldap, and can act as oauth providers. (Oauth is single sign on), which are the features I want. There are also integrated, including it all in the one app.
There is also LLDAP, which is a web ui for ldap, and then you could use a service that connects to that, like authelia or keycloak, to add oauth on top.
This requires manually enabling every additional provider.
No, it doesn't. The docs are confusing on this, but forgejo has two methods to enable oauth/oidc. One is to manually enable them, but there is a second, where people bring their own openid link.
The docs contain 3 things related to oauth:
I (plus friends who do something similar) have been using centralized auth systems for this stuff. Proxmox supports OIDC, so if you are using Authentik or something similar you can just use one password.
And then Authentik supports 2FA, so you can use TOTP with that, or use passwords only.
In addition to netbox, a wiki or other knowledgebase would be nice. You can document setup procedures as you go, and then other people can use that to figure stuff out.
Forgejo has a feature (that people usually disable) where you can bring your own openid connect url and use it to auth. So if I have my own OIDC provider I am self hosting, I can just use that to log in.
Most people only use OIDC for google and microsoft and whatnot but it's very possible. I don't realkly see what FedCM offers that OIDC doesn't or can't, or why we shouldn't be adding features to the existing and popular OIDC instead.
My one fear with this is offline authentication. I enjoy oauth/oidc a lot, but it doesn't have mechanisms for machines to continue to be able to authenticate while offline, like the way ldap/kerberos can do.
Is this just for machines that will always be online? I can understand that usecase but :/
EDIT: Okay, one comment, mentions himmelblau an alternative to authd, which seems to be more mature. Himmelblau has docs about offline usage. It looks like it has an emergency config that can use a cached password from the oidc provider,
Single-factor authentication (SFA-only) users and Hello-PIN users already have offline sign-in capability
Hmmm. Okay. Upon doing further reseach, it looks like offline authentication is exclusive to Microsoft Entra ID. :/
I use fluxcd with helmrelease's which auto update the helm release. If the helm chart versions specify container versions, then updating the helm chart updates the containers in the deployments.
But for raw deployments, I found this, but not much else.
Also check out meshcentral. Important thing aboout meshcentral is that it lets you hijack the users screen, show you can show them step by step through things. RDP doesn't do that, it kicks the other user out.