| Git Clone URL: | https://aur.archlinux.org/slimjet.git (read-only, click to copy) |
|---|---|
| Package Base: | slimjet |
| Description: | Fast, smart and powerful browser based on Blink.(Prebuilt version) |
| Upstream URL: | https://www.slimjet.com |
| Keywords: | blink browser chromium slimjet web |
| Licenses: | LicenseRef-Freeware |
| Conflicts: | slimjet, slimjet-beta, slimjet35 |
| Submitter: | denkijin |
| Maintainer: | ahmedmoselhi (zxp19821005) |
| Last Packager: | zxp19821005 |
| Votes: | 35 |
| Popularity: | 0.000027 |
| First Submitted: | 2015-08-22 22:29 (UTC) |
| Last Updated: | 2025-03-10 03:33 (UTC) |
@ahmedmoselhi, great that you take care of this package.
It is a very good idea to add the file libffmpeg.so to the PKGBUILD. However, it seems to me that it would be better and clearer if this file was downloaded directly from the author of this file from https://github.com/nwjs-ffmpeg-prebuilt/nwjs-ffmpeg-prebuilt/releases
@dalto yes i have fixed that . I also added modified version of libffmpeg.so to fix video playback issues
It looks like you forgot to update the package sums in your last version bump.
Also, the .SRCINFO changes seem wrong.
You don't need to edit the .SCRINFO manually. You can use makepkg --printsrcinfo > .SRCINFO after you have updated the PKGBUILD.
I have updated to slimjet 35.0.2.0
./flashpeak-slimjetThis is fastest browser. (tested on Windows Starter 32-bit, Intel Celeron N3060, 2Gb RAM ) Now install it on Ctlos (ctlos.github.io)
Current version : Slimjet Version 34.0.2.0 (based on Chromium 98.0.4758.9) (Official Build) (64-bit)
After reading these linked articles, I don't see anything to worry about. This information from 2018 is mostly out of date (you can now use the Duck Duck Go search engine) and the Windows user mentioned there probably had some malware for Windows.
Slimjet has many advantages and it would be good if there was a slimjet package maintainer to update it to the latest version 33.
@beserkk: Okay, the second reference you provided is subjective in my opinion. Those users could have picked up the backdoor from the browser they used to download Slimjet or they may have picked it up beforehand and only noticed it after installing Slimjet. Additionally, all of the users were using Windows, not Linux.
Regarding the first reference that you provided, it appears that that user was also using Windows. Maybe it's a Windows thing?
If you have an account for the Slimjet forums, it would be interesting to see what the Slimjet devs response would be to your findings. I just searched the forums and didn't find anything.
@beserkk: Both references provided are from 2018. Is the information still valid?
@dalto: You might consider reaching out to the Slimjet development team about the issues you're encountering. I also appreciate the work you've done; thank you.
Pinned Comments