cross-posted from: https://piefed.world/c/technology/p/1296065/ftc-sues-hims-hers-for-sending-user-health-info-to-meta-snap

cross-posted from: https://piefed.world/c/tech/p/1296064/ftc-sues-hims-hers-for-sending-user-health-info-to-meta-snap

Forgive me if this is yesterday's news to some of you, but I just found this amazing replacement for the proprietary Japanese keyboard simeji: sumire

That's all.

Also, if anybody here happens to already use it and know whether it's possible to adjust this somewhat ugly disproportionate toolbar, please advise!

Someone (average smartphone user) complained to me the other day that there isn't a clear solution to navigating the web because it's either ai slop or the results are poor.

And I kinda agree, nowadays you do have to put in some more effort to get what you're looking for.

And so I told them I'd compile a list of which search engines are best for what purpose.

So far I have:

Startpage: works, but does a poor job of finding product codes and whatnot.

Duckduckgo: gives more general results afaik

Ecosia: works great but relies on bing

I have tried things like qwant ect but haven't really settled on those.

Any other suggestions?

I'd tell em to use udm14 but it's still google so I'd rather keep that as a plan B.

OQB @FreddiesLantern@leminal.space

in its first iteration, it strips all AI shit, doesn't just disable it; the hero went through the source tree and patched it by hand!

it differs from LibreWolf and friends as there's an intention to hard-fork the thing (LW should be based on basebrowser) and let the abomination that is the mozilla shell-game-corp of today behind, thus returning to the original idea behind creating mozilla, best described by the dude who gave us the thing:

In my humble but correct opinion, Mozilla should be doing two things and two things only:

1. Building THE reference implementation web browser, and
2. Being a jugular-snapping attack dog on standards committees.
3. There is no 3.

mastodon thread: https://mastodon.social/@sarahjamielewis/116994970688711387

the patch repo: https://codeberg.org/basebrowserproject/organization

firefox repo: https://github.com/mozilla-firefox/firefox

build instructions: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html

the only thing missing's how to apply the patch. it's as simple as going to the firefox source folder and applying the patch file with:

patch -p1 < the.patch

and then proceed with ./mach build.

this was my first time building firefox from source and it wasn't half as bad; about 30ish minutes on an i7-870 in the background without any excessive load that woulda made the system unusable.

theguardian.com/us-news/2026/jul/23/cop-city-protester-phone

consumerrights.wiki/w/Common_Questions,Arguments,&_Responses_when_discussing_Flock_Surveillance

The U.S. government has charged Samuel Tunick with allegedly typing in a passcode to wipe his phone before officers could search it. “I hope people understand that the charges against me are meant to intimidate people,” he said.

Just another example of the Trump admin trying to intimidate protestors using whatever the fuck they can to bring up whatever charges they can.

**So this is how it went. **

2 month ago 'Flock No' wants cameras removed

1 month ago Flock cameras set to go dark June 29th

1 week ago Cleveland city council set to vote on Flock Safety camera contract renewal

Lemmy isnt ready for this project and so deleting the post

I hope this project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll ever be enough and so im still concerned it isnt ready to share. While im using AI throughout. This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

• Enkrypted.Chat

This is intended to demonstrate client-side managed secure cryptography.

• Introducing Enkrypted Chat
• Whitepaper (work-in-progress)
• Protocol Spec (work-in-progress)
• Roadmap

I know the project above is going to be tricky to understand. It might help to understand with an open-source version of the concept for educational purposes. Its's important to note, i have since deprecated it in favour of the version linked above.

Open source demo (deprecated)

PS. Im calling it a "Signal Messenger Clone"... that's just a matter of how to frame it for users getting started. It doesnt work in a way thats comparable to the signal architecture. This project is fairly complicated and the links above are likely not going to be enough, so feel free to reach out for clarity on the details.

PPS. I made a similar post on Reddit and it seems to be reasonably well recieved and so branching out to Lemmy here. It might help to take a look there if questions are asked/answered already.

Full article:

Claude is exposing a wealth of users’ chats and creations in Google search results, meaning anyone can dig through conversations or other material that people used Claude to make but may not have realized were publicly available for strangers to see.

The exposed data includes an AI-powered therapy app that someone appears to have vibe-coded, notes on meetings, and a dashboard someone made apparently to analyze medical billing data. Exposed chats reportedly include private cryptocurrency wallet keys and personal information like peoples’ addresses

Anthropic did not immediately respond to a request for comment.

Like other chatbots, Claude lets people share their conversations with others by creating a publicly accessible link of the chat. People may do this to send the full text of a conversation to their friends or coworkers in a group chat, for example. But they may not realize Google is also surfacing these links in search results, making them available to essentially anyone.

One Google dork — a super specific search that is useful for finding particular webpages or files — surfaced Claude chats, according to this post on the Claude subreddit. At the time of writing, that Google dork appears to have been mitigated. No results appeared when 404 Media tested it, on both Google and DuckDuckGo. The post said some of the surfaced chats included API keys, login credentials, and personal information like names, addresses, and phone numbers.

Claude also offers Artifacts, which are interactive work spaces for trying out vibe-coded apps or other tools. A Google dork for surfacing them is still working at the time of writing.

The data exposure is similar to one that impacted OpenAI’s ChatGPT last year, in which nearly 100,00 ChatGPT conversations were searchable on Google. A researcher was able to scrape those exposed chats, meaning that even if Google or Anthropic works to remove the Claude search results, third parties may have already grabbed their content. And it is still possible to view exposed chats even if they’re removed from Google results if you have the direct link itself.

Forbes reported the same thing happened with Claude last year too.

Claude users can change their privacy and sharing settings to make their chats no longer publicly accessible.

TL;DR: v1.4.2 is the latest stable release. Since v1.0, I've added P2P synchronization, ArchiveBox integration, and expanded platform support to Windows and BSD.

Release v1.4.2

GitHub: https://github.com/blob42/gosuki Documentation: https://gosuki.net/

Hi All,

It has been about a year since I posted the first version of GoSuki here. For those who missed it, I built this tool because I was tired of bookmark managers that require a cloud account or a browser extension that tracks every page I visit.

Since v1.0, the project has evolved from a simple aggregator into a more robust local-first data tool.

What has changed since v1.0 The core philosophy remains the same—no extensions, no cloud, no telemetry—but the implementation is significantly more capable:

• P2P Synchronization (Gosuki+): I implemented a real-time peer-to-peer sync mechanism. You can now synchronize bookmarks across multiple devices without a central server or a third-party provider.
• Archival Integration: I've integrated ArchiveBox support, allowing users to automatically trigger local snapshots of their bookmarks to prevent linkrot.
• Expanded Browser Support: Beyond the basics, GoSuki now supports Zen Browser, IceCat, Pale Moon, and Basilisk.
• Database Resilience: The storage layer has been hardened with schema versioning and automatic backups before migrations to ensure data integrity.

Highlights of the v1.4.x Series

The latest updates focus on platform accessibility and developer workflow:

• Windows and BSD Support: GoSuki is no longer Linux-only. It now builds for Windows (with a native systray icon) and Open/Net/Free-BSD.
• macOS: Available via homebrew Tap / Cask
• Decoupled Browser Definitions: Anyone can participate to add support for new browser by defining default paths in a simple YAML file.
• Enhanced CLI: The suki command now supports advanced search and sort syntax.

Upcoming feature: Local Reddit Archival

I am currently building a deeper archival system for the Reddit module that will keep a full local copy of all your liked/upvoted posts, including comment tree and media. Lemmy would be an easy update afterwards.

GoSuki remains open source under the AGPLv3 license. If you value data ownership and want a tool that treats your bookmarks as your own, I invite you to check out the latest release.

Reports that Madison Square Garden temporarily shut off its facial recognition system for Swift’s wedding expose a glaring problem with how the elite wield and control mass surveillance.

They gonna ram it in. They create the problem to solve the problem. Boy oh boy they getting creative on those camera tricks.... @1:49... constitution be damned... there is nothing good left in the USA... nothing but a zombie corporation ran by pdfiles. We are slaves no doubt about that. It is like us plebs get no chances but the corpos get infinite forgiveness.

Privacy.sexy builds privacy and hardening scripts for Windows, macOS and Linux. You pick the changes you want, read the exact commands and side effects, then copy or download the script and run it yourself. Nothing runs in the browser, no backend.

The original by undergroundwires hasn't had a commit since April 2025 and the OSes moved on. Windows shipped Recall and Click to Do, wmic is gone, half the registry paths point at nothing. I forked it and started fixing.

What's different:

• Updated the Windows catalog for the new AI features (Recall, Click to Do, Copilot).
• Removed tweaks I think were harmful, like ones that disabled browser updates or antivirus for a marginal privacy win. Gone or opt-in now.
• Deleted the Electron app. Shipping a stale Chromium to run a static page is a worse tradeoff than opening a browser.
• Fixed dead registry paths and stale commands across all three platforms.
• Added regression tests so a script that disables security-critical behavior fails CI.

One disclosure: I use AI assistance to write and research scripts, and review everything against vendor docs and the tests before merging. If you find a script that's wrong, that's the best bug report you can file and I'll fix it fast.

Independent fork, AGPL-3.0 like the original, not affiliated with undergroundwires. The architecture and most of the script library are their work.

By developer @turtlecute@feddit.it