sneak @sneak@sneak.berlin

just signed a contract and almost dated it 2019

@surfingalot yes obviously but it is ruining them as a company. they delighted me and a bunch of their other users for *decades*, like a solid 30+ year run, and now they just constantly piss me off with each new release of software or hardware.

it's tragic and sad, like watching a loved one slowly die of dementia.

@friend @sp1rit

absolutely nothing about open source requires that you engage with the community of users. most open source projects are one dude who functions as dictator. it's a common misconception that open source means you have to listen to any outsiders, or even accept patches.

you're also wrong about the security vulnerability thing, too.

@friend @sp1rit

this is false. all of the signal clients are released under the GPL. attitudes of the distributor do not factor in to whether or not something is "open source".

also, after you spout this falsehood, the rest of your comment is full FUD. i get it, you don't like signal, message received. (i don't care about your preferences.)

can we go back to discussing facts now?

@sp1rit @friend imagine if he said you're only allowed to use $BROWSER_NAME to access signal.com

@sp1rit @friend

that comment refers to two things:

1) using the name "signal". a fork should not use the name "signal", i agree.

2) "using the Signal servers". releasing software doesn't use anyone's servers. people who *run* that software use servers, not the people who published the software. moxie is talking about authorized users of signal using forks to talk to signal servers. moxie doesn't get to tell authorized users what software they're allowed to use.

@sp1rit @friend
sircmpwn has an axe to grind against signal, and spreading FUD about it because he doesn't personally like it is his own issue. facts are facts.

@surfingalot it's tragic watching post-jobs apple try to turn into a rentseeker instead of just making good products.

@sp1rit @friend one interesting part of the Signal ToS however is that you consent to permit them RCE on your client machines:

"Software. In order to enable new features and enhanced functionality, you consent to downloading and installing updates to our Services."

@sp1rit @friend I just read the Signal service ToS and nowhere does it say you are restricted to using Signal-branded client software.

Even if they amended it to do so, there is no technical grounds for enforcement, and while I am not a lawyer, I don't think there is much in the way of legal grounds either.

@sp1rit @friend i'm not a lawyer but i'm not sure that there is any legal distinction between an authorized user of the Signal online service using the Signal-branded GPL client and a non-Signal-branded fork client.

technically, if the fork doesn't diverge much, it wouldn't even be possible for Signal to know you're using a fork.

@sp1rit @friend The ToS is an issue between Signal and the *user* of such a fork.

I don't know if services are legally permitted to dictate *how* users of the service can connect to it. In any case, there is precisely zero from stopping a software developer from publishing a non-Signal-branded fork of Signal that connects to Signal servers.

Signal would have to take that issue up with the users that are using that nonbranded fork to connect. I don't think they would.

apple has some serious dark patterns around the options to downgrade your monthly payments for icloud storage amounts. shady as fuck, they are.

heh

https://www.youtube.com/watch?v=wYObKoGMXWg

@alrs you have turned my statement that "the gzip package in ubuntu is pathologically broken and should be fixed or replaced" into some kind of anti-shell-script, "rewrite stuff" tangent. i'm fine with shell scripts calling gz. i like bash. i don't like a 30x slower /usr/bin/gzip for no reason.

this whole "moxie doesn't let signal forks talk to signal servers" is nonsense. signal is GPL, you are allowed to fork it and you are allowed to distribute a fork that connects to signal.org. if moxie has a problem with signal users talking to signal.org (using forked clients), that's a ToS issue, not anything to do with the GPL Signal application, which can have any URLs you want in it.

https://www.theatlantic.com/national/archive/2012/11/its-time-to-stop-using-the-fire-in-a-crowded-theater-quote/264449/

@stelepami why

@alrs if i am compressing a file and it takes 32x longer to compress than it's supposed to, that's broken.

@alrs yes so why is the existing broken one being shipped and not a replacement with the same name?