erebion

joined 1 year ago
[–] [email protected] 1 points 3 weeks ago* (last edited 3 weeks ago)

I already have an invite flow that users will arrive at and go through when signing up, now I want to let users create invites for other users. That page does not mention anything about that. It seems to be about adding a flow that asks user for details such as an email address and then they get their account.

In my case users have already gone through that and want to invite someone else.

With invitations, you can either email an enrollment invitation URL to one or more specific recipients with pre-defined credentials, or you can email a URL to users, who can then log in and define their own credentials.

I already have enrollment invitation URLs. Just not automatically. I wrote a script that uses the API for that purpose.

The docs even mention this about the flow:

Enrollment (2 Stage)

Flow: right-click here and save the file.

Sign-up flow for new users, which prompts them for their username, email, password and name. No verification is done. Users are also immediately logged on after this flow.

[–] [email protected] 1 points 3 weeks ago* (last edited 3 weeks ago) (2 children)

Nope. Not what the question is about. This requires an admin user to create an invitation in the admin backend. I want a way to let users do that.

 

Hey there,

I'd like to allow users in a specific group (not the admin group) to create invites for Authentik, so that people at my hackerspace can invite others to our Single Sign-On system.

Has anyone got a recommendation or idea how this could be done?

We also have a Nextcloud instance, maybe there's a simple tool that allows Nextcloud users to trigger an API call without revealing any API secret?

All we need is an input field that forces users to note who the invite is for and a button that allows creating it and receiving a link.

[–] [email protected] 3 points 1 year ago

Do you get fined if you are unlucky to have no harvest and cannot bring anything back?

[–] [email protected] 2 points 1 year ago

Oof, hopefully you have photos at least.

[–] [email protected] 5 points 1 year ago

Now... I'd love to read a How To.

[–] [email protected] 4 points 1 year ago

Depaving the way to a bright future, love it.

 

Most parts work, still not sure why Bluetooth gives me errors in dmesg, audio out works, microphone input not yet... I'm getting there.

But graphics, charging, low standby power consumption, LTE, wifi... those all work already.

The fact that postmarketOS has support and also that there are people working on mainline support, makes this a task that is not as difficult as I thought, as most work was already done for another distro.

Otherwise it runs more fluid than Android ever did on it and it has a great standby time (forgot to turn it off at around 80 % and a few days later it was at 58 %).

For now stuck on merging the Kernel patches from the sdm670-mainline project with those from Mobian, not really something I can do without knowing C. I just hope someone with the right skills does it at some point.

Then I just need to make some smaller merge requests, like one to add a udev rule for vibration support and so on.

Not much missing before I can finally use it as a daily driver.

 

What is the current state of Gnome mobile?

Will the patches get merged to the main branch, so it just becomes available on all diatributions?

Why has only PostmarketOS packaged it so far?