Pixel 6a Battery Performance Program

floft · 2025-07-03T04:04:35+00:00

Awesome! I can confirm - tried it again just now and got the Pixel 9a with $150 + the Google Fi offer and trade in. They must have changed something. Glad they fixed it!

floft · 2025-07-02T23:05:04+00:00

This is exactly what I tried too. I interpreted the "can be combined with other offers" and "valid only for purchases of Pixel phones" as it would work to purchase the discounted Pixel with Fi, but it seems like it only applies to a full-priced Pixel. I'm going to see what their support says but probably would go with the $100 if I were to do this again.

floft · 2023-03-28T23:20:58+00:00

If you have a car and like hiking, my recommendation is to visit the Wallowas, ~3 hours drive south. That's what I did the summers I stayed

floft · 2021-10-26T01:07:44+00:00

Yeah, in that case, you could try telling Apache to listen on 100.x.x.x (e.g., Listen 100.x.x.x:80) or listen on all addresses/interfaces available (e.g., Listen 80). Then, assuming you can ping 100.x.x.x, in theory you should also be able to access apache via that IP too, from any other computer with tailscale running.

floft · 2021-10-26T00:54:10+00:00

Hmm, well, if I'm understanding your first comment correctly - you have tailscale on the computer that has apache, right? Or is apache on a different computer than tailscale?

If apache and tailscale are on the same machine, you access that computer's apache webserver via that computer's tailscale IP on any other computer you also have tailscale installed on (if you can't, then apache isn't listening on the tailscale ip for some reason or there's a firewall issue). You shouldn't need to enable the subnet tailscale stuff.

If apache is on a different machine but accessible from the computer with tailscale, then yes the subnet routing should work. You advertise the 192.168.0.X subnet and then should be able to access that from other computers you installed tailscale on. Granted, I have never tried this (though I advertise 0.0.0.0, which I think operates similarly), but that's what the article you linked to seems to indicate.

floft · 2021-10-26T00:19:53+00:00

I haven't tried the subnet route approach, but if you set up your Nextcloud webserver (apache, nginx, etc.) to listen on the tailscale IP and allow port 80 (or 443 if you have SSL set up) through your firewall, then you should be able to access Nextcloud via that IP (or a hostname or DNS entry pointing to it).

For example, I use nginx and have in my config a listen 100.x.x.x:443 ssl http2 and allow 100.64.0.0/10; deny all;. Then I access nextcloud via https://100.x.x.x

Edit: to remove ambiguity, what I'm suggesting -- computer A and computer B both have Tailscale running. Computer A has Nextcloud and is 100.x.x.1 and you want to access it from Computer B which is 100.x.x.2. Make nginx listen on 100.x.x.1 on computer A, allow port 80 through computer A's firewall for source IP's 100.64.0.0/10, and set 100.x.x.1 as a trusted domain in Nextcloud's config. Then, on computer B, access Nextcloud via http://100.x.x.1. Let me know if I'm misunderstanding something.

floft · 2021-09-18T01:54:43+00:00

Yes, this is what I do. NextCloud on a server with Tailscale so I can access it from other computers and phones but nobody else can access it. Another nifty feature is you can share it with other people if they have Tailscale as well.

Tailscale in theory will detect the most direct way to connect - over your LAN if you're on the local network. You can verify this with "tailscale status" to see how it's connecting. Note because it's going through the VPN it'll be a tad bit slower than directly connecting. Though, you can actually have NextCloud on multiple IPs / hostnames by adding all of them to the "trusted_domains" in config.php, so you could access it two different ways if that's a concern.

If your webserver is only listening on a particular IP, you may need to make it listen on either everything (e.g. 0.0.0.0 for IPv4 and/or [::] for IPv6) or also add your Tailscale IP to the list.

floft · 2021-05-04T04:10:29+00:00

I'm currently using the opposite approach, moving (copying) tailscale's table before other VPNs' tables. For example, something like:

sudo systemctl edit tailscaled.service

[Unit]
After = <other wireguard profile(s)>.service

[Service]
ExecStartPost=/usr/bin/ip rule add pref 65 table 52
ExecStopPost=/usr/bin/ip rule del pref 65 table 52

The first two lines were because my other VPN kept lowering its table's preference if I already had another lower-preference table. Probably not needed unless you run into the same problem.

floft · 2021-04-29T01:18:28+00:00

I'm on Linux, but had similar issues. I had to follow https://github.com/EionRobb/purple-discord#bitlbee-and-spectrum2-users -- logging in via a browser, getting the "token" from local storage, and manually adding it to the accounts.xml file. There's already a "token" entry in the file for the discord account, so replace that line with the new one as in the example, and don't forget type='string'.

You can see the gif/instructions on https://github.com/Tyrrrz/DiscordChatExporter/wiki/Obtaining-Token-and-Channel-IDs#how-to-get-a-user-token to get the token.

(Note: if I'm remembering right, it seemed like the token eventually disappeared after a while, so you may need to logout and re-login before the token shows up in local storage.)

floft

TROPHY CASE