Update src/pages/about.tsx
All checks were successful
Release to Staging / build_and_release (push) Successful in 1m1s
All checks were successful
Release to Staging / build_and_release (push) Successful in 1m1s
This commit is contained in:
parent
2dccadd670
commit
efa16433e8
@ -13,20 +13,22 @@ export type FAQItem = {
|
||||
const FAQ_ITEMS: FAQItem[] = [
|
||||
{
|
||||
question: "You don't host mod files?",
|
||||
answer: `We could, but that's not the focus. When a creator publishes a mod, they have the option to upload their mod files to whichever server
|
||||
they want, and simply add the link to their post. To the end user, there's no difference, they'd always see a 'Download' button. This results in the
|
||||
censorship-resistant structure of a creator's mod post, however, later on we'll be implementing a system where creators can upload within the site (not to the site)
|
||||
and with multiple options of server host to choose from (to upload to one or more), with us potentially offering a backup, and said system would also
|
||||
provide censorship-resistance to the mod files themselves as well, as anyone would be able to host the files and back them up and provide it for the public
|
||||
to download from, decreasing the chance of the file getting taken down or having it lost.`
|
||||
answer: `We could, but that's not the focus. When a creator publishes a mod, they have the option to upload their mod files
|
||||
to whichever server they want and simply add the link to their post. To the end user, there's no difference; they'd always see
|
||||
a 'Download' button. This results in the censorship-resistant structure of a creator's mod post. However, later on, we'll be
|
||||
implementing a system where creators can upload within the site (not to the site) and choose from multiple server hosts
|
||||
(to upload to one or more), with us potentially offering a backup. This system would also provide censorship resistance to
|
||||
the mod files themselves, as anyone would be able to host the files, back them up, and provide them for the public to download from,
|
||||
decreasing the chance of the file getting taken down or lost.`
|
||||
},
|
||||
{
|
||||
question:
|
||||
'How do you assure security of game mod files that someone downloads?',
|
||||
answer: `When a mod creator attempts to publish a mod, there is a security field that they can fill up that shows a scan report of the files, and users would
|
||||
be able to see that report. If a mod creator doesn't add a report, a promenent warning would be shown to the user on a mod's post (TBA, if not already added).
|
||||
Later, when the new file uploading system (Blossom) gets implemented, along with further security implementations, a scan would automatically happen (depending on the server
|
||||
that it is being uploaded to) and a report would be auto-generated and shared within the mod post.`
|
||||
answer: `When a mod creator attempts to publish a mod, there is a security field that they can fill out
|
||||
that shows a scan report of the files, and users would be able to see that report. If a mod creator doesn't add a report,
|
||||
a prominent warning would be shown to the user on a mod's post (TBA, if not already added). Later, when the new file uploading
|
||||
system (Blossom) gets implemented, along with further security implementations, a scan would automatically happen (depending on
|
||||
the server that it is being uploaded to), and a report would be auto-generated and shared within the mod post.`
|
||||
},
|
||||
{
|
||||
question: "Why are you quoting 'account'?",
|
||||
@ -47,10 +49,11 @@ const FAQ_ITEMS: FAQItem[] = [
|
||||
{
|
||||
question:
|
||||
"You can't do anything about any mod or person? Nothing at all? What about the illegal stuff?",
|
||||
answer: `While we can't directly take down mod posts or ban user accounts, the best that we can is hide posts form initialy being view on the site.
|
||||
However, they can stil be accessible if a user has a direct link, and they can also be accessible on different sites running the same protocol and similar
|
||||
setup to DEG Mods. When non-mods, harmful, or illegal posts are published, such posts would be discovered then hidden. Afterwards, relavent authorities would
|
||||
handle the rest.`
|
||||
answer: `While we can't directly take down mod posts or ban user accounts, the best that we can do is hide
|
||||
posts from initially being viewed on the site. However, they can still be accessible if a user has a direct
|
||||
link, and they can also be accessible on different sites running the same protocol and similar setup to DEG Mods.
|
||||
When non-mods, harmful, or illegal posts are published, such posts would be discovered and then hidden.
|
||||
Afterwards, relevant authorities would handle the rest.`
|
||||
},
|
||||
{
|
||||
question:
|
||||
|
Loading…
x
Reference in New Issue
Block a user