Ben Matthews

  • New here on lemmy, will add more info later …
  • Also on mdon: @[email protected]
  • Try my interactive climate / futures model: SWIM
  • 0 Posts
  • 24 Comments
Joined 2 years ago
cake
Cake day: September 15th, 2023

help-circle
  • 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.


  • 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’d like to have no phone at all, I don’t like small screens, nor being interrupted. Problem is that phone apps are now almost obligatory for IDs, transport tickets, passes, banking, etc. So I’d just like a phone-receiver (modem) with a sim card on a USB stick that can enable phone-app-stuff via my laptop or tablet. (Yes some tablets have data sim cards, but we still need sms and occasional phone functions for ‘verification’ etc.). Any suggestions?







  • Two thoughts:

    • I’m subscribed to 160 communities, most very small, but see interesting stuff due to the Scaled option - also deliberately avoid the big news communities. Evidently, it takes time to join 160 small cs, so to get started it could be handy to have an all/local except list, and remove the biggest news /memes unless people tick a box saying they like such. Or make an algorithm that prioritises stuff related to what I upvote (which is how other social sites seem to get people started - e.g. i just tried rednote and it quickly learned i like mountains and trains) - but i guess that’s hard to implement as each instance would need to work out ‘related to’.
    • 2nd point - there are other user-interfaces - I’m using Alexandrite which has a better layout than lemmy default, but how to make this easier (instructions suggest docker, how many casual users will do that …)?

  • OK so I read "Here the key concept is that some of the effects of the large herbivores, such as eradicating trees and shrubs or trampling snow, will result in a stronger cooling of the ground in the winter, leading to less thawing of permafrost during summer and thereby less emission of greenhouse gases".
    I know the big impact of trees and shrubs on albedo - in spring they absorb sunlight and shake off snow, which remains on flat grassland. But regarding trampling - compaction- I’m not convinced. Winters are long and summers short, so accelerating cooling by some weeks wouldn’t make so much difference, as accelerating warming in the summer - that’s when the gases are released.
    Anyway what we do urgently need is global science cooperation to try to save the carbon and ecosystems of that permafrost, in that spirit such projects might help to thaw geopolitical obstacles.