Admiral Patrick

I’m surprisingly level-headed for being a walking knot of anxiety.

Ask me anything.

I also develop Tesseract UI for Lemmy/Sublinks

Avatar by @SatyrSack@feddit.org

  • 4 Posts
  • 129 Comments
Joined 2 years ago
cake
Cake day: June 6th, 2023

help-circle


  • Admiral Patrick@dubvee.orgtoAndroid@lemdro.idJust look at Huawei’s trifold phone
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    1
    ·
    edit-2
    12 days ago

    Remember “phablets”; almost all smartphones eventually turned into phablets.

    Which is, arguably, for the worse. I miss smaller 16:9 devices I could use one-handed and reach all the corners of. Almost cried when I had to give up my OnePlus 3 and everything now is an unwieldy, tall-skinny rectangle.

    I’ve not had a hands-on experience with foldables yet, but the reviews I’ve read imply they still seem too fragile for the price.




  • I’d considered the Razr but was uncertain on the durability of it. Reviews were about 50/50 last I read.

    That’s awesome you mentioned using it closed most of the time. I’m tired of the “tall, skinny rectangle” form factor (and not being able to use it one-handed despite having not-small hands lol). Since smaller phones seem to be extinct, it’s cool there’s a middle ground in being able to use it that way.

    I do need to make sure I can find one that’s bootloader unlockable. Kind of a hard requirement for me and necessary to de-google it to my satisfaction. It’s not listed as supported by Lineage, but I’ll browse XDA and see what they’ve been able to do with it.

    Thanks!



  • Is there a way I can get Let’s Encrypt to dole out a wildcard certificate

    Yep. Just specify the domains yourdomain.com and *.yourdomain.com in the certbot request. Wildcard domains require the DNS-based challenge, but you’ve said you’re already good there. You don’t technically need the apex domain (yourdomain.com) but I always add it since I do have services running there.

    Any subdomains under the wildcard can use internal DNS or internal IPs on the public DNS (I do the former, but the latter works too).

    I used to run an internal CA, and it wasn’t too hard to setup a CA and distribute my root cert. Except on mobile devices. On Android it was easy, but there was a persistent warning that my network traffic could be intercepted (which is true when there’s a custom root cert installed), but it since it was my cert, it got annoying seeing that all the time. Not sure if Apple devices can even do that, but regardless, it wasn’t practical for friends who wanted to use my self-hosted services to install a custom cert when they were over.








  • Depends on what I’m transferring and to/from where:

    • scp is my go-to since I’m a Linux household and have SSH keys setup and LDAP SSO as a fallback
    • sshfs if I’m too lazy to connect via SMB/NFS (or I don’t feel like installing the tools for them) or I’m traversing a WAN
    • rsync for bulk transfer and backups
    • Snapdrop/Pairdrop for one-off file/text shares between devices with GUIs (mostly phone <–> PC)
    • SMB if I’m on a client PC and need to work with the files directly from the fileserver
    • NFS between servers
    • To get bulk data to my phone (e.g. updating my music library), I connect via USB in MTP mode and copy from the server via SMB or sshfs.

  • I’ve always thought the firewall color codes were arbitrary, though I might just have not paid attention all these years lol.

    Just to clarify: I meant connect your OpenWRT device to your hotspot instead of the AP you’ve been working with. Just to rule out multiple MACs being blocked on the AP.

    Beyond that, I’m not really able to help troubleshoot further, but worst case and if all you need is internet, you can set your OpenWRT device up so that it just NATs your downstream connections. Double-NAT, in most cases, is fine.



  • I did that with a GL.iNet travel router after flashing stock OpenWRT, and used it as a wireless bridge for several years. It uses relayd to bridge the Wifi station interface and Ethernet. Once you have an ethernet bridge, you can connect another AP or do whatever from there.

    If you create a second wifi interface in AP mode (in addition to the station/client one connected to the upstream), you should be able to add that to the LAN bridge alongside the ethernet interfaces. That bridge will then be part of the relayd bridge, and it all should just work (should, lol. I haven’t tested that config since I only needed to turn wifi into wired ethernet with this setup).

    Interfaces:

    LAN Bridge: Ethernet interfaces to be bridged to the wifi

    I have both of its interfaces in this bridge, and it also has a static management IP (outside of the WLAN subnet). This management IP is a static out-of-band IP since the devices connected over ethernet won’t be able to access it’s WLAN IP (in the main LAN) to manage it. To access this IP, I just statically set an additional IP on one of the downstream ethernet client devices.

    The LAN bridge is in a firewall zone called LAN.

    WWAN: Wireless station interface that’s configured as a client to the AP providing upstream access. I have this configured statically, but DHCP is fine too. Firewall zone is WLAN.

    WLANBRIDGE: The relayd bridge (Protocol: relay bridge). It’s interfaces are the LAN bridge and the WWAN interface.

    Disregard the WGMesh parts; that’s separate and not related to the wireless bridging mode.


  • Look at RCS

    I’d rather not lol. Google basically forces you to use your phone in a Google-approved configuration or RCS silently fails. So if you’re rooted, no RCS for you. You can spoof SafetyNet attestation all you want, but they constantly blacklist fingerprints (even legit ones) and RCS stops working (but still says “connected”). After 3 months of fighting it, missing messages, or having to wait 90+ seconds for outgoing messages to fallback to SMS, I just disabled RCS and went back to SMS/MMS. Since that was the last Google service I was trying to use, I just disabled Play Services and completed the de-googling of my devices.

    If RCS is to ever succeed, , it needs to be a carrier service and not a Google service. As it is now, it is impossible to use RCS on Android without Google Play Services (e.g. De-Googled device). That’s absolutely unacceptable.


  • Honestly, I dread the e-SIM only future. They’re okay as something that complements a physical SIM, but I much prefer swapping the physical one than going through the carrier to transfer it.

    I tend to use devices and mobile OS’s that aren’t carrier-blessed (but are otherwise compatible with the network); it’s often necessary to first activate the service in a “supported” device and then move the SIM to the device I actually want to use.

    I also change devices often, kind of like choosing the right footwear for the event. I’ve got a general purpose “daily driver” mostly dumb phone, but I also swap my SIM to a few other devices depending on need. e.g. occasionally, I’ll need my actual smartphone and move my SIM into that for the day or I’m going backpacking and move my SIM into my rugged smartphone which is otherwise a beast to carry but nice in the wilderness, etc.

    Plus, I’ve had phones just up and die. With my cell as my only phone (and sometimes only internet connection), it’s a little difficult to reach the carrier to move service to my backup device. Much easier to just pull my SIM and move it.

    If I were doing all this with eSIMs, I’d probably be setting off all kinds of false alarm bells swapping around so much; all false alarms that, to date, haven’t been an issue with a physical SIM. That’s not even getting into the artificial restrictions that will eventually come. Wouldn’t put it past some shitty carriers (cough Verizon cough) to limit the number of times you can swap in a month and/or to charge a BS “activation” fee for it.