For any UI devs: I’ve starting working on a lemmy front end called
lemmy-ui-leptos [https://github.com/LemmyNet/lemmy-ui-leptos] using leptos
[https://leptos.dev/], a Rust UI framework with isomorphic support, and tailwind
+ daisyUI [https://daisyui.com/] for the component styling. This could
eventually replace the frankenstein’s monster that lemmy-ui has become. Some
reasons for doing this: - lemmy-ui uses infernojs, which is based on the react
model. IMO is largely superseded by signal-based reactivity in use in android
jetpack-compose, SolidJS, and most new UI frameworks. - I had to hack on
isomorphic support / server-side-rendering to infernoJS, and it’s very messy.
Leptos has isomorphic support out of the box. - All the benefits of Rust over
javascript. - Since leptos is in Rust, we can import the lemmy types directly. -
I’ve been waiting for years for a good rust UI framework, and I think we’re
finally here with leptos or sycamore. - lemmy-ui uses bootstrap, which is
showing its age and limitations. Tailwind (and daisyUI) seem to be much more
future-proof. I plan on leaving the site design and component styling to other,
more skilled UI devs, while I work mostly on the auth, services, params, and
overall back-end structure. - Please use daisyUI classes tho whenever possible
over exhaustive tailwind ones. - I’d also like it if the UI could match that of
jerboa’s (whenever possible), so that a change in one could be represented in
the other, and so that things like badge appearance for admins, could be
recognizeable across lemmy’s front ends. You don’t really need to learn rust to
help out with this, as the components look very similar to JSX. Instructions for
running it are in the CONTRIBUTING.md
[https://github.com/LemmyNet/lemmy-ui-leptos/blob/main/CONTRIBUTING.md] . Feel
free to contribute! Right now only the home page, and post pages are working,
but ready to be styled.
Quoting the author
I’ve starting working on a lemmy front end called lemmy-ui-leptos using leptos, a Rust UI framework with isomorphic support, and tailwind + daisyUI for the component styling. This could eventually replace the frankenstein’s monster that lemmy-ui has become.
The fediverse to me will always be an expanding niche, I don’t think the network effect social growth works without cash. If your looking to measure by quality of dialogue instead of growth I think this presents the best option. There’s plenty of economic benefit beyond ad sales from good discourse.
Instead you’re looking a million AOL install disk moments until ubiquity, if it doesn’t fall apart first.
Instances shutting down is actually markedly like the way famine, war or anything else beyond my control as your average user would have pushed us to other reps. You can pick up and move, but how much of your stuff? Open question. Long term it should be feasible for your own instance to fire up, fetch messages and close again, so in theory you could keep all of it.
Now hardest: scale and cost, which I’d really contend are the same problem. If you look at how such systems are introduced you find advocates for vanguard, reps, workers tribunals and nothing quite ever sticks without some lingering problems. And the reality is the web of our modern universe isn’t going to independently operate with anything.
I don’t think anything but a charitable model gets it off the ground, the same way I don’t think the Internet is a thing without the crazy good folks running BBS boards. But it should be institutional as broadly as possible if you want long term success and trust in platform.
I think perhaps you may be confusing nobody to assert ownership of the bits, with the supposition that there is no cost on delivery.
the supposition that there is no cost on delivery.
The absolute opposite, actually. There is a cost to content distribution and for the maintenance of the service beyond the servers. Moderation, system administration, bug fixing, security research, optimizations in storage…
Putting up a server is the easy part. Ensuring that it can serve its users well, not so much. To do it properly, it becomes a part-time job. Now that there is an element of novelty to it, we will see many people sticking around to this work, but as the novelty wears off, they will either treat it like work or stop doing it altogether. We can see that happening already with Mastodon.
So in reverse order:
The fediverse to me will always be an expanding niche, I don’t think the network effect social growth works without cash. If your looking to measure by quality of dialogue instead of growth I think this presents the best option. There’s plenty of economic benefit beyond ad sales from good discourse.
Instead you’re looking a million AOL install disk moments until ubiquity, if it doesn’t fall apart first.
Instances shutting down is actually markedly like the way famine, war or anything else beyond my control as your average user would have pushed us to other reps. You can pick up and move, but how much of your stuff? Open question. Long term it should be feasible for your own instance to fire up, fetch messages and close again, so in theory you could keep all of it.
Now hardest: scale and cost, which I’d really contend are the same problem. If you look at how such systems are introduced you find advocates for vanguard, reps, workers tribunals and nothing quite ever sticks without some lingering problems. And the reality is the web of our modern universe isn’t going to independently operate with anything.
I don’t think anything but a charitable model gets it off the ground, the same way I don’t think the Internet is a thing without the crazy good folks running BBS boards. But it should be institutional as broadly as possible if you want long term success and trust in platform.
I think perhaps you may be confusing nobody to assert ownership of the bits, with the supposition that there is no cost on delivery.
The absolute opposite, actually. There is a cost to content distribution and for the maintenance of the service beyond the servers. Moderation, system administration, bug fixing, security research, optimizations in storage…
Putting up a server is the easy part. Ensuring that it can serve its users well, not so much. To do it properly, it becomes a part-time job. Now that there is an element of novelty to it, we will see many people sticking around to this work, but as the novelty wears off, they will either treat it like work or stop doing it altogether. We can see that happening already with Mastodon.