> I think the main thing to be worried about is that this model is undermining the fundamental economic model the internet's currently based on.
And this is the reason why Google took its sweet time to counter OpenAI's GPT3. They _had_ to come up with this, which admittedly disrupts the publishers business model but at least if Google is successful they will keep their moat as the first step in any sales funnel.
I'm speaking for its place in video games. Stuff like Hearts of Iron and Diplomacy are birthed from Risk but are extremely niche. In fact, for fully graphical video games, they often have board-game like communities (the games have no QoL systems like match making, you'll have to organize it yourself on Discord). For example, the QoL to be able to jump into a lobby like the one posted here is not available in $50 dollar Risk-like/Diplomacy-like games. You can't even do that in 4x grand strategy multiplayer games. It's a got a long way to go. It took some time until all the concepts of DND got fully fleshed out into graphical RPGs and MMOs. I hope the same happens with the Risk-line of games, but it may also forever be niche.
This game right here is a offspring of SC2 Risk Legacy map:
Both games have a small, dedicated community. Line wars usually require people in Discord to gather people for games.
The compelling thing about Risk games is that once you make it past the early game, it quickly shifts into a sophisticated social game where you have to LARP geopolitical diplomacy since most countries/armies are too big (entire sovereign nations) by the end game.
> All the work I spent customizing window manager settings in the 90s, or improving my Perl development experience early this millennium, produced stuff I don't use now—except for the skills.
If you enjoyed the process it was time well spent.
We had like 4 Tektronix X Terminals that could connect to Sun workstations for those fortunate to have accounts, the rest was using VT terminals to a VAX. And yes, the talk and MUD use cases where popular ;)
I checked the math and it is correct!
So assuming this is a representative sample, there would be 800000/0.000013 ~= 61 billion galaxies in the celestial sphere.
According to Wikipedia, "It is estimated that there are between 200 billion to 2 trillion galaxies in the observable universe."
Another datapoint with an 15 Pro Max. I shot a couple of pics indoors in my own room and got the message. Seems the app is continuosly processing what's coming from the sensor.
Sounds like the app is just not properly optimised yet.
The built in iOS camera app can do something sort of similar - you can set it to shoot in adobe raw (12mpx scaled down from the 48mpx sensor). Often the phone will shoot HDR by combining multiple photos. And in night mode (either manually activated or auto) it will stack (combine) multiple exposures for long exposure noise reduction and (maybe) exposure stacking. Setting it to a longer amount (max is 7 seconds I think) should thereotically combine more photos.
The adobe raw format can store this info (it's actually quite underrated - I first switched to iOS with the 15 pro and immediately tried to find a way to shoot a true "normal" raw like a .DNG). I'm very into photography and used to be a professional film editor and one my favourite hobbies is astrophotography (with a real camera and tripod).
The cool thing about adobe raw specifically is that the HDR stack is not baked into the file. If you open one in Lightroom mobile, for example, there is a slider under the far right "profiles" editing section. The slider defaults to the middle (50) which is basically the default stacked HDR look from Apple. Moving the slider all the way left will have it use a single exposure (normal raw - no HDR no stack). Anywhere in between will be a blend of the two. If you don't see the slider then you haven't properly opened the adobe raw file in Lightroom mobile (you may have opened a jpeg preview or accidently shot in .heif)
It's quite counterintuitive because "profiles" when editing a non adobe raw is a totally different function (more like adding preset looks). If the file was not taken in HDR then the slide will do nothing. I'm not exactly sure what moving the slider to the right does (it seems to increase the amount of HDR or something - I never use it).
I've noticed that when editing adobe raw on iOS messing with this slider seems to be by far the most CPU intensive aspect. Sometimes the image preview updates immediately and sometimes it takes awhile and the phone heats up. Sometimes the app just crashes. It might be using a similar algorithm to what the Adobe Indigo app is using here for image capture.
Editing raw files also kills my battery life faster than anything else I've done (which makes sense) considering that it's a fairly intensive process. This was also true on previous Android phones so it's not limited to iOS. I usually stop any music playing at the same time and make sure the phone is out of direct sun and it seems to handle heat buildup well when doing this. If it does heat up I remove the case and put it in front of my car AC vent or some other ventilated area and it cools relatively quick.
And this is the reason why Google took its sweet time to counter OpenAI's GPT3. They _had_ to come up with this, which admittedly disrupts the publishers business model but at least if Google is successful they will keep their moat as the first step in any sales funnel.
reply