ubergeek77

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.

AVNC is open source and it at least has a mini keyboard where you can queue Super to be held with your next keypress

https://f-droid.org/en/packages/com.gaurav.avnc/

If you're using a USB or Bluetooth keyboard, it's probably not possible for you to use your actual super key on it. That gets translated to "Home" in Android which is why you go back to your launcher. For whatever you're trying to do, software keys is probably the only option.

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.