• 5 Posts
  • 131 Comments
Joined 3 months ago
cake
Cake day: July 5th, 2025

help-circle

  • The biggest difference is that the Dot Com bubble was strongly focused on tech companies going public and pumping small cap stock prices up.

    The AI bubble on the other hand is almost entirely being built by private equity, with the largest players all privately held but with large cap stock companies holding substantial stakes. Rather than a bunch of small companies getting pumped up stock prices of many multiples of their debut price then falling to zero, instead we have large cap stock companies bumping up their value substantially, but not by major multiples, while the actual value of the biggest players in AI are all speculative and can’t be invested in by retail investors.

    This is all by design, the financiers of the AI boom are well aware that a public stock oriented rush into AI for retail investors would lead to massive speculation and an inevitable crash, instead with all the retail money going into large cap stocks they hope to capture that value and funnel the money into buying long term gains by making sure that those big companies have some stake in the “winning” private companies. When the first big AI companies go bust, they will be consolidated into their investor groups and harvested for innovation to transfer over to the winners.

    Overall this strategy seems sound to avoid a major retail stock bust, but isn’t wothout its own risks, for example if open source AI ends up winning out and the biggest private players fall flat they could become toxic assets and drag down the large cap stocks, and thereby the Indexes and Index funds in favor of leaner players. In the current landscape, that would mean Microsoft going down with OpenAI while Apple goes up, Apple is waiting on the sidelines with a huge cash warchest, ready to buy.








  • Not to mention that the scraped indexes can and should be shared. Unfortunately what OP is seeing may be a move to thwart this type of brute force scraping, and might resolve as dynamically assigned domain addresses, where the URL of a set object is temporarily assigned and streamed only to a single or group of IP addresses that request it within a given timeframe before being rotated out until found in search again and then reassigned a new URL, etc. This is a frankly stupid use of resources, but can effectively be used to prevent crowdsourced indexes from proliferating, and to punish IPs or even MAC addresses or browser fingerprints associated with downloading and reuploading videos which almost certainly have stegnographic fingerprinting embedded that associate with who the video was served up to at the time it was downloaded.




  • What? I pay $23 USD for YouTube Premium Family Plan, which includes ad free video and YouTube Music for 4 people. Still pretty reasonable IMO, never going back to Spotify that’s for sure, I have thought about trying Qobuz for higher quality, but the price increase across my family plus the fact that I never ever want to watch ads on YouTube makes it a difficult value prop, I’d probably rather buy one album a month from BandCamp.


  • I looked around a bit more, seems to be regional which is growing faster. UK Meshcore is growing fast, which makes sense since core devs are there. I haven’t found a good statistics source for node numbers, probably for the best given the network goals. Meshtastic of course is older so has the inertia lead, but the security and routing of Meshcore definitely is appealing to me and seems better for emergency situations where text messaging reliability is top priority.








  • If only I were the king of the world!

    I think what you are arguing for is hardcoding requitement for signatures with an “age appropriateness” ranking into the OS. How does this change the current situation where adult sites and apps are legally required to have an age verification popup/warning? Whether signature based or graphically based, what is at issue here is age verification which means referring to some “repository of truth” outside the will of the user. The problem is that the effect of this is to link government ID directly to web traffick, as to truly verify age requires verifying identity meaning abolishing anonymity on the web and enabling complete tracking of dissent.

    I could see a version of what you are describing akin to the way physical cryptographic keys are used to manage DRM on high end enterprise software, where identity/age verification would need to be done by the hardware vendor and not the software/site, the problem with that however is the aftermarket and multiple-user devices. You could say that the “age key” would be a hardware device sold to adults using physical ID akin to spirits or tobacco, something like a SIM Card but preferably with NFC rather than having to be installed in the device. “Adult Access” would then be enabled on sign-in by scanning the “age key”, enabling onboard software to serve software and sites that don’t have an “all ages signature”.

    Honestly as I write this, it isn’t the worst solution, the main thing would be keeping the Age Key as an interchangeable, replaceable device that only interacts with the OS and isn’t referenced by other software, so it doesnt just become another Digital ID proxie.