Node.js

https://fetch.spec.whatwg.org/#body-mixin

@jasnell I think the Blob and consumer helper text() methods need to run through toUSVString which is used in the url module?

Since iOS has changed its cookie policy named as INTELLIGENT TRACKING PREVENTION (see risetechnologies/cookieTest#2 (comment) for a brief explanation) cookies set by the server are not being taken into account anymore (also see https://forums.meteor.com/t/sticky-session-using-cookies-and-cordova/44419/9).

This is especially an issue if load balancers use

Describe the bug
Using xframe ALLOW-FROM throws error in console: Invalid 'X-Frame-Options' header encountered when loading 'https://api.dev.mysite.com/uploads/my-file.pdf': 'ALLOW-FROM dev.mysite.com' is not a recognized directive. The header will be ignored.

https://strapi.io/documentation/v3.x/concepts/middlewares.html#response-middlewares
instructions for xframe indicate `ALLOW-FR

Our internal, server-side i18n package is deprecated, and so is the use of i18n.t().

Instead we have a new package @tryghost/tpl that does string interpolation and makes refactoring i18n out of the codebase easier.



We have successfully removed i18n.t() from core/frontend, but the rest of the codebase has many many references that need to

Hi, I'm trying to read a CSV file like this (;, delimiters):

A;B;C;D
1,1;2,2;3,3;4,1
1,1;2,2;3,3;4,1
1,1;2,2;3,3;4,1

What happens: semicolon from the first line does not become the main separator, the comma from the second line does and it breaks the file's logic.

Code that reads:

X.read(e.target.result, { type: 'string' })

Result

{
      A1: { t: 's', v:

The file ~/.config/joplin-desktop/log.txt is never rotated or truncated, and gets included in every Time Machine backup. The longer you've been using Joplin, the slower your backups run.

% cd ~/.config/joplin-desktop
% head -5 log.txt
2021-03-15 21:28:13: App: "Profile directory: /Users/jgreely/.config/joplin-desktop"
2021-03-15 21:28:13: "Database was open successfully"
2021-03-15 2