!learningrustandlemmy@lemmy.ml

It’s for learning rust (the programming language) and the lemmy code base itself as a sort of “reading club”. If you’re the type of person who might be interested there’s a good chance you’ve heard of it already. We’re currently working through The Book (conventional learning resource) through a couple of Twitch streams and regular posts/discussions.

More collaborative learning activity is plenty welcome!

Not sure how true that is. Either way, from what I’ve seen, fediverse platforms move slowly compared to what people would prefer.

later than the exodus, probably earlier this year.

There’s a chance what you saw was in part the core devs being a bit cranky toward feature requests that come off a bit “demanding”. In my case I asked them how the felt about the idea.

Actually, I think you’re spreading some false-hoods here.

I’ve spoken to the core-devs about this here, and they acknowledged that being able to follow people/users would be a generally good idea, but felt that it was a lot of work and so not a priority at the moment.

I’m with you on the desire of a platform the fuses the two general mechanisms (groups and users), and I think a groups-first platform like lemmy can bring something valuable to how a user’s feed would work … but the reality is that this sort of thing is just not in the fediverse’s DNA at the moment. These aren’t for-profit companies that need to wheel out features constantly to keep their stock price up!

There’s an exception to that though … friendica, hubzilla and streams, the sort of alternative timeline or “ancient magic” for the fediverse that predates ActivityPub and mastodon by long margins. They have clunky UIs, but are quite feature full, and happily combine both groups and users.

I believe you … gate-keeping types are all over the place really.

But vegans or the “vegan-curious” aren’t one thing or one kind of person, at least not any more. I personally have only ever had positive conversations with vegan types.

This instance, in being insistent on not entertaining any “harm reduction” or “compromises”, makes sense though … because it’s a space for people to talk about that sort of dedicated approach.

they drive away potential allies because the concept of harm reduction is anathema to their binary thinking. If you’re not ALL in, you’re the enemy.

I can resonate with that. But I come back to … “it’s totally ok for people to create their own spaces, especially on federated social media and especially for minority groups/ideas”.

There are likely plenty of other spaces for “potential allies” to engage and talk about veganism if they want to, or plenty they, or you, could make on their own.

Tacitly admitting that vegans are usually antisocial zealots. “It’s right in the name!”

Well, they’re running their own social media platform, so I’m not sure how anti-social they are.

Right. Well, I think the instance name “vegantheory.org” was doing that already, and I’m betting you drew your conclusion from the public description of the place too (and aren’t in the modlog or anything for challenging their ideas).

And what would a non-vegan want to do in there?

What’s wrong with minority views and practices creating their own spaces?

On which, is there any non-vegan/anti-vegan thought or idea that a vegan is likely to have not heard already? How many haven’t they heard relative to the amount of decent “pro-vegan” ideas they also haven’t heard of?

Maybe a specialised space, echo chamber even, makes sense in order to balance against the gravity of the mainstream?

I’ve peaked at that issue a couple of times, but I never worked out what the issue/feature got stuck on. Naively I would have thought it a relatively workable feature to add.

Youre right about lemmy-ui, unfortunately it doesnt have enough contributors. I dont know why that is, you’d think a project written in a popular language like Typescript would easily find contributors.

Random thoughts:

• Is it obvious enough that one can contribute to the UI separately from the backend and that it’s a Typescript SPA style UI?
  • If not, maybe a bit of a “dev recruitment campaign” could help … let people people know and what sorts of issues could really do with new contributors lending a hand? Maybe even a bit of a “Inferno isn’t that different from all of the other SPA frameworks/libraries spiel?”
• Is the use of Inferno as oppose to one of the big 3 React/Vue/Svelte a repellent? (perhaps a downside to the “diversity” of frontend frameworks?)
• Are would-be UI contributors more inclined to make their own front-end or app than contribute to the default webUI?

More generally:

• Would a server side rendered webUI be welcome?
  • Then the contributions would mainly be on templates and their “simpler” logic, which might be more attractive or easier to get started on?
  • Plus, it might be more efficient? The current UI feels to me like it would suit server side rendering well.
  • Is this where the new leptos UI is heading … more server side rendering (I don’t know much about leptos)
• Do you have a sense of usage numbers for the different apps and frontends? Obviously you only run lemmy.ml, but do you have a sense of how much the front-end gets hit versus the API directly?
  • I ask, because If the default WebUI is really the main interface, then it makes sense to try to organise some more contributors (It’s certainly my main, nearly exclusive interface, as much as I’ve like some of the alt front ends or apps)

Absolutely!

The bit I’m conceptually stuck on (not know much at all about how a good plugin architecture would work) is how a plugin can surface or affect the UI, especially in an ecosystem with multiple UIs/Apps/Frontends, and, a federated ecosystem at that.

Given the apps, I figure it’s not possible without a convention of plugins providing APIs which apps can then implement against when available, which adds a good amount of complexity but should be viable for popular/useful plugins. Though, tangentially, this does affirm for me that the whole native mobile app expectation is a bit of a trap for a social system like the fedi (as webUIs are naturally more universal and maleable).

So, for immediate results, I can see only two options:

1. a plugin operates on the backend directly manipulating or creating content not unlike a bot
2. a plugin provides its own webUI which is made available through a simple and dedicated location in the UI

Is there something I’m missing about how a plugin system could work?

I hear you for sure on this.

I personally appreciate the push the core devs make for a “less demanding” relationship between users and open source devs. I think they have a point and it’s good for long term sustainability and I’ll probably find myself defending it.

But I like you’re framing, and in retrospect it seems (as is usually the case) that some people organising was what was missing just to get everyone helping each out as much and efficiently as possible. While any member of the community can (and should) do that, at some point it makes sense for the core devs to take on a task like that, I agree.

Should there be something like a lemmy admin’s community for talking about the ins and outs of running a lemmy instance? Something like that over time can be some sort of band-aid for missing documentation (it’s searchable etc).

I’m aware that there’s the matrix room and a lemmy support community … but maybe just opening things up to any chat about hosting lemmy in one place could actually help (in part because you can easily search specifically within one community).

but we’re at a critical point right now. It’s no longer software that is just fun side projects and building stuff that looks cool, it has some real issues now that it has a real userbase. I’m definitely one to say “But it’s FOSS, and other people can pick up and submit a PR” - but it also says something when the head devs just completely ignore a massively huge issue with it.

This is a general issue I think, not just for lemmy but the whole fediverse (whatever one’s opinions might be on particular priorities).

It’s all non-profit and being run and built at a much smaller scale than many users would appreciate (I think). Sure there are plenty of people here, but not that many. Combined with no obvious revenue streams, such as ads or subscription fees, there really is only so much that can be done. Some time last year even the Mastodon team (by far the most successful fediverse platform) admitted that they didn’t have the capacity to work on new things for a while … they were just busy keeping things running. And they are (apparently) notorious at being slow to ship new features. Meanwhile platforms like firefish just straight up died last year.

So yea, it might be a critical point, for sure. But putting more on the core dev teams may not be the answer for the simple reason that it’s just not viable in the long run.

If we enjoy the bigger community focus and open and non-profit organisations that makeup the fediverse, the “answer” at this critical point might be to find a way to give back somehow … to organise, build communities, run fund-raising campaigns, think of ideas for more sustainable funding, find devs who can help etc etc. It’s perhaps onerous and annoying, even to read perhaps … but this is likely the tradeoff we have to make for a place like this.

The introduction of a plugin system seems interesting here, though it’s still alpha and basically looking for feedback from would-be plugin developers

AFAICT, there’s no established way for a plugin to surface affect the UI, which would be a somewhat unwieldy problem anyway due to the apps and frontends ecosystem. Probably the best path for any plugin that provides a UI would be to have a system for aggregating links to plugin UIs.

With something like that in place, plugins and other services that just use the DB/API, could really go a long way to filling these holes, if they haven’t already.

So it seems that the work needed here is perhaps “distribution” work … where there’s a more “plug and play” Lemmy distribution with plugins etc bundled?

A few months ago, the “Nazi” presence on substack and substack’s insistence on not moderating them (like at all it seemed) broke as a story, during which Casey Newton (and by extension his “platformer” blog) got engaged with substack about the issue and, after being disappointed with substack’s responses and policies, famously left for Ghost (see their post on the move here.

Pretty sure that boosted its profile and prompted talks of federating, which they were initially hesitant to do … but here we are now.

Ha, yea! If you know rust, then you don’t need to reach for Python (right?!). Plus the main motivation was to contribute to lemmy itself while also learning rust. That another platform is good for personal instances doesn’t change that, though piefed does seem cool and I can see myself wanting to get involved with it at some point.

Cheers! 2 threads and 2gb RAM I’d what I would have hoped for anyway. Thanks!

But I get the database thing. Its spiking every couple minutes and a lot every hour. It’s not a big deal if you have 2 threads at least but I can see how it doesnt work for everyone in every scenario.

Yea database management seems to where the growing pains are right now (with the core devs welcoming help from anyone with DB/PostreSQL expertise) … and indeed it seems to be a perennial issue across the fediverse platforms.

If I may ask (sorry, probably annoying) … what sort of resources would you recommend for a small personal lemmy instance? (let’s say 1-5 users, ~200 community subs and a few local communities?)

Woah woah … this is legit awesome! Just tested (on lemmy.ml) and yep … seems to be working like a charm!

Give up to matc-pub for the PR (and maybe a new core dev for lemmy too?).

I figure this makes live megathread style posts/chats more viable … which is certainly cool!

I’ve mentioned this before, but an interesting possibility might be to enable selected posts to be “live chats” through a websocket like process as lemmy used to be, just for selected posts for certain windows of time, whenever a live chat dynamic is sort.

It’s the sort of thing that could be scheduled and subject to admin approval or something if resources are a concern.

Otherwise … awesome to see!