Closed dimkauzh closed 2 months ago
Package is banned. It's the same upstream project.
Package is banned. It's the same upstream project.
@xiota Wait but i ported it to use electron31. Is there anything else i need to do then? To maybe get this package to Chaotic?
This should actually be fine @xiota. I reviewed the JavaScript, there is nothing problematic in here. Electron has indeed been replaced in the PKGBUILD as well.
As I just let you know this might be a candidate for opt-in update PRs we could implement, if we decide to add it.
@dimkauzh we are quite suspicious of this developer since a while. There is absolutely no reason to use a custom Electron version imo.
The upstream project developer is the same person as the maintainer of libelectron. While the program currently looks fine, nothing stops him from turning it into a huge phishing project. In principle, the silo packages should also be dropped, which I have previously considered. (Not helpful that shortly after this issue was opened, some one/bot posted suspicious links.)
This should actually be fine @xiota. I reviewed the JavaScript, there is nothing problematic in here. Electron has indeed been replaced in the PKGBUILD as well.
As I just let you know this might be a candidate for opt-in update PRs we could implement, if we decide to add it.
@dimkauzh we are quite suspicious of this developer since a while. There is absolutely no reason to use a custom Electron version imo.
Hmm. Idk the developer much, but I have been using the original package since it's release and it was good. Furthermore, if you don't like the developer (or me I guess) you can just forget about this pr. :)
P.S this aur package (netflix-electron31) is built by me), the other one (netflix) isn't built by me. Also sorry for my bad English.
The upstream project developer is the same person as the maintainer of libelectron. While the program currently looks fine, nothing stops him from turning it into a huge phishing project. In principle, the silo packages should also be dropped, which I have previously considered.
As I'm the one who built the netflix-electron31 package, if the original package turns malicious I just wont update it. Not much more features to add here not gonna lie.
I'm generally against this type of package (unofficial apps for paid services). In addition to the risk of becoming phishing expeditions, they are engaged in blatant trademark infringement. The silo apps have the same problems.
I'm generally against this type of package (unofficial apps for paid services). In addition to the risk of becoming phishing expeditions, they are engaged in blatant trademark infringement. The silo apps have the same problems.
Hmm okay. I'll keep that in mind.
Package:
https://aur.archlinux.org/packages/netflix-electron31
Purpose:
Unnofficial Netflix desktop application. A netflix electron31 port to desktop.
Benefits:
Till now there only has been a silo build of netflix on here, that requires silo to function. This is a electron31 port, which requires electron31, which is from my point of view a little more used. And this is a little more smoother experience than silo-netflix
Building:
makepkg
I tried it withyay
and building from source and it works greatCopyright:
GPL
Expected Interest:
Few
Already available?
No
Unique request?
Yes
Banned package?
No
More information:
This is an issue that's follow up to #3285 being closed because of it using libelectron. I completely rebuild the package to work with electron31, which works great now.