Uncheck all the DLCs except for wetland, you should have maybe 8 animals left. Play with the habitat options abit if you don’t, but eventually settle on Exhibit, you should end up with just Danube Crested Newt. Now go and turn off each individual biome slowly. One would expect the Newt to disappear and never come back, but instead it pops in and out of existence. Something quirky is happening and you may wish to review the logics.
The amount of people who would pay is going to be near zero in the grand scheme of things.
Next time you’re anywhere where you could discretely look at people’s phones, see how many of them run apps with ads. Most apps will offer very cheap IAP to remove ads, but people choose to not pay it. Vast majority of the users have already decided that their time wasted on ads are worth less than whatever tiny monetary cost it would be to remove them. Same thing here: Vast majority of the users have already decided they’re not going to pay to get rid of the ads. This in turn means due to how few people who would be willing to pay, it is not going to be nearly sufficient to keep the infrastructure required up and running, as well as keep the creators compensated for creating the content.
Japan has nicovideo.jp as well. Russia has Yandex Efir (gone through a couple rebrands, Efir was the name in 2020 when we were discussing deals; it was operating under another name prior, and I think it is superseded by dzen). Off to the side I think vK also has a small video delivery presence like how Facebook has videos in their feeds. China has several platforms: Tencent Video (owned by Tencent), Youku as you’ve called out (owned by Alibaba), XiGua (ByteDance), Haokan (Baidu), and then slew of smaller ones like KuaiShou, BiliBili and that video thing WeChat tries to push. None of these are public service operated by the State, by the way. List really goes on… and I’d know, because I’ve worked in the space for almost 12 years now.
China’s great firewall aside, all these platforms are tiny in comparison, and in the grand scheme of things, and barely have any reach. In general, these regional are all taking a backseat just like Nebula and alike — if creators’ content are hyperlocal/super niche, they might be okay with smaller regional platforms; but if they’re trying to extend their reach and monetization (to ensure they have money to continue producing content), the creators’ presence on these platforms are really just auxiliary to their primary presence on YouTube.
Getting viewers to these smaller platforms is going to pose a significant chicken or the egg problem — creators aren’t incentivized to be there because lack of viewer, viewers aren’t incentivized to go there because lack of content. Worse yet, I’ve also seen situations where creators are paid for some period of exclusivity and then when the deal lapses they just go straight back to YouTube.
Real competitors do not exist, and likely will not exist for the foreseeable future. YouTube is the million pound behemoth when everyone else barely registers on the radar.
That’s a drop in the pond in the grand scheme of things. You just out source that out to rights management companies and absolve yourself from that obligation behind safe harbour. This is basically what they’re doing in this department. They’ve built Content ID for digital finger printing, and then invented an entire market for rights management companies on both sides of the equation.
On the other hand, 500 hours of video footage got uploaded to YouTube every minute per YouTube in 2022 (pdf warning). 30 minutes of video game content (compresses better), just the 720p variant using avc1 codec is about 443MB of space. Never mind all the other transcodes or higher bitrates. So say 800MB per hour of 720p content; 500 hours of content per minute means 400GB of disk space requirement, per minute; 500TB of disk space per day.
That’s just video uploaded to YouTube. I don’t even know how much is being watched regularly, but even if we assume at least one view per video, that’s 500TB of bandwidth in and then 500TB of bandwidth out per day.
Good luck scaling that on public budget.
Good luck getting that through the system… the cost to run something like YouTube is… well, let’s just say the lack of real competitions speaks volumes.
Here we observe a pro gatekeeper in their natural habitat…
Self driving cars need to convince regulators that they’re safe enough, even if assuming they master the tech.
LLMs has already convinced our bosses that we are expendable, and can drastically reduce cost centres for their next earnings call.
There was similar things done on Reddit during the big exit. I doubt it achieved what people expected it to achieve. Even if they’re not visible externally, I’m sure they can easily access (thereby make deals to license) the data out of their backend / backup; just a matter of how hard they want to try (hint: it’s really not very hard).
Having seen some spicy pillows in my times… I’d hate to be onboard if any of the battery containers becomes a bouncy castle.
Can’t wait to see how these compares to the M series from Apple. More competitions should be good for both platforms, forcing them to push performance further.
I’ve seen that. Thanks! Now if only they’d enable it for Europe instead of forcing people to use their AltStore, which ends up costing them more, AND costing everyone else more.
https://developer.apple.com/support/core-technology-fee
Also worth noting, distribution on third party App Store does not exempt developers from the developer program fee — Developers must sign a separate agreement to opt into the new business terms.
So, not only they are still responsible for the $99/yr fee, they’d need to sign a new agreement to opt into the new business terms, which has a separate additional fee schedule attached.
So does altstore. With the core technology fees and application requirements, it is much much higher than the 99/yr developer fee.
Also that’s besides the point. I’m trying to learn if the developer said they’d publish on the App Store, not the AltStore.
The linked toot states for publish on the altstore, which is not the App Store. Is there a different statement elsewhere stating otherwise?
One potential downside to this on the posts/comment front is that if the thread in question is not in a community your instance is federated with, any form of local redirect would yield just an empty post with no comments. Lenny’s current federation is primarily push driven, so when requesting a post from an unknown community will yield no historical comments, as your instance have never subscribed to the community and thus never received the push notifications. Whereas getting sent to the original instance, you’d be able to see the full interaction history and have a better picture of the intended discussion.
Honestly, neither does having to securely wipe SD card (or any storage device for that matter) as one cross the international border like the thread further up suggests. So the whole thing is just having fun with (potentially roleplaying) over paranoid people :)
May I interest you in this $5 wrench?
Most DNS requests are clear text, which is why DOH was introduced to secure it such that no one can snoop on you looking up something-embarrassing.com. Also, the initial request, before you get the SSL certificate from the web server, you must tell the server at 169.169.169.169 that you’re looking for the certificate for something-embarrassing.com before they can get you the correct certificate. This is why ECH was introduced. Neither of which have became mainstream yet, and so there are still some basic leakage going on.
Strictly speaking, Encrypted Client Hello (ECH) paired with DNS Over HTTPS (DOH) can resolve this. But not many people have their systems setup this way, so it is still pretty niche.
The industry by and large have moved on to containers, with docker being the entry point and eventually graduating to something larger and more orchestrated like k8s.
You’d generally use a publisher container (I.e. php:latest), and then volume mount your code into it for development, and eventually baking your own image for deployment. Be mindful to not include secrets (API keys, passwords, etc.) and inject them via environment variables.