<commit_before># History

## 5.0.0

- Node versions greater than 8 are supported.
- Changes to vocabulary use:
    - `solid:inbox` is deprecated in favour of `ldp:inbox`.
    - `acl:defaultForNew` is deprecated in favour of `ack:default`.
- Terms of Service may be added and enforced for new registrations,
  but is disabled by default.    	
- DELETE operations on a resource now require that the user has write permissions on
  the file's container
- Improved support for logout ensures users can use different
  identities.
- The profile container is now public readable by default.
- Access Control: 
    - The Access Control List system has undergone extensive
      changes. Security has been tightened, and some unsafe practices that
      where web apps was authorized access in the past are now not
      permitted. 
    - The browser-reported `Origin` header will now be checked by
      default, and the ACL system can be used to restrict access
      to applications for added security.


#### 5.0.0 Upgrade Notes

- As of v5.0.0, all Turtle files need an extension. (**Intervention needed when updating from < 5.0.0!**)
    - **How to upgrade?**
        1. Stop the server.
        2. Update node-solid-server to 5.0.0.
        3. Make a backup of your `data/` and `config/` folders.
        4. Invoke `solid migrate-legacy-resources -v`.
           This makes the files in your `data/` and `config/` folders
           automatically compatible with the new system.
           You only need to do this once.
           Different data folders can be migrated as well with the `-p` option:
           `solid migrate-legacy-resources -p my/custom/data/folder -v`<commit_msg>note verbose<commit_after># History

## 5.0.0

- Node versions greater than 8 are supported.
- Changes to vocabulary use:
    - `solid:inbox` is deprecated in favour of `ldp:inbox`.
    - `acl:defaultForNew` is deprecated in favour of `ack:default`.
- Terms of Service may be added and enforced for new registrations,
  but is disabled by default.    	
- DELETE operations on a resource now require that the user has write permissions on
  the file's container
- Improved support for logout ensures users can use different
  identities.
- The profile container is now public readable by default.
- Access Control: 
    - The Access Control List system has undergone extensive
      changes. Security has been tightened, and some unsafe practices that
      where web apps was authorized access in the past are now not
      permitted. 
    - The browser-reported `Origin` header will now be checked by
      default, and the ACL system can be used to restrict access
      to applications for added security.
- Logging is now verbose by default so the `-v` option has been
  removed and a `--quiet` option has been added to mute the log.


#### 5.0.0 Upgrade Notes

- As of v5.0.0, all Turtle files need an extension. (**Intervention needed when updating from < 5.0.0!**)
    - **How to upgrade?**
        1. Stop the server.
        2. Update node-solid-server to 5.0.0.
        3. Make a backup of your `data/` and `config/` folders.
        4. Invoke `solid migrate-legacy-resources -v`.
           This makes the files in your `data/` and `config/` folders
           automatically compatible with the new system.
           You only need to do this once.
           Different data folders can be migrated as well with the `-p` option:
           `solid migrate-legacy-resources -p my/custom/data/folder -v`
{'fraction_non_alphanumeric': 0.07126502575844304, 'fraction_numerical': 0.011448196908986834, 'mean_word_length': 2.710191082802548, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1007355', 'n_tokens_mistral': 964, 'n_tokens_neox': 910, 'n_words': 470}