

Yeah, unfortunately it’s closed-source. It’s a good app though! If you build something similar that’s fully open source, with an Android app and Android Auto support, then I’d definitely be interested in trying it.
Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @dan@d.sb
Yeah, unfortunately it’s closed-source. It’s a good app though! If you build something similar that’s fully open source, with an Android app and Android Auto support, then I’d definitely be interested in trying it.
Have you tried Plexamp? It supports all the features in your list. You need a Plex Pass for most of its features though.
I’m not mentioning it to suggest your project is bad or to discourage you; I’m mentioning it since it might give you some inspiration for features to implement in your one :)
Bitwarden and Vaultwarden are different products. Vaultwarden is API-compatible with the Bitwarden client apps, but it’s a completely separate project.
Both are self hostable. Bitwarden is designed for large deployments (like companies with tens of thousands of employees) so the design is very different to Vaultwarden which is designed for small deployments.
I used to self-host Bitwarden but switched to Vaultwarden a while back.
In the Bitwarden Android app, make sure all the autofill settings are enabled, including accessibility (which helps with autofill in apps that don’t officially support it). Sometimes, system updates seem to disable them.
Also note that Android apps need to explicitly support autofill. Not all apps do. The “use accessibility” option is supposed to help with apps that don’t officially support autofill.
I think they’re pretty different cases.
Amazon’s one was essentially a side project for them, likely fully funded in-house using their R&D (research and development) budget.
In Nate’s case, it was their entire product. They received funding from investors purely for the AI functionality that didn’t actually exist or work. They specifically claimed that it did work, which is how they got the money. They spent all the investor money and had essentially nothing to show for it.
At least there’s some competitors now, which could be used as drop-in replacements if Let’s Encrypt were to disappear.
I suspect the vast majority of certificate authorities will implement the ACME protocol eventually, since the industry as a whole is moving towards certificates with shorter expiry times, meaning that automation will essentially be mandatory unless you like manually updating certs every 90-180 days.
They already factored in some amount of tariffs into the US price. It’s not really that it’s cheaper in Japan, but rather it’s more expensive in the USA. It’s also US$65 cheaper in Australia, for example, and even cheaper in the UK.
(keep in mind that advertised prices in Australia and the UK include tax, so you need to subtract the tax to compare with US prices)
The tariffs are just a lot higher than everyone expected. Nintendo were probably preparing for a 20% tariff, not a 54% one.
Maybe! I’m sure there’s loopholes of some sort.
This is a rare case where a piece of consumer electronics is going to be quite a bit cheaper in Australia compared to the USA! Usually stuff costs more in Australia.
The Switch is currently US$450 and will probably go up with tariffs. Meanwhile, it’s listed as AU$700 in Australia, which is AU$630 before tax (all advertised prices include tax), which is US$385.
I imagine this is going to happen for a lot of devices. I’m an Aussie living in the USA and I never thought I’d see the day when buying stuff in Australia would be cheaper. Australia has better consumer protection too, around things like repairs/refunds due to major issues even outside the warranty period.
Do you not like reading the truth?
Absolutely. The console is manufactured in Vietnam, which now has a 46% tariff. I really doubt that Nintendo’s profit margin is high enough to allow them to just eat that cost.
There’s no reason your media server needs to be directly exposed to the public internet. Use Tailscale. Get everyone that uses it to sign up for a Tailscale account, and add them all to your Tailnet.
Tailscale will perform better than a Cloudflare tunnel because it’s a direct connection between the two peers, whereas Cloudflare tunnels route through Cloudflare.
Tailscale does have relay servers, but they’re only used in very rare cases, if both peers have very strict firewalls. Almost always, the connection between two peers over Tailscale is a direct connection, so there’s no extra latency (other than some small overhead for the encryption)
You could use Wireguard and manually configure it to be in a mesh config, but Tailscale makes it so much easier. I’m a big fan of their product.
I loved the explosion sound, and the “oh no” when you click the undo button. I have the Windows versions of KidPix on CD somewhere.
I don’t see any mention of torrents in the article?
Oh yeah, there’ll be some overhead if you’re running Wireguard on a router. Hitting your router’s public IP won’t go out to the internet though - the router will recognize that it’s its IP.
It’s common to run Wireguard on every computer/phone/tablet/etc where possible rather than just on the router, since this takes advantage of its peer-to-peer nature. For home use, that’s how it was originally designed to be used. Tailscale makes it a lot easier to configure it this way though - it’s a bit of work for vanilla Wireguard. Tailscale does support “subnet routers” if you have any devices that you want to access over the VPN that can’t run Tailscale.
My point is that since the VPN uses a different subnet, it’s fine to keep it connected even at home. It’ll only use the VPN if you access the server’s VPN IP, not its regular IP.
In any case, Tailscale and Wireguard are peer-to-peer, so the connection over the VPN is still directly to the server and there’s no real disadvantage of using the VPN IP on your local network.
Yeah, this. Plus if you leave it connected, you can use the VPN IPs while at home instead of having to use a different IP when at home vs when out (or deal with split horizon DNS)
Headscale is a replacement for the coordination servers, which are only used to distribute configs and help nodes find each other. It won’t change client-side behaviour.
I did this and it still seems to randomly disconnect.
It was missing a bunch of features last time I tried it - no crossfades, no automatic playlists (for things like liked songs, decades, etc), no artist radio (play an artist plus similar artists), no way to play sonically similar songs (based on server-side analysis), no loudness leveling, no Android Auto. Maybe it’s improved now - I’ll have to give it another shot.
Unfortunately I’m not sure I know enough about audio processing and similarity analysis to be able to implement those features myself.