I for sure will never touch Pale Moon. This is absurd.
@mulander What the hell even is it
I've never heard of it before and the hits I'm seeing for it sound like something I'd expect to be loaded with adware
@zigg @mulander it had a use *briefly* when mozilla put DRM into their browser - it was probably the most mainstream mozilla fork to take an anti-DRM stance. But this isn't the only thing they've done Wrong. They also removed the ability to install AdNauseam add frustration tool. That's when I forked https://github.com/themusicgod1/Paler-Moon/network
@mulander That "you will" phrasing was unforgivably presumptuous.
If somebody addressed me in that fashion, and they weren't paying me, I would tell them to fuck off. Hell, I'd probably tell them to fuck off regardless.
@starbreaker read my last comment, they fucking attacked him on a work in progress repo - he approached them 2 days earlier on their forum to coordinate branding & upstreaming patches. This is infuriating and insulting.
@mulander No shit. It's almost as if the Pale Moon clowns think OpenBSD is some fly-by-night operation.
@mulander Moonchild seems to have very ... peculiar opinions in general. They're also under the impression that the purpose of TLS certificates is to mark websites as non-fraudulent: https://forum.palemoon.org/viewtopic.php?p=117501#p117501
Yep, that's definitely the kind of understanding of the Web PKI I'd wish for from a browser vendor.
@mulander a fun game is to look through mozilla's security advisories from about a year or two ago, find a good one (sev:critical, rce), search mozilla's tree for the bug number to find the patch, and then check if pale moon has the same code and if they patched it 😬
that's why I won't touch it
@cb Never realized that Pale Moon does not have the same code like Firefox? The patches what Mozilla inserts are useless if the code does not exist in Pale Moon. And pretty much code of Mozilla of lately is not around.
How should the security issue arrive then? Present from Avatar or Santa Claus?
@DCM @cb they might not share newly added issues (assuming they don't take any patches from upstream Firefox) but they do share a common ancestor so a large portion of the code.
Very often, newly found vulnerabilities are actually very old.
Take for example this: https://www.securityfocus.com/bid/96691
Security issue from March 2017 - it was present in the browser since Mozilla Firefox 0.1...
@mulander wooooww, that's some grade-A assholery.
Like, I get it, they think someone is violating their terms. why be so confrontational about it? that's pretty much a case study in how _not_ to approach this kind of issue
@mulander What a total waste of resources.
@mulander why so uppity about the brand? they didn't build that browser
@mulander they don't really have anything riding on that branding that i'm aware of, and this is, like, an under-the-hood change so the browser works better. i don't get it
@KitRedgrave I'm afraid I'm not the person to answer that. Usually I would suggest asking the authors but you might want to consult your lawyer before getting in touch with them.
@mulander i am not gonna poke this with a stick. i have no stake in any of this
@mulander
Instead of discussing things - it is ok to be agressive right from the start. There is no sane middle ground anymore....
@mulander Wow. That's a textbook example of "how to be a dick." I feel I should take notes.
@mulander Doesn't Mozilla do the same thing with Firefox?
@rook @mulander
I believe so, however the issue (in this thread) isn't about the branding. It's about Palemoon's response to a work-in-progress repo to port it to OpenBSD, which was not being distributed at the time of the github issue. @bcallah had reached out to them about the branding through their forums, and this issue on github is their response.
At least, that's how I understand it.
@architect @rook @mulander That's a good summary of it.
@architect @mulander @bcallah yeesh, if so that's pretty bad. Though I don't really see any bad intentions here, just an utter lack of tact. Idk.
@rook @architect @mulander I also don't think there were bad intentions either. But a "Hey, do you mind disabling x, y, and z while we figure out all the logistics?" from them would have been met with a "Sure, no problem." from me. I have better things to do with my time than deal with attacks in response to my trying to work with them.
@bcallah @architect @mulander I hear that, just the way I'm hearing it it sounds like a response was solicited?
If so, it kinda comes off as a list of requested instructions. Again, totally tactless.
Don't get me wrong, my response to that kind of comment would be very stern regardless of their intent.
@rook @architect @mulander Yes, I was looking for a response. But the response was a bit unexpected to say the least.
@mulander @architect @rook And since according to upstream, this browser is his full time job (IIRC) and I was coming as a potential volunteer who would provide more users (and thus more income for him... none of which I would see), I guess the last thing I was expecting was the response I got.
@mulander the fact that besides open source software licenses people will still have to deal with special redistribution licenses is completely insane. That shouldn't even exist at all. Well wtv, good to know to stay away.
@mulander I love pale moon but this is not good at all.
@mulander wow, this is crazy. Pale Moon biggots.
They even have gentoo vocabulary (“portage trees, overlays, ebuilds”) in their license stuff…
@mulander Well they can stick a brolly up their arse and open it.
@mulander ...and the absurdity comes from tobin
why am i not surprised?
@mattatobin @mulander what? you've been absurd since i've known you :P
@feld in that case you are in violation ;)
Especially since the port is named palemoon and has --enable-official-branding in the Makefile ;)
>> "You will" indeed...
> Technically, he wasn't wrong. Those lines were in fact removed as part of deleting the port :)
:-D
https://lists.freebsd.org/pipermail/freebsd-ports/2018-February/112462.html
This whole thread is getting even more bizarre https://lists.freebsd.org/pipermail/freebsd-ports/2018-February/112469.html
@mulander the Pale Moon Cartel will break your kneecaps if you 'misuse' their O F F I C I A L B R A N D I N G
@Cybertrash @mulander excuse me, that's ＯＦＦＩＣＩＡＬＢＲＡＮＤＩＮＧ (if you're going to fullwidth, fullwidth right)
@calvin @Cybertrash hey, you can't use the system font for that.
@Cybertrash @mulander They are not wrong though... he just pointed out, correctly, that it is a violation. Perhaps a bit precipitously but why should he wait? He didn't use any foul language. He was direct.
I think Ibra was the one who had a bad day... Respecting licenses is important. Everyone in FOSS knows this. It is bad when a non-foss project misuse this.. but a foss-project like openBSD should know better. Instead of just acknowledging the issue he demanded to talk to the IP owner...
@shellkr @Cybertrash please read my comment on the github issue.
Ibra approached them 2 days before this whole thing on github popped up. Asking on how to cooperate & coordinate. Not a single copy of pale moon was distributed, that repo is a draft in progress of a port. They jumped the gun.
@mulander @Cybertrash I did.. but consider it a bit beside the point. Unless mattatobin participated or knew about that forum conversation. Do you know if he did?
I think Ibara sidestepped a bit there.. He could have mentioned the post on their forum e.t.c.. instead of just demanding to talk to the IP-holder.
It is sad to see it went the way it did.
@shellkr @mulander @Cybertrash Yes he did. He followed the link in my post on their forums to get to the github.
@shellkr @mulander @Cybertrash I actually didn't see the thread on the forum until later. I hadn't been reading every thread/post for the past week or so because I had been very busy.
@mulander pale moon is garbage and has been garbage the entire time.
@mulander aka the pale weasel :)
@mulander purged from my system too :D
@mulander oh for fuck's sake, I was going to try out Pale Moon today on my Alpine because hey it's an old Firefox it should be lightweight enough for my system