c0ntroller/frontpage-content
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Spelling fixes...

Browse Source
This commit is contained in:
Daniel Kluge
2022-10-18 17:56:26 +02:00
parent a5161afd72
commit 1af6779b0a
11 changed files with 43 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
projects/ol-git.adoc
View File

@ -1,5 +1,5 @@
:experimental:
:docdatetime: 2022-07-29T11:27:37+02:00
:docdatetime: 2022-10-18T17:56:27+02:00
= Overleaf Sync with Git
@ -43,7 +43,7 @@ But how to use them?
== Access granted
I noticed the front end uses session IDs for user authentification.
I noticed the front end uses session IDs for user authentication.
You get an ID, you POST valid credentials (and a CSRF token) to `/login` and your session ID get's "verified".
Using their repository, it was easy to find other routes that are useable.

6
projects/simple-cb.adoc
View File

@ -1,5 +1,5 @@
:experimental:
:docdatetime: 2022-08-08T12:19:20+02:00
:docdatetime: 2022-10-18T17:56:27+02:00
= Simple Callback Server
@ -12,12 +12,12 @@ Still, I needed it sometimes and I didn't want to rewrite it every time I use it
== What can it be used for?
When creating a dev application on Google, Spotify, or other services you often have some heavy authentification flow to get access.
When creating a dev application on Google, Spotify, or other services you often have some heavy authentication flow to get access.
But normally I want to use the API for private projects and it's _my_ account that gets authenticated every time.
To make reauthentication easier these OAuth protocols often provide a "refresh token" which can be used to get a valid new token.
To get the initial authentification token and to get such a refresh token you provide a callback address where you get redirected after the user logs in.
To get the initial authentication token and to get such a refresh token you provide a callback address where you get redirected after the user logs in.
The tokens and meta information normally are sent in a `POST` body.
And this is where this small application is necessary.

16
projects/terminal.adoc
View File

@ -1,9 +1,9 @@
:experimental:
:docdatetime: 2022-08-10T17:09:32+02:00
:docdatetime: 2022-10-18T17:56:27+02:00
= c0ntroller.de
= Terminal
Hello and welcome to my website.
Hello and welcome to my CLI website.
== Why did I do this?
Mainly because of boredom and because I like to code.
@ -62,12 +62,12 @@ I talked about shortcuts before, but here's a list of which shortcuts are possib
|kbd:[▲] / kbd:[▼]
|Scroll through last commands.
|kbd:[Strg+L]
|kbd:[Ctrl+L]
|Clears the history. +
Similar to `clear`.
|kbd:[Strg+D]
|Exits the page. Don't work in (most?) cases because of a https://developer.mozilla.org/en-US/docs/Web/API/Window/close[JavaScript restriction]. +
|kbd:[Ctrl+D]
|Exits the page. Doesn't work in (most?) cases because of a https://developer.mozilla.org/en-US/docs/Web/API/Window/close[JavaScript restriction]. +
Similar to `exit`.
|kbd:[Ctrl+U]/ +
@ -82,8 +82,8 @@ kbd:[Ctrl+C]
- Every line in the history window is parsed in a custom format.
* `%{command}` is parsed to a clickable command
* `#{link text|url}` is parsed to a link
- Project logs are loaded dynamicly. They can be updated at any time.
- There are lots of eastereggs. Some are for specfic people, some for me and some for fun.
- Project logs are loaded dynamically. They can be updated at any time.
- There are lots of eastereggs. Some are for specific people, some for me and some for fun.
- I made some custom annotations for code blocks show faulty code (wrong syntax/will not compile/etc.).
[source.notCompiling, rust]