[–] 2 points 6 days ago

Self hosted bit warden is rad I imported the DBs of all my Google account password managers and never looked back. Works great on my mobile device for passkeys/biometric also

  • source
  • [–] 15 points 2 weeks ago (2 children)

    Yep the only reason modern medicine went the antibiotic route instead of the bacteriophage route was the logistical and clinical challenges in stocking 100 treatments for an infection instead of 1 (or thousands instead of dozens) but now that we can print them on demand, you just have to show the AI an infectious agent or tumor cell and it can just crank out a custom virus that kills it specifically. Won't help with infectious prions or viruses but opens the door to new treatments for those too

  • source
  • parent
  • context
  • [–] 19 points 3 weeks ago

    It connects people with like minded people who also decided to show up so from a networking and community building perspective it's not worthless. Lots of people meet the contacts that will later recruit them to knock on doors or phone bank or run for office in the future who would never show up to a town meeting or city council meeting.

  • source
  • parent
  • context
  • [–] 5 points 3 weeks ago (6 children)

    All of this can be done on a graphics card from 3 generations ago locally though - it's like Photoshop you know, people can use Photoshop to make revenge porn but Photoshop isn't illegal, using it to make revenge porn is illegal.

  • source
  • parent
  • context
  • [–] 1 point 3 weeks ago

    In the case of HA, the agent is receiving ambiguous natural language requests and converting them into HA MCP calls. I can open the HA app and press buttons, sure, but the agent can reason over time about patterns of water/electricity use, provide natural language feedback, push back on my automation ideas with counterexamples from sensor logs - and all the sensors in the home and on the phones carrying the companion app are rich signal sources for an agent. It unlocks neat tricks like when our babysitter comes over the front door agent can alert her if there's a water leak and walk her through shutting off the water to the house or locate the backup key for her. It can DM me when someone rings the doorbell and carry on a different conversation with STT depending on if it is a person wearing a uniform or holding a clipboard for example thanks to Frigate and some custom vision ingestion with Qwen 3 VL.

    Regarding the torrents, that agent keeps track of my ratios on the private trackers and I can give it natural language feedback about what I did or didn't like about a show or movie and it will suggest alternatives, find them on a private tracker, download them, unpack them, and ingest them in the library for me, keeps track of the families like and dislikes and suggests media to watch together, watch private trackers for open invites or interview slots and take the knowledge interviews for me on IRC, deduplicate downloads and hunt for releases with minimum quality standards etc. one of my first tasks for it was replacing my music collection that got damaged when my external hard drive got dropped with no backup and I had to get it extracted in a clean room. Lots of rare lifetime accumulated mp3s gone - mostly recovered now. Searching for replacements would have been a long slog so I automated it.

    To your point some of these things could be done by deterministic python scripts and in fact the agents write those to save inference costs later and most of this stuff I could do by siting on my computer an clicking on stuff and reading - the point is that the agents constitute a natural language control surface to trigger all of those actions for me automatically so I can just send a couple chats to a discord bot and it will be done a few minutes later. I'm a busy person I dunno if you can relate. Busy career, got a family to support, parenting obligations, no time to hang out playing video games any more sadly. Building stuff takes time and effort and you have to learn and read about how to do it or pay someone else to do it for you so I was stuck on the easy convenience of windows and Netflix and Amazon/kindle etc. Not anymore! It started with having to install docker desktop to get OpenClaw working and then pretty fast I figured out pretty much everything I wanted to do now that was not work related is better done on Linux and better done self hosted. I would never have gotten over that hump without LLMs.

  • source
  • parent
  • context
  • [–] 2 points 3 weeks ago (2 children)

    So one thing that's really helpful to automate is checking all the repos for my self hosted stacks and testing/validating/deploying new versions when they come out. They're also good at writing helper scripts in Python to automate things deterministically so I don't have to keep using LLMs for it. There's an agent that is focused on learning and managing my wife's school schedule, ingests her grades and syllabi and reviews her homework and makes helpful 10 minute podcasts on concepts she's struggling with in her engineering program (not notebookLM, a self hosted lookalike), there's a domestic agent that accepts uploads of grocery receipts and does our meal planning and schedules time for meal prep and chores and divides it up between us and the kids depending on everyone's calendars, there's a home media agent that manages qbittorrent and my ratios on private torrent trackers and files new manga or TV shows or movies ebooks audiobooks etc in the right library when new things come out we might like, viewing/reading/watching metadata tells the agent what content is popular to queue up in the next sweep - there's a home assistant front door agent that can make automations or report sensor state or trigger scenes or entities in the general text channel of our home discord server and can tell me where my phone or keys are thanks to ESPresence being able to use cheap ATOM esp boards throughout the house (tiny little USB powered things with Bluetooth and wifi) to triangulate the location of any watched Bluetooth device or tracker tag in 3 dimensions through floors and walls - what else..there's a home security red-team agent that looks for security holes in my cloudflare tunnel/kv worker/tailscale/caddy/protonVPN routes and monitors a cyber security RSS feed, I have a job/market research bot that ingests another RSS feed for news relevant to my industry and organization and gives me email and voice briefings on new regulations and corporate leadership signals, stuff like that. What else.. there's a game dev bot where my kids can talk to a discord bot that routes to a game dev agent that has Godot MCP and Unity MCP and renpy MCP and lots of other fun tools like Roblox MCP and Minecraft to make custom games we can deploy on Google cloud for their friends to play (my daughter is really into visual novels for some reason I don't get it) - all sorts of fun stuff. Discord is kind of the family shared interface and then the privileged control planes are routed to my phone through tailscale and the home media server stacks are exposed through cloudflared.

  • source
  • parent
  • context
  • [–] 6 points 3 weeks ago (5 children)

    Yes, with OpenClaw I can expose my agents via discord apps on my home discord server, I like that route because of the rich media and UI options (agents can give me drop down selector lists and approve/reject buttons). I have two 24gb Nvidia cards for local models usually Qwen, Mistral, and nemo based models for different purposes. I can chat with the agents anywhere I'm logged into discord and I expose privileged control surfaces and nodes via tailscale and family/shared endpoints via caddy and cloudflared

  • source
  •  

    I’m trying to recover many years of Google Maps Timeline history and have gotten far enough into the problem that I’m hoping someone familiar with Android Keystore, Google Play Services/Folsom security domains, or Maps Timeline’s encrypted-backup implementation might recognize what is happening.

    The short version is:

    Google confirms that encrypted Timeline backups for my account still exist on its servers, but every device I try says “Your encrypted data isn’t unlocked yet.” On the S23 that was probably involved in the Timeline migration, an Android bugreport shows Google Play Services actually attempting key recovery and failing with:

    LocationHistory: [BackupRunner] Failed to get encryption key for backup

    LocationHistory: bmas: 38502: Domain is not retrievable

    The recovery flow also invokes:

    com.google.android.gms.auth.folsom.StartKeyRetrieval

    and references:

    on_device_location_history

    How I think I got here

    I have used Google Maps Timeline/Location History for many years.

    For most of that time my primary Google account on Android devices was one account, while the account I actually used inside Google Maps for Timeline was a different secondary Google account. That worked normally for years.

    My main phone during the transition from Google's old server-based Timeline system to the newer device-local/encrypted-backup system was a Samsung Galaxy S23 Ultra, SM-S918U1.

    At some point I had to repair/reflash the S23 firmware. I believe I used firmware that was compatible with the hardware but may not initially have been the exact correct region/CSC variant. The phone continued working afterward.

    I cannot prove that this caused the Timeline problem. It is simply the most suspicious event in the history because Android Keystore/device trust material may have changed during that process.

    Later I noticed that older Timeline history was gone from the normal Maps UI.

    What Google Takeout shows

    I requested a Google Takeout specifically for Timeline.

    The plaintext Timeline export only contains relatively recent device-local history.

    However, Takeout also produced an Encrypted Backups file that explicitly states that I have encrypted Timeline backups stored on Google servers.

    So as far as I can determine:

    Old Timeline data

        ↓
    

    encrypted backup still exists at Google

        ↓
    

    decryption/recovery state is unavailable

        ↓
    

    Maps cannot restore it

    Importantly, the Takeout file is not the encrypted backup itself. It just confirms that encrypted backups exist.

    What Maps does

    On the S23, my new Galaxy Fold, and several old Android devices, Maps shows:

    Your encrypted data isn’t unlocked yet

    If I tap the Timeline cloud/backup icon:

    A spinner appears.

    It waits for a while.

    The spinner disappears.

    No backup list appears.

    I never receive a PIN/password/key-recovery prompt.

    I never get a usable “Fix now” flow.

    I have tested:

    Galaxy S23 Ultra

    Galaxy Z Fold8 Ultra

    Galaxy Note8

    Galaxy Tab A

    The older devices were preserved and had not necessarily been wiped, but signing the Timeline Google account into them does not change the behavior.

    This suggests that simply having an old device is not enough. The specific device-side recovery/security-domain state apparently matters.

    What I found on the S23

    I kept the S23 intact after moving to the Fold and captured an Android bugreport while reproducing the Timeline failure.

    The critical log entries are:

    LocationHistory: [BackupRunner] Failed to get encryption key for backup

    LocationHistory: bmas: 38502: Domain is not retrievable

    The bugreport also shows the Google Play Services key-recovery path actually launching:

    com.google.android.gms.auth.folsom.StartKeyRetrieval

    The recovery request is associated with the correct Google account and:

    on_device_location_history

    There are also Google Play Services/Keystore references such as:

    com.google.android.gms.auth.folsom

    com.google.android.gms.backup/folsom

    security_domain_member_key

    security_domain_member_key_encrypted_locally

    and activity involving operations with names along the lines of:

    ListSecurityDomainMembersOperation

    GetKeyMaterialOperation

    MarkLocalKeysAsStaleOperation

    INVALIDATE_LOCAL_KEYS

    I am not interpreting those names as proof that Google deleted the keys. They are simply what appears in the recovery sequence.

    Current S23 state

    The phone currently reports:

    Model: SM-S918U1

    Android: 16

    Bootloader: locked

    Verified Boot: green

    Warranty bit: 0

    Security patch: 2026-08-05

    Sales code: XAA

    So there is no obvious current unlocked-bootloader/failed-Verified-Boot situation.

    The Keystore is also clearly functioning in general. Google Play Services can create/use hardware-backed operations. The unresolved question is whether the specific historical Timeline/security-domain key material is gone, stale, inaccessible, or simply failing to be retrieved from Google's recovery infrastructure.

    Things I have deliberately NOT done

    I have not:

    deleted the encrypted Timeline backups

    selected Google's “delete encrypted data and start over” option

    factory-reset the S23 during this investigation

    cleared Google Play Services storage

    cleared Maps storage

    unlocked the bootloader

    removed the affected Google account

    reflashed the phone again

    I want to preserve every remaining recovery possibility.

    Things I've already tried

    Tested the original/current S23

    Tested a new Fold

    Tested old Note8 and Tab A devices

    Verified the correct Google account is being used

    Verified normal Google authentication works

    Confirmed the encrypted backups exist via Takeout

    Captured ADB/logcat/Android bugreport during failure

    Submitted the exact error through Google Maps feedback

    Posted to the official Google Maps support community

    The normal Google support documentation basically says to recover encrypted Timeline data using the original device, or delete the encrypted backup and start over if recovery is impossible.

    The problem is that I still have the likely original device, and its recovery process is actively running but failing internally.

    What I'm trying to figure out

    Does anyone recognize:

    38502: Domain is not retrievable

    from Google Play Services, Folsom, security-domain recovery, Android backup encryption, or Maps Timeline?

    In particular, I’m trying to determine whether this means:

    The historical device-bound encryption key was permanently lost during the earlier firmware event.

    The local Google security-domain membership/key wrapping state is damaged but potentially repairable.

    Google still has enough recovery metadata server-side, but the security domain is in a broken/stale state.

    This is a Google Play Services/Maps bug rather than true key loss.

    There is some supported or unsupported way to re-enroll the device into the existing security domain without deleting the encrypted backups.

    I am comfortable with ADB, Android debugging, Linux, Docker, firmware tooling, and doing forensic-style diagnostics on the S23 now that it is no longer my daily phone.

    I am not looking to bypass someone else's encryption or account security. These are my own Google account, phone, and Timeline backups. I’m mainly trying to avoid destroying the one server-side copy that apparently still exists.

    If anyone has dealt with Google Play Services auth.folsom, Android security domains, or Timeline's newer end-to-end encrypted backup implementation, I would especially appreciate pointers about what 38502 / Domain is not retrievable actually signifies and what additional state I should preserve before experimenting further.

    view more: next ›