ubergeek77 @ ubergeek77 @lemmy.ubergeek77.chat

Posts

3

Comments

168

Joined

2 yr. 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.

Cloudflare Tunnels are black magic and exactly what you're looking for:

https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/

Free, no need to self host a server somewhere externally. Can even be used for SSH!

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.

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.

They also don't magically make lawyers free. No lawyer is going to bother with an EULA squabble pro bono.

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.

I'm not talking about that. I'm talking about this:

I agree with the sentiment here, but all the technologies mentioned allowed us to ship a working application in a timely manner. I think that should always be the first goal. Now that this is out of the way, we can start looking at improving efficiency, security, resilience etc.

"Security Second" is not good messaging for a project like this.

But I'm glad my comment was hilarious to you.

I don't need or want replication of my private projects to a peer to peer network. That's just extra bandwidth to and from my server, and bandwidth can be expensive. I already replicate my code to two different places I control, and that's enough for me.

I'm not sure who Radicle is for, but I don't think the casual hobbyist looking to self host something like Forgejo would benefit at all from Radicle.

Loading the source code for Radicle on Radicle also seems fairly slow. It seems this distributed nature comes at a speed tradeoff.

With the whole Yuzu thing going on, I can see some benefit to Radicle for high profile projects that may be subject to a takedown. In that respect, it's a bit like "Tor for Git."

I suspect that over time, pirate projects and other blatantly illegal activities will make use of Radicle for anti-takedown reasons. But to me, these two projects solve two different problems, for two different audiences, and are not really comparable.

Edit: There is already enough controversy surrounding Radicle, that, if I were someone looking to host a takedown-resistant, anonymous code repository, I would probably be better served hosting an anonymous Forgejo instance on a set of anonymous Njalla domains and VPSes. The blockchain aspect was already a bit odd, and what I'm now seeing from Radicle does not exactly inspire confidence. I don't think I'll ever use this.

It was just how the settlement was worded; this team is prevented from distributing "anything that circumvent's Nintendo's blah blah," and Citra was developed by the same team. So, it got taken down all the same :(

Great work, thanks!

Anything on Citra? PineappleEA made it easy enough to also download binaries for Yuzu, but I've got nothing but a flatpak for Citra.

A central place for binaries of both emulators would be great.

Both flatpaks are still available, by the way:

https://flathub.org/apps/org.yuzu_emu.yuzu

https://flathub.org/apps/org.citra_emu.citra

They can be bundled and exported after downloading, although it will only be for the architecture of your machine.

Then I'm probably wrong. It's not clear at all how those apps are doing it though. The API documentation is rough.

It doesn't seem like the Lemmy API provides any way to tell if a remote instance has downvotes disabled or not.

18 isn't long enough, better wait until 34

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.

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.

The API that FDroid is using has only just come out.

Not true. Android has supported rootless unattended upgrades at a system level since Android 12 (October 4 2021). That was nearly 2 and a half years ago, so it's been a while.

This is what Neo Store used. F-Droid only just now got around to supporting this with this recent update.

I don't think they were disagreeing with you, I think they were just trying to say:

You shouldn't need braces to be vertically aligned if your code is uniformly indented. Then you can easily see what code is paired together just by their indentation level.

Of course this is not always true if you've got a bunch of crazy nested indentation pushing things off to the right.

Makes sense. The article calls it "unwarranted gatekeeping," but they wouldn't say that if they knew how Android internals work.

Looking at the video demo for Circle to Search, it's very likely they built this on top of ActionsServices, an Android component that enables extra interactions on top of the Recents switcher. This is already what's being used to do things like OCR in the Recents switcher.

Other non-Google ROMs use ActionsServices too, but their implementations vary, and they can't just "tack on" something as complicated as this onto any vender implementation of ActionServices and expect it to work. They might not even have a vendor rollout plan for this thing yet, for all we know it was rushed out the door.

Google has had a tight partnership with Samsung since the Pixel 6 came out, which is why it doesn't surprise me that Samsung will be getting this feature first. Google can essentially boss Samsung around for little system things like this.

The "for a long time" comment was probably due to Android 15 already being mostly final at this point. I wouldn't be surprised if there were core changes to Android to allow more pluggable customizations to the Recents switcher in Android 16. That might enable Google to offer this feature to other vendors more cleanly (assuming the feature survives that long, which is doubtful).

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.

What's the logo that looks exactly like Arch but with a stylized X over it? I can't find any distro with that logo.