74 lines
3.4 KiB
Markdown
74 lines
3.4 KiB
Markdown
|
|
# **This box URL belongs to no one.**
|
|
|
|
**Drop a file** with the `Edit code` field of your choice **to claim this URL as yours**.
|
|
|
|
So as long as you **keep your edit code**, you will be able to make permissive moditifications to this box,
|
|
including visualizing files, moderation and exclusion of files.
|
|
|
|
**To make modifications to this readme section, drop a file called `README.md`** that will override the
|
|
currently set header. This is how you're supposed to make edits to this section.
|
|
|
|
New boxes have been set to have a **maximum lifetime of two years,** after the lifetime period is over,
|
|
the box files are going to be deleted and the URL is going to be reclaimed. You'll no longer own this URL.
|
|
|
|
Once you've claimed this box, you'll be able to **drop a `config.json5`** with valid [`json5`](https://json5.org/) options
|
|
**to replace the default box configuration.** [The default configuration file can be found
|
|
here](/box-configurations#) along with all customizeble options.
|
|
|
|
## FAQ
|
|
|
|
### Can I set a maximum upload size?
|
|
|
|
Works is in progress. You won't be able to set it above the maximum size set be this instance administrator
|
|
|
|
### Is there a views counter?
|
|
|
|
Works is in progress. There will be one.
|
|
|
|
### Can I block others from viewing the box contents?
|
|
|
|
Works is in progress. You will be able to.
|
|
|
|
### What filetypes are allowed? Can I black/white list filetypes?
|
|
|
|
Per the default configuration, all filetypes are allowed. but works are in progress. You will be able to
|
|
white or blacklist filetypes.
|
|
|
|
### How can I see the IP addresses of the file uploaders
|
|
|
|
You cannot and there is no configuration you or the instance administrator can set that will allow you
|
|
to see address of the uploaders because the servers don't collect them in the first place.
|
|
Let it be known that the instance administrator can still set the server to run behind a reverse proxy
|
|
which would allow him or her to collect data from the client accesses, but even still,
|
|
this is not something the instance has access to and therefore you won't either.
|
|
|
|
### Is the instance adminstrator able to view the contents of this box
|
|
|
|
Yes they are. Whether you trust the instance adminsitrator with these files is up to you.
|
|
|
|
### What can't be uploaded to these boxes?
|
|
|
|
This is up to the instance administrator to define. See [Uploading guidelines](/uploading-guidelines#).
|
|
|
|
### What happens if the instance administrator changes the max lifetime of a box or the maximum upload size?
|
|
|
|
If the max lifetime is changed your newly created box won't be affected and your lifetime will still be the same from when the
|
|
box was created. If the instance administrator changes te maximum upload size, your configurations will be capped to
|
|
conform to those changes. Make sure your configurations are up to date by downloading the `config.json5` from this box at
|
|
every periodic change.
|
|
|
|
### Making changes to these files is hard on a mobile UwU, why can't I edit the configurations with a form?
|
|
|
|
Not our problem. Get a computer.
|
|
|
|
### Why json5?
|
|
|
|
YAML sucks. TOML sucks. JSON sucks. JSON5 sucks less. [Here's what it looks like](https://github.com/chromium/chromium/blob/feb3c9f670515edf9a88f185301cbd7794ee3e52/third_party/blink/renderer/platform/runtime_enabled_features.json5).
|
|
Lua is an option and it actually rocks but that's a bit overkill for this project.
|
|
|
|
### What happens if I lose my edit code?
|
|
|
|
It's totally up to you to not do that.
|
|
|
|
<script>alert("if this is executed it means we screwed up")</script>
|