Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.18.6 hotfix release blogpost #142

Merged
merged 5 commits into from
Mar 1, 2020
Merged
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 50 additions & 0 deletions _posts/2020-03-02-newpipe-0.18.6-released.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
---
layout: post
title: "NewPipe 0.18.6 released: Hotfix for the last hotfix"
short: "NewPipe 0.18.6 released"
date: 2020-03-02 00:00:00 +0100
Poolitzer marked this conversation as resolved.
Show resolved Hide resolved
categories: [release, pinned]
author: Poolitzer
image: newpipe
excerpt_separator: <!-- more -->
---

Have you fully read the last blog post and remember the [first paragraph in the Whats New]({% link _posts/2020-02-26-newpipe-0.18.5-released.md %}#what-changes) section? Do you not and you can't care less? Well, I don't care either, I have a story for both of you...
<!-- more -->

## Another release???

Yes, another release. The developers told me they are deeply sorry. And now it is on me to try to explain why you have to update (and I have to write a blogpost...) again.

The build four days ago was a preparation for March, where YouTube shuts down the way NewPipe used to access their website. The release happened as quickly as possible in order to get the update out in time to F-Droid users, since NewPipe basically faces a wait-time of a week for each update.

Now, as you can imagine, basically every part of the app relies in one way or another on a properly parsed YouTube site. After pushing out the update and ensuring in advance that basic funcionalities do work with the new way of accessing YouTube, users and developers where quick to realize that not everything works as well as it used to. So the NewPipe team decided to push out a hotfix for the hotfix, adressing these issues.

## What changes

A lot. All of the entries in the list fix issues not happening in 0.18.4. We have two general improvements though. [@Stypox](https://github.com/Stypox) improved the playback. You are already able to increase the tempo and pitch, and can unlink those settings. So far, you would need to unlink them in every video. Now, NewPipe remembers what you selected, so you can watch every video as linked or unlinked as you like.
If you happen to have one of those fancy fullscreen smartphones with a notch, you can thank [@moneytoo](https://github.com/moneytoo), he made NewPipe support them in fullscreen properly. Now, to the list of fixes, you will love it:

- Proper rounding of number of subscribers, with one instead of zero decimals
- Trending page not containing everything, not only three elements. To be honest, who is actually watching those? Anyway, if you are, you can without any restrictions now. Lucky you.
- Correctly parse special links, not so special anymore, those links
- Pictures of certain channels werent displayed
- YouTube Music playlists work again (yay music)
- Some channels don't have videos tabs, which doesn't break NewPipe anymore (take that, weird channels)
- Video titles with `@` work again
- `#` in descriptions are supported again
- Channel descriptions work again
- 0 subscribers on channels - 0 broken NewPipes. At least now
- Fix channels with multiple views on Videos tab
- Thumbnail URLs starting with // work again
- All search queries which should return something will return something
- Correctly display Network error when a network error happened instead of a general crash error (so much error)
- using less data, based on a new way of accessing only the wanted information instead of the whole webpage. Not really a bugfix but worth a mention

Those people where involved in the fixes, some more, some less: [@wb9688](https://github.com/wb9688), [@mauriciocolli](https://github.com/mauriciocolli) [@B0pol](https://github.com/B0pol), [@gzsombor](https://github.com/gzsombor), [@TobiGr](https://github.com/TobiGr) and [@Stypox](https://github.com/Stypox). Thanks to all of them, and thanks to people reporting the issues!

## Where to get the latest version

NewPipe notifies you about new versions, you can download them when you press the notification. An alternative is the [Github release page](https://github.com/TeamNewPipe/NewPipe/releases). If you use the [F-Droid app](https://f-droid.org/), it notifies you as well about an update for [NewPipe](https://f-droid.org/packages/org.schabi.newpipe/) - please keep in mind that it can take F-Droid a while to update their repository.

Please let us know what your experience of the latest release is, especially bugs in need of fixing. As usual, you can reach out to us via IRC ([#newpipe on freenode](https://webchat.freenode.net/?channels=newpipe)), [open issues on GitHub](https://github.com/TeamNewPipe/NewPipe/issues/new) or ideally use our built-in crash reporter to send us machine-readable issue reports. You can even [send in fixes](https://github.com/TeamNewPipe/NewPipe/blob/dev/.github/CONTRIBUTING.md#bug-fixing) yourself.