1. Increasingly it feels like I do my best work in the dead of the night. Maybe a nocturnal lifestyle isn't all that bad...

  2. @tkuenneth@snapp.social It does feel a bit overbearing but the alternative is the undocumented app killing behavior other OEM skins implemented for improved battery mileage. I'd rather these come from Google and be consistently enforced than it be a Samsung and OnePlus problem I have to debug anew every year.

  3. Content warning: google / doxing / dangerous policy update

    @SylvieLorxu @riderexmachina When has Google been good with words 😬

  4. Content warning: google / doxing / dangerous policy update

    @SylvieLorxu @riderexmachina They're right, the address and phone number bits are specifically for business accounts and not individuals.

  5. @Gankra I think it's part column A, part column B. My knowledge here is quite superficial, but if you try to call source with a shell with stdlib APIs, wouldn't it run in a subshell and not update the active session of the user?

  6. Kinda wanna replace my little bag of Bash scripts for managing Claw with something more dependable, but the only thing that comes to mind is Python...

  7. @cadey Is it bad if I'm mildly impressed by the fact that there is a pretty decent plot among the unhinged madness

  8. Taking app screenshots and keeping them up-to-date is such a chore 😭 #AndroidDev

  9. Finally giving #Firefox another shot in lieu of the Chrome Web Integrity proposal and I'm genuinely quite impressed with how much _nicer_ everything feels now. I used to have gripes about the UI but it's all completely gone and the migration worked flawlessly as well.

    I think I might just stay this time round :)

  10. I've been hacking on a #Kotlin compiler plugin for the past day and it's been the most frustratingly challenging project I've picked up in a while. I'll be quite proud of myself if I can get an MVP out next week.

  11. @SylvieLorxu echoing other replies, I've also found Immich to be a great option as of late. It's no Google Photos but catching up quite quickly.

  12. Somehow managed to hit the jackpot of pain, doing release automation for *Flutter* packages

  13. Back in Bangalore for a bit, let's see how much socialization I can cram into this week without making myself miserable

  14. @stacy reading this as I'm scratching my head at d.android.com because the docs seem to be gaslighting me :android:

    Replying to source post

  15. @gonsalves These are getting pretty good!

  16. @seanmonstar @hyper_rs In the release notes, the part which reads "Any IO transport type provided must not implement `hyper::rt::{Read, Write}`" is probably supposed to be "must *now* implement" instead?

  17. @nileane This looks incredible, great job!

  18. @p @jhpratt another vouch for git-absorb, it's the tool I use every day for PR/patch stack workflows and have no complaints.

  19. @gp5 I found Google's own docs pretty decent for getting a quick leg up on fundamentals and building up a mapping of Views -> Composables for everyday stuff. The NowInAndroid sample is also quite excellent for finding examples of more involved topics.

    developer.android.com/jetpack/

  20. @malwaretech that "OWNED!" at the end is absolutely sending me

  21. @taco Sorry for the "well, ackshually"! I figured you were aware but I've seen the same thing repeated sincerely a bit too often each time a remote shell vulnerability is disclosed 😬

  22. @taco Similar vulnerabilities with other software have been used by good samaritans to patch machines but more often than not it only increases the work for the owners of said machines. They now have to do a more thorough analysis since the patch could very well have been done by a malicious actor after they've exfiltrated what they needed.

  23. @taco Welcome! :androidWave:

  24. @QuietMisdreavus Absolutely not, the couch makes for an incredible background. The plain white wall behind me is seething with jealousy.

  25. Dear Windows,

    When I open the settings app of my desktop OS, I should not see a "Rewards" button.

    Signed,
    A tired user

  26. Content warning: threads [derogatory]

    @0xabad1dea I feel the QR code scanner used might be a relevant metric. I can scan it fine with the Google App's QR scanner on Android.

    Though in a slightly funny turn of events if I try to open the link scanned from the QR code it triggers a deeplink to the Threads app which promptly crashes.

  27. I've often worked with tech I didn't personally enjoy for my day job but this is the first time it has absolutely destroyed my productivity. NodeJS and microservices are too far out of my wheelhouse for me to feel comfortable or useful. Here's to hoping I can muster enough strength to close out my current projects and return to mobile tooling.

  28. @b0rk I've exclusively used sd for nearly 2 years now and have never needed to fall back to sed.

  29. I hate that `rm -rf node_modules` is still a completely expected debugging step for #nodejs. It's been literally years since I've had to do anything similar even with Gradle.

  30. Content warning: cw

    @SwiftOnSecurity Did not expect to see a Bukkit cosplay on Mastodon