Well, it’s a kind of stretched thought experiment, to imagine they had precise satellite-like temperature measurements in those days. But if you really want to ask, when did humans first have a discernible influence on the climate, it surely goes back much earlier than that - due to deforestation and associated changes in albedo (as well as CO2), also desertification in some regions (north africa?). I don’t see albedo or land-use change in this paper, only fossil emissions.
Well problem with any Lemmy community as such a forum, is that current usage (not necessarily intrinsic to the software) is so ephemeral. So it’s good for discussing breaking news, but not to gradually accumulate discussion of solutions to complex problems, over years. I wish this were not the case, but doubt anybody will even notice this comment, as no longer ‘hot’, and folded away … Rather, a few weeks later the same topic will be reopened under a different post, and we start over again.
I agree with most of what you say. I’m a long-time fan of calculating more complex things client side, as you can see from my climate model (currently all calcs within web browser, evolved from java applet to scalajs).
Also, in regarding social media, keeping the data client side could make the network more resilient in autocratic countries (many), and thelp this become truly a global alternative.
On the other hand, some ‘trunk’ server interactions could also doing more not less, bundling many ‘activity’ messages together for efficiency - especially to reduce the duplication of meta-info headers in clunky json, and work of authentification-checking (which I suppose has to happen to propagate every upvote in Lemmy?).
Thanks, that makes sense if I think about it, but maybe users shouldn’t have to - i.e. the Mdon part-conversation way still seems confusing to me (despite being a climate modeler and scala dev), although haven’t used Mdon much since I found Lemmy. And I still feel that both ways seem intrinsically inefficient - for different reasons - if we intend to scale up the global numbers (relating OP).
That makes sense, to store only popular stuff, or temporarily - especially for ‘heavier’ images (although as we see with lemm.ee, that leads to issues when an instance dies). Yet I also wonder about the scalability of just the minimum meta-info, whose size does depend on the protocol design.
For example with Lemmy every upvote click propagates across the network (if i understand correctly, mastodon doesn’t propagate ‘likes’ so consistently, presumably for efficiency, but this can make it seem ‘empty’). Maybe such meta-info could be batched, or gathered by a smaller set of ‘node’ instances, from which others pick up periodically - some tree to disperse information rather than directly each instance to each other instance ?
As the fediverse grows, gathering past meta-info might also become a barrier to new entrant instances ?
I agree with the gist of much of the article.
Although a fan of the original web, and developer of a climate web-app, I think small screens make people into consumers, while creators or investigators need a large screen, and that should be for dedicated periods of the day, not carried everywhere.
And we wish our kids had never had these things (gift from grandparents - hard to reject).
However the article title is over-simple, impractical - how would you even define what is a smartphone, in the spectrum of devices ? (maybe that’s cause of downvotes ? )
I don’t think the general architecture scales that well (think of all the duplicate storage …
That’s my hunch too, although haven’t studied in detail - so I wonder how we can fix it ?
Is there an forum that discusses this scaling issue (in general, across fediverse) ?
Since much (so-called) “AI” basic training data depends on Wikipedia, wouldn’t this create a feedback loop that could quickly degenerate ?
Oh, it’s designed for a big desktop screen, although it just happens to work on mobile devices too - their compute power is enough, but to understand the interactions of complex systems, we need space.
For many of them it’s still far away. But I note the ukrainian counter of russian casualties is about to pass a million. While there is ‘fog of war’ it’s easier to say people are missing, so friends and relatives can keep hoping that theirs is the special case. During any prolonged ceasefire, it would become clearer who’s gone forever - which is one reason why P avoids this situation (and also bans NGOs like soldier’s mothers, who used to help connect these dots).
Indeed, here’s an example - my climate-system model web-app, written in scala running (mainly) in wasm
(note: that was compiled with scala-js 1.17, they say latest 1.19 does wasm faster, I didn’t yet compare).
Je suppose la problème fondamentale c’est qu’il faudrait de la coordination avec d’autres pays vers lesquels ces milliardaires pourrait se déménager, mais actuellement la politique de certains de ces pays est capturé par ces mêmes milliardaires. Néanmoins, il faut préparer, pour qu’on puisse saisir le meilleur moment des oscillations politiques mondiales, quand cela s’aligne.
What happened to Assam and beyond ?
OK, nice promises, but seems to me overpowered for phone functions, so what’s their plan for battery lifetime (bearing in mind that a desktop os is less optimised for efficiency)?
Indeed it seems Trump picked up some ideas about “Juche” (national self-reliance?) from his best buddy “rocket-man”.
US has only 4% of the world’s population, there are now plenty of super-rich in China, India, etc. who like to flaunt i-stuff.
Yeah, but you just gave me an idea too, how about AI-directed canines? “apple-intelligence” applied to follow-your-nose. My dog loves to chase small spots of light, which might be a trick to steer them.
And if chinese buy iphones, do they now have to pay 84% tariff? - maybe HQ in europe solves that too?
So do they also tariff imports (e.g. american rice) that much ?
I haven’t been in Japan since 1997 (COP3) but was impressed by cycling past many little rice fields sandwiched between city buildings - it’s human-scale which is worth defending (similarly to some european agriculture - idea of CAP), the opposite of US prairies.
Isn’t it technically possible to split browser functions so we can recombine as we like? - i.e. separating the rendering / js engine from everything around the side - managing all the tabs, bookmarks, cookies and passwords, workspaces and sessions, mail, notes etc. In my case, I like the workspace structure provided by Vivaldi, but don’t see why it has to be built on chromium browser. Anyway as a developer I need to test against blink, webkit and gecko, so would be nice to swap them within the same user interface structure.
By the way, I develop a “javascript-heavy” web-app (interactive climate model) and it seems to be working fine, and fast, in firefox, so I’m not convinced by complaints in the article.