Ben Matthews

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 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) ?

I’m more interested in distribution of users and local-focus of communities than country-based instances, nevertheless the map does illustrate that Lemmy has huge gaps - no country instance in all of Africa, hardly any in Asia… What can we do to make it a more global conversation ?

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 …)?

I might try Friendica, although coming from lemmy I’d be more inclined towards Mbin, to combine topic-focus and people-focus.
However as a developer I first check the code repos and see that both are based on php, which seems rather old, and i doubt this would scale efficiently if the network really took off. Recall that twitter was once based on ruby (like mastodon is) and shifted to scala for such reasons. So I feel, these are exploring well the potential user-experience, but the code may need a fresh structure (if somebody knows this tech issue better, please say). It’s good to discuss these things, to help consolidate potential efforts.

At the end I read: “I found my ideal social network … with the functionalities of Friendica, the UX/UI of Sharkey and the stability and reliability of Mastodon …” - so - please forgive me if I missed something, what does this combination, do we have to make it ?

I agree. For global discussions, are many Indians going to learn Chinese, Swahili, Hausa, Arabic, and vice-versa ? Meanwhile international-english is the new latin… Even within India, the south insists to keep english as an official language, to avoid being dominated by more populous hindi-speaking north.
Alternatively LLM-translation may facilitate multi-lingual discussion, but in this case the language of software development may still be influential during such transition.
By the way - this is an important topic for future of lemmy, which should expand more towards the south - where’s a good place to develop it (beyond such set of replies)?

I like some concepts and design of Mbin, something to learn from, but I’d believe more in its growth potential if not written mainly in php.

Interesting observation and analysis, and illustrates the potential of more lemmy-mastodon interaction.
Indeed mdon like-federation seems weird but I presume it was setup this way for efficiency, to reduce the number of small communications? Although Lemmy has a backend in rust - more efficient than mdon’s ruby - still I wonder whether the lemmy system of federating all upvotes would scale well if the number of users grows to that of mastodon and beyond ? Could there be some intermediate compromise solution (e.g. federate batches of 100 likes)?

I didn’t discover Lemmy through search, nor did I ever use reddit - I found it from mastodon where a few people promote lemmy posts. Then gradually realised I preferred the community-focus here, compared to the individual-focus of mdon (although combining both could be good). As mdon has many more users, improving this inter-op would help to bring people here.

Thanks, fixed! As you can see parts of the science code are already accessible via the ‘cogs’, but not yet the structural code - anyway keeps evolving, update soon.

Similar - I thought about codeberg for the source of my interactive climate model,
but am not yet ready to give it a pure-foss license - might split in parts with different licenses. Could try self-hosting.

I don’t buy this. I’m still using SMTP on my own domain and it’s working fine, a bit of spam but not unmanageable, real messages get read. Main challenge is digesting so many potentially-interesting list messages, indicating email’s continued dominance for professional topics. Seems this author has another agenda.
Having said that, it’s a pity the world never agreed a protocol for micro-payment for emails (and for many other services), which would resolve the spam problem, and not be a burden for honest users.

I see that says ‘has to be local only, not federated’ (same issue also discussed on github).
‘Local only’ suggests to me front-end, i.e. info stored by browser. In that case people who are often switching devices would have to re-organise on each one, which could be tedious.
So isn’t there something in between local and federated - i.e. saved by the instance as user-settings, but not pushed to other instances?
Maybe there could be some manual copying mechanism, so a user who organises a big set of communities could share with others. (This reminds me of mastodon ‘lists’ and various ways of organising and transferring them).

Nearly 200 upthumbs, more ?!
But the discussion explores broader and narrow variants, need to coalesce.

I’m using Alexandrite, find it good

Well, for example if I could reply to a mastodon post from my lemmy account - the poster would see that there (not here - but could show up on my profile page), and might follow it, so it could gain followers. To write such a reply, I’d need to somehow view the original post while logged into lemmy. My comments here do federate to mastodon, and if somebody searched for related words (at least from the instance from which I followed my #lemmy account) they should find this. Your “virtual community” seems like a mastodon list (I have a dozen such topic lists, that system could be better, but is improving), indeed it would be helpful to consider that alongside a lemmy community for similar topic.