It’s “many” like in “Many people on twitter are saying…” i.e. they found 3 or 4 people saying crazy shit and acted like it was a big thing.

Its just unreasonable to expect spotify to be able to afford that when they already barely pay musicians.

The audiobooks help them pay even less for music:

With the introduction of the stand-alone audiobooks offering, Spotify is now able to pay lower music-licensing rates for the music-and-audiobook bundle, introduced in the U.S. in November 2023. The 2022 settlement agreement between the National Music Publishers Assn. and streaming services includes a carveout for bundles (such as Amazon Prime and Apple Music + Apple News), which the new audiobook offering falls under. Such plans lower the mechanical licensing rates the company pays in the U.S. Spotify’s lower royalty rates are retroactive to March 1, 2024.

However, NMPA president-CEO David Israelite had strong words for the move when contacted for comment by Variety. “It appears Spotify has returned to attacking the very songwriters who make its business possible,” he wrote. “Spotify’s attempt to radically reduce songwriter payments by reclassifying their music service as an audiobook bundle is a cynical, and potentially unlawful, move that ends our period of relative peace. We will not stand for their perversion of the settlement we agreed upon in 2022 and are looking at all options.” The NMPA and streaming services resolved a years-long standoff over royalty rates with a Copyright Royalty Board ruling in 2022, and agreed upon a new rate of 15.35% for the 2023-2027 period.

This doesn’t help with your current issue, but you should use Nextcloud All-In-One instead of setting up individual containers like in the tutorials you linked. It will create and manage all the containers that are needed.

Domains are pretty cheap, so you may want to consider whether not using one is really worth the effort.

The article sounds like you could have the A records on a local DNS service like Unbound or Pi-hole instead of public DNS. I guess maybe they just need to be defined somewhere that they’ll resolve for your Caddy instance.

Keepass has a synchronization mechanism, maybe you can get it to work between your phone and your PC?

If the files to be synchronized are accessible via a protocol that KeePass supports by default (e.g. files on a local hard disk or a network share, FTP, HTTP, HTTPS, WebDAV, …, see the page ‘Loading/Saving From/To URL’ for details), then no plugins/extensions are required.

If one of the files to be synchronized should be accessed via SCP, SFTP or FTPS, you need the IOProtocolExt plugin, which adds support for these protocols to KeePass.

If one of the files to be synchronized is stored in a cloud storage: for most cloud storages, there is an integration with the local file system available (i.e. you can access your stored files using Windows Explorer). For example, Dropbox, Microsoft OneDrive and Google Drive provide such an integration. If such an integration is available, it is recommended that you access your database file this way; this often works better than accessing it via a protocol like FTP or WebDAV. If no such integration is available and your cloud storage also is not accessible via a standard protocol, a specialized KeePass plugin for this cloud storage might be available.

Like the other commenter said, you can use Let’s Encrypt without needing to expose anything on your network to the internet. I set it up on my network a couple of weeks ago using this guide; I couldn’t get caddy to work with duckdns but it worked with Cloudflare without any trouble.

According to Engadget’s coverage of the first model with the touchscreen case, the case mostly just lets you use functionality from the app that goes with the earbuds without actually going into the app. I don’t use the apps for my earbuds or headphones, so I can’t say how useful quicker access to their functionality would be.

deleted by creator

Jeez, my Razer mouse only launches the installer for their crap, it doesn’t automatically do the installation.

I guess buying that online news law hasn’t been a great investment for Murdoch.

This seems relevant: My Distaste For Your Solution Does Not Mean Disregard For The Problem

Anyway, I don’t think this law would reduce Meta’s power if the company cooperated, because if Meta only falls under the law if it has power then news organizations have an incentive to make sure it keeps enough power to keep the law applicable and keep getting them paid.

“Meta’s practices are clearly designed to discipline Canadian news companies, prevent them from participating in and accessing the advertising market, and significantly reduce their visibility to Canadians on social media channels,” the CBC said in a joint statement with the Canadian Association of Broadcasters and News Media Canada, a trade organization that represents newspapers.

Isn’t the argument for C-18 that the advertising market isn’t doing the news organizations much good anyway?

And as far as their visibility on social media channels, the news organization created this problem for themselves in the first place by encouraging people to share their work on social media; if they’d focused on making sure people know where to find them instead of posting all their work maybe their sites would be getting more traffic. They tried a business strategy, it didn’t work out, and now instead of coming up with a better strategy they’re trying to force Meta and Google to give them money and make the bad strategy work.

Canadians expect tech giants to follow the law in our country.

The law says Meta and Google have to pay to carry news; it doesn’t say they have to carry news. Maybe the law should have been written without that gaping hole?