Spelling #88
Open
Spelling #88
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
jsoref
commented
Sep 19, 2022
Comment on lines
-83
to
+84
| - [Docker Let's Encrypt & NGiNX-proxy](https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion) | ||
| - [DigitalOcean NGiNX reverse proxy](https://www.digitalocean.com/community/tutorials/how-to-configure-nginx-as-a-web-server-and-reverse-proxy-for-apache-on-one-ubuntu-20-04-server) | ||
| - [Docker Let's Encrypt & NGINX-proxy](https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion) | ||
| - [DigitalOcean NGINX reverse proxy](https://www.digitalocean.com/community/tutorials/how-to-configure-nginx-as-a-web-server-and-reverse-proxy-for-apache-on-one-ubuntu-20-04-server) |
There was a problem hiding this comment.
I think nginx has gone through a couple of branding iterations. At this point, they seem to use either nginx or NGINX and not NGiNX.
| NSS implements a pod server and and identity provider (IDP), meaning users can register a WebID, create a data pod and authenticate with it. | ||
| NSS implements a pod server and identity provider (IDP), meaning users can register a WebID, create a data pod and authenticate with it. |
There was a problem hiding this comment.
The current iteration of check spelling can flag duplicate words...
| @@ -5,7 +5,7 @@ \section{Proof of Concepts} | |||
| The goal of these modules is the symbiosis of decentralized stored data in a highly functional system without comprising its \textit{Performance}, \textit{Security}, or \textit{Usability}. | |||
|
|
|||
| % subsection POC A | |||
| \input{thesis/latex/sections/03aa-commeting-module} | |||
| \input{thesis/latex/sections/03aa-commenting-module} | |||
| The implementation of Solid comes with imperfections. The detailed analysis and evaluation of the Solid apps have shown those flaws in the synergy between Indico and Solid principles. The flaws being mainly performance regressions in the retrieval and distribution of data from several external data pods. Where in centralized systems the data is stored in one place and can be processed and prepared for clients neatly, in a decentralized architecture several requests are required to retrieve the data first. The prototypes' design was as decoupled as possible from Indico to not infiltrate Indico's functionality and allow other systems to integrate the modules as well. The decoupling has proven that the two systems are too distant and implementations need to be closer to Indico. A more imminent solution means Indico is required to change too. The data flow from the data pod back in to Indico, as demonstrated in the second implementation of the \gls{poc}, is challenging by reason of lacking any semantic structure whatsoever in Indico. | ||
| The implementation of Solid comes with imperfections. The detailed analysis and evaluation of the Solid apps have shown those flaws in the synergy between Indico and Solid principles. The flaws being mainly performance regressions in the retrieval and distribution of data from several external data pods. Where in centralized systems the data is stored in one place and can be processed and prepared for clients neatly, in a decentralized architecture several requests are required to retrieve the data first. The prototypes' design was as decoupled as possible from Indico to not infiltrate Indico's functionality and allow other systems to integrate the modules as well. The decoupling has proven that the two systems are too distant and implementations need to be closer to Indico. A more imminent solution means Indico is required to change too. The data flow from the data pod back into Indico, as demonstrated in the second implementation of the \gls{poc}, is challenging by reason of lacking any semantic structure whatsoever in Indico. |
There was a problem hiding this comment.
-The data flow from the data pod back in to Indico,
+The data flow from the data pod back into Indico,
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I was going to send you an updated workflow, but it seems you just deleted it, that's fine (I'd rather you not use it than use the version you were using).
Anyway, here are spelling fixes.