ubergeek77

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.

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.

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.

Ahhh RVC is the right word for this sort of thing. Thanks! It's crazy that this was a one day project!

Your AI voice in this sounds pretty natural. Did the AI generate this just via text? Or was it "overlayed" to the original V voice? I've never really messed with voice AI before, so learning how you trained it well enough to fit right in with a game would be a pretty interesting read! I'll even take a TL;DR, I know writing takes a while 😅

Wow, this is awesome. Good work!

Were you thinking about writing up a little blog post or something about how you did this?

Ah, I misunderstood what you were saying at first. You're right, it's not everything on the instance that gets sent, only those things that federated instances need.

But as a user, unless I run my own instance, I don't get to decide when my posts or edits get sent out to any federated servers. That's what I was referring to. All of that stuff gets sent out "like a firehose."

And over time, as more people on Threads interact with certain ActivityPub instances, the range of communities Threads will be sent updates for might as well be the entire instance. If I block them, that's just a visual block. My stuff will still be sent to them, and depending on how they set up their federation, my content might be available on "threads.net" as well.