Skip Navigation

Posts
0
Comments
107
Joined
2 yr. ago

  • I have owned the Light Phone 1 and the Light Phone 2 -- both were built with the intent to stay connected in a handful of ways without needing to have a full-spec'd, app-heavy, typically-sized smart phone.

    If the intent and the vibe make sense to you, then it is a wonderful approach for a more 'minimalist' device: you can go outdoors, travel, hike, camp, etc., without having a smart phone to pick up and play with. I dig it.

    If the intent and vibe don't make sense to you, the Light Phone may not be a good fit.

    I really like the device, and use it often enough as a daily driver on weekends. Always glad to see some public attention on it.

  • I have looked around, myself, but not found a FOSS alternative. There are typically compliance issues like PCI DSS for certain banks that prevent trust and cooperation from those banks outside a larger entity like Google, Apple, etc.

    Aside smart phones, Flipper Zero can clone some cards sucessfully. But that's an entirely different device, not an app for a phone. Best of luck!

  • CATSPAWs

  • A chemical compound causes the cloth to turn blue when polishing an iPhone, green when polishing an Android. It's only a subtle difference.

  • NC Password works well, but does require the server to be up -- that can be a painpoint. Keeping an encrypted CSV/spreadsheet backup of your passwords for offline use is one option. Another option might be to see if this Linux Desktop Nextcloud app is still functional: https://gitlab.com/j0chn/nextcloud_password_client

  • As a feature request, this might require some client-side processing. I have seen similar asks in other communities, though.

    A interesting UX to test this, if it were possible, mkght could be something like:

    [Post title]

    [All Lemmy instances/communities to which a user has subscribed that this post exists.]

    [Post content]

    Etc.

    While this may not be an easy implementation, it would interesting to test on Jerboa.

  • Duskers looks fantastic. Thanks for sharing the link!

  • I suspect it may be a bit more along how you're describing here -- we expect some user experience patterns to already be in place, if not considered, like not being able to select inappropriate handles. Former Twitter folks should know 'better.' From the outside looking in, it tracks.

    I wonder if the Bluesky team, right now at least, is more engineer / dev heavy, and they have not brought on UX folks to help drive a product design that considers patterns we'd be used to experiencing. They may be operating pretty lean.

    An idea, at least.