ubergeek77

joined 1 year ago
[–] [email protected] 48 points 7 months ago

This was the point of the protest. Reddit is all over search engine results, especially Google. If people can't get their answers from a random Reddit search result, the Reddit listings will eventually be deprioritized in favor of other, more reliable sources.

[–] [email protected] 4 points 7 months ago

I’m scratching my head to think what Vultr could do better in this case

There was substantial room for improvement in the way they spoke publicly about this issue. See my comment above.

[–] [email protected] 20 points 7 months ago* (last edited 7 months ago) (1 children)

I still don't like how flippant they've been in every public communication. I read the ToS. It's short for a ToS, everyone should read it. They claim it was taken "out of context," but there wasn't much context to take it out of. The ToS didn't make this distinction they're claiming, there was no separation of Vultr forum data from cloud service data. It was just a bad, poorly written ToS, plain and simple.

They haven't taken an ounce of responsibility for that, and have instead placed the blame on "a Reddit post" (when this was being discussed in way more detail on other tech forums, Vultr even chimed in on LowEndTalk).

As for this:

Section 12.1(a) of our ToS, which was added in 2021, ends with "for purposes of providing the Services to you." This is intended to make it clear that any rights referenced are solely for the purposes of providing the Services to you.

This means nothing. A simple "we are enhancing your user experience by mining your data and giving you a better quality service" would have covered them on this.

We only got an explanation behind the ToS ransom dialog after their CMO whined in a CRN article. That information should have been right in the dialog on the website.

In both places, they've actively done vague things to cause confusion, and are offended when people interpret it incorrectly.

[–] [email protected] 35 points 8 months ago

There was no judgement, only a settlement. Yuzu is not "illegal." Nintendo can abuse DMCA and request GitHub take these down, and GitHub will probably listen, but Nintendo would not be "legally in the right" to do so.

[–] [email protected] 18 points 9 months ago (6 children)

18 isn't long enough, better wait until 34

[–] [email protected] 4 points 9 months ago

Also, if you get the permission of someone in leadership to clone their voice, one angle could be to voice clone someone on ElevenLabs and make the voice say something particularly problematic, just to stress how easily voice data can be misused.

If this AI vendor is ever breached, all they have to do is robocall patients pretending to be a real doctor they know. I don't think I need to spell out how poorly that would go.

[–] [email protected] 10 points 9 months ago (2 children)

Even if this gets implemented, I can't imagine it will last very long with something as completely ridiculous as removing the keyboard. One AI API outage and the entire office completely shuts down. Someone's head will roll when that inevitably happens.

[–] [email protected] 4 points 9 months ago* (last edited 9 months ago) (2 children)

You are giving it the -d flag. -d means "detached." There are logs, you are just preventing yourself from seeing them.

Replace the -d with an -i (for interactive) and try again.

Have you completed the podman rootless setup in order to be able to use it? You may need to edit /etc/subuid and /etc/subgid to get containers to run:

https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md#etcsubuid-and-etcsubgid-configuration

More than likely, this might have something to do with podman being unprivileged, and this wanting to bind to port 80 in the container (a privileged port). You may need to specify a --userns flag to podman.

Running in interactive mode will give you the logs you want and will hopefully point you in the right direction.

[–] [email protected] 3 points 1 year ago (1 children)

Hi :)

If you're already running an instance, you're not going to have a good time of this on the same server unfortunately. The webserver config I ship assumes a single instance, and all of the handling assumes only one domain. You would have to basically modify my entire script to support something like this.

You can take a look at my advanced configuration page to figure out what files you can edit, but this would be a very manual process for what you want to do.

Apologies, but you would be better off deploying a new server.

[–] [email protected] 3 points 1 year ago (1 children)

More like guesswork/assumptions than reality

Sorry to be blunt, but you're not a developer and it shows. Android's build system was purpose made to be reproducible. Electron was not.

There is so much going on in an Electron build, most of which is out of Signal's control unless they maintain an entire fork of the Electron build stack. That is an enormous engineering effort for basically zero benefit.

It probably is functionally reproducible, apart from checksums differing due to build dates baked into the artifacts somewhere. It's not as easy as you think.

If you think it's as easy as "building it in a Docker container," then by all means, try.

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago)

Thanks, I didn't know about this!

But it doesn't look like it supports text message triggers :(

[–] [email protected] 5 points 1 year ago (2 children)

It's not an assumption. The vanilla Signal app has code in it that disables itself after a certain period without updates. Unless they removed that from this app, then this will do the same thing.

view more: ‹ prev next ›