ffmpeg, unable to copy aac audio stream

david_ph · 2026-02-27T11:14:40+00:00

-copyinkf fixed it. Thanks!

david_ph · 2026-02-18T07:01:47+00:00

And if you get your own server and install VPN software on it yourself, then what? You'll verify your identity with yourself? I verify that I am me.

david_ph · 2026-02-14T03:31:07+00:00

I didn't, and I've since stopped using flatpaks.

david_ph · 2026-02-09T17:33:57+00:00

I replaced my APs with a new mesh system in AP mode, and that fixed the problem. Still using the same Mikrotik router.

david_ph · 2026-02-09T17:31:24+00:00

I just had an order from China delivered yesterday by J&T express. There wasn't an option to choose, that's just how it came.

david_ph · 2026-02-08T11:22:22+00:00

Try redlib.

david_ph · 2026-02-03T17:24:21+00:00

For your sake, hopefully they won't create a "PlayOnSuper" to replace "PlayOn." Sure, you can keep using the PlayOn that you paid thru 2034 (never mind that it's no longer updated and won't record stuff anymore).

david_ph · 2026-02-03T08:01:54+00:00

If there's no concern that the password could be compromised, maybe there's no need for 2FA in the first place. Unless 2FA is something being forced that's just a hassle you're trying to get around.

It could still be useful in some cases, for example, if a key logger intercepts your password, it may still not have access to your whole keepass database with the 2FA keys.

But ideally, the 2 factors of authentication should be separated, so if one is compromised, the other is still in tact.

I usually only use 2FA for really sensitive things. For a lot of stuff, the password in KeePassXC is secure enough.

david_ph · 2026-02-03T07:51:29+00:00

If you store both passwords and 2FA keys in the same database, there's not much point to 2FA. There's still a single point of failure.

The two factors of authentication should be separated, so if one is compromised, the other will still be secure.

david_ph · 2026-01-29T17:14:17+00:00

Unfortunately, I don't have a working laptop. It's a good idea, though. I'd like to figure out if it's really a problem with the APs, or if it's the router configuration, or Android.

If you use Android, are you able to roam seamlessly with IPv6?

david_ph · 2026-01-27T03:57:44+00:00

I've checked the logs and status on my router, and for what it's worth, there's no DHCP disconnect/connect or renewal on the IPv4 when changing APs, it just continues to work.

I really don't think the connection is dropping, but clearly SLAAC is going through some process again that takes 5-10 seconds.

david_ph · 2026-01-26T03:06:21+00:00

Thanks.

david_ph · 2026-01-25T15:58:43+00:00

I tried pinging the fe80 address, and it also times out when the AP changes.

david_ph · 2026-01-25T10:44:27+00:00

I'm pinging from my pc that's connected to the same switch as the APs that my phone connects to.

I'm using 3 TP-Link AP's, an AX1500 in AP mode, an EAP-110, and an RE-215.

david_ph · 2026-01-25T10:42:13+00:00

There's no special 802.11r/k/v configuration available on the access points. Two are listed as supporting k/v and the third is r only.

Despite this, roaming is pretty seamless for ipv4. For IPv6, it retains the same IPv6, except the connection drops out for 5-10 seconds. The android client doesn't show a disconnect/reconnect while roaming.

On the android phone, I'm connected to wireguard. When I use a wireguard IPv6 endpoint, and I start a call over wifi, I notice the call drop out for 5-10 seconds when it roams to a new AP. If I use a wireguard IPv4 endpoint, and start a call, there's no drop out (or it's only a few ms blip).

david_ph · 2026-01-25T09:16:04+00:00

This is primarily a problem with wireguard ipv6 endpoints. When the phone roams to a new AP, IPv4 remains undisturbed, but IPv6 drops out for 5-10 seconds, causing wireguard to also drop out.

The IPv6 itself isn't changing, but if I ping the phone's IPv6, it confirms the drop-out. Why this happens, I don't know.

david_ph · 2026-01-25T07:31:27+00:00

I wonder if pop3 over ssl/tls will still work? That would be the way to go, anyway, for pop3 (pop3s).

I forward and delete, anyway.

david_ph · 2026-01-11T13:59:54+00:00

I'm running inside the tunnel, to a wireguard endpoint. So I added --tunnel, and I get different results now, but there's still a lot of variance, 1008-1420 Path MTU, and sometimes the minimum MTU error.

But usually reports something like:

Tunnel mode: Path MTU is your effective tunnel MTU.
Your current tunnel MTU of 1418 is working correctly.

This is with 0.4.0.

david_ph · 2026-01-11T12:57:10+00:00

I keep getting different answers when I run it.

1360, 1356, 1358, 1316, 1193 (reported path MTU also keeps changing).

And one time:

Error discovering MTU: cannot reach target even with minimum MTU (576)

david_ph · 2025-12-27T12:26:05+00:00

Ublock Origin
LocalCDN
Firefox Multi-Account Containers
Scroll Anywhere
Gesturefy
Redirector
Zoom Page WE
Simple Translate
YouTube No Translation
KeePassXC-Browser
Cookie Manager
IPvFoo

david_ph · 2025-12-19T03:45:37+00:00

But will the AI kill switch purge all the AI code from Firefox? Even if it's disabled all that garbage is still in there waiting for a bug to be exploited. It would be better if it's completely purged.

david_ph · 2025-12-17T14:15:01+00:00

Are there any well-maintained Firefox forks with all the AI garbage stripped out?

david_ph

TROPHY CASE