Pipe changelog addpipe.com

Improvement

We finally separated FTP and SFTP storage options. You will see the separation in the Pipe Account Dashboard (credentials and logs) and the documentation.

FTP (File Transfer Protocol) and SFTP (SSH File Transfer Protocol) are 2 diferent protocols.

Moving forward, we expect to deprecate FTP because it is inherently insecure. We plan to add support for FTPS (FTP over TLS). This separation will clear the way for that effort.

New

Improvement

The embed code generated in the account dashboard now enforces HTTPS for the two main assets: pipe.js and pipe.css. Previously it inherited the protocol used to deliver the page in which the code was embedded.

Separately, the Pipe recording client also enforces HTTPS for POST communication and asset loading. Previously it inherited the protocol used to deliver the page in which the code was embedded. This is important for kiosk-like applications where the pages are usually delivered over HTTP/localhost.

Fix

We have fixed an issue where when saving the SFTP credentials, the SFTP folder value was not prepended with a /.

New

Improvement

We've implemented multipart upload for Amazon S3 object storage and compatible services (Google Cloud, Digital Ocean Spaces). This applies to both the Pipe storage and to your own storage for recordings larger than 100 MiB in size.

What this means for you:

1. This method ensures improved throughput, which means that you will experience faster uploads for large files, especially visible if the upload happens between different geographical regions, for example, if the recording is uploaded from our EU2 region towards your S3 object storage located in the US or Asia. From our limited testing, we've observed as much as a 3x increase in upload speeds.
2. Another benefit is that you will be able to upload recordings that are larger than 5 GiB in size.
3. On choppy connections, parts that failed to upload will be retried (up to 3 times) instead of retrying the entire file.

New

Fix

We have updated the Recordings page:

1. Implemented the option for the users to filter their recordings by the UTC date.
2. The Copy and conversion delay is now present for each recording
3. The switching pages of recordings now works properly.

Improvement

On the Dropbox Integration page the user is now able to see which email is connected for each recording environment.

If the user disconnects the Dropbox App, he will see the remaining time it will take for the changes to reflect to our servers, or can manually remove the credentials by pressing a button.

Improvement

We have made a better user experience by making it clearer and notifying the user with an alert that at least one video output should be selected on Transcoding Engine page.

New

The users can now remove themselves completely from our News & Product Updates list rather than subscribing and unsubscribing.

New

We now save the client provided User Agent when a password reset is made and we display it in the account dashboard under https://dashboard.addpipe.com/sessions to let you see from what kind of browser/device the password reset was initiated.

Improvement

We've updated the Singing Webhooks docs with:

1. new info regarding what data needs to be signed (and how to get it) when using application/json instead of application/x-www-form-urlencoded
2. updated PHP code
3. "Signing" instead of "Authenticating"

le: added a new Python & Flask code example