Well, Thorium developer stated he intends to support Mv2 past the 2025 deadline. Whether he’ll make it, we’ll see. It’s a one man show, there was some drama involving it in the past, and there’s the question of what’s the point in maintaining Mv2 extensions support if you won’t be able to install them from the store after they’re cut off?
To clarify for anyone curious about the drama, while it was blown out of proportion, it was absolutly vaild.
there was a light nsfw furry easter egg, removed once found. Considering the browser was originally a side project by a young guy (teen/early 20?) it’s not really surprising or a big deal.
Once the browser gained a sudden boost in users and it was found, the image was removed (once the guy got back from vacation? hospital?, there was a month or two gap)
this one was a larger problem for sure, and again removed. If I reacll right, he was apparently hosting a website for a friend about supporting the end of a certain procedure done to baby males at birth. There were some graphic images, its not technically CP anymore than the infomus Nirvana cover, but still…not okay.
To make matters worse, the link the site was somewhere browsers home or about page, making it pretty easy for anyone to find.
It’s all old news now. Personally I didn’t really care, but some people might.
I don’t actually care about the drama per se at this point either. I mentioned it because, along with the fact that:
development is not very open (in that only that one guy commits and releases stuff)
release cadence is very erratic and often lags behind upstream chromium, which is a direct consequence of the previous point
you mentioned about the guys absence - the first time was some time ago and he was inpatient in the hospital for (IIRC) alcohol abuse, and this absence actually coincided with the drama over the furry and the other stuff, so it took awhile for it to be addressed, which only added more fuel to the fire. The second was just this last couple of months were he was house sitting for his parents (mentioned on the release notes I linked before)
All of this paints a bleak outlook for the long term health of this project, IMO. Which is too bad , because I still think it’s one of the better forks of chromium.
Well, Thorium developer stated he intends to support Mv2 past the 2025 deadline. Whether he’ll make it, we’ll see. It’s a one man show, there was some drama involving it in the past, and there’s the question of what’s the point in maintaining Mv2 extensions support if you won’t be able to install them from the store after they’re cut off?
To clarify for anyone curious about the drama, while it was blown out of proportion, it was absolutly vaild.
there was a light nsfw furry easter egg, removed once found. Considering the browser was originally a side project by a young guy (teen/early 20?) it’s not really surprising or a big deal. Once the browser gained a sudden boost in users and it was found, the image was removed (once the guy got back from vacation? hospital?, there was a month or two gap)
this one was a larger problem for sure, and again removed. If I reacll right, he was apparently hosting a website for a friend about supporting the end of a certain procedure done to baby males at birth. There were some graphic images, its not technically CP anymore than the infomus Nirvana cover, but still…not okay.
To make matters worse, the link the site was somewhere browsers home or about page, making it pretty easy for anyone to find.
It’s all old news now. Personally I didn’t really care, but some people might.
I don’t actually care about the drama per se at this point either. I mentioned it because, along with the fact that:
All of this paints a bleak outlook for the long term health of this project, IMO. Which is too bad , because I still think it’s one of the better forks of chromium.