Lemminator is a web UI that aims to make Lemmy more approachable for a broad non-technical audience. It can be hosted by Lemmy instance owners, and Lemmy.world users can use https://lemminator.netlify.app/.
Suppose I modified Lemminator's search bar so you could paste a link like https://lemmy.ml/comment/1234 or https://lemmy.ml/post/5678 in it and press Enter to navigate to the relevant comment/post within the web UI. I could automatically infer that these are permalinks from other instances. Would that help at all?
You're hitting the nail on the head. Reddit-style websites are familiar to a lot of people, but we need to do a better job of explaining instances and federation. Not with text or technobabble, but with a UI that's so intuitive it almost speaks for itself.
Prior to starting my own web UI I considered becoming an Alexandrite contributor. I like how colorful it is compared to the regular web UI. My vision is too different from a technical, design and UX perspective though, so I still think it's worth pursuing a separate effort. I hope it'll pay off.
Thank you! There's obviously still quite a way to go, but I'm hoping I or someone else will get there eventually.
I agree that defaults matter a lot. You get only one chance to make a first impression, and most people will probably decide within a few seconds whether Lemmy is worth exploring. We need to get those users excited to explore the platform.
Granted, some people may be scared that it's going to "dumb down" Lemmy. But Lemmy will always continue to be about freedom of choice: you pick an instance you like, instances can offer any selection of web UIs they want, and you pick from the offered web UIs.
The prototype is live at https://lemminator.netlify.app/ now! You'll notice that it's still readonly, so not quite ready to be a daily driver, but gotta start somewhere.
Not sure I'd make the width cover the full middle section, but I agree that search needs to play a more prominent than in Lemmy's official web UI. The related post search is an interesting suggestion I hadn't considered yet!
I'll take it into consideration! My first focus will be on enabling more basic functionality like upvoting, downvoting and commenting. Right now it's still read-only.
Awesome. Read-only browsing is fairly stable at this point, but I think I'll need to have basic account interactions like upvote, downvote and comment implemented before I have a minimum viable product. In general, I prefer to polish the experience before expanding the feature set.
Lemminator is a web UI that aims to make Lemmy more approachable for a broad non-technical audience. It can be hosted by Lemmy instance owners, and Lemmy.world users can use https://lemminator.netlify.app/.
I've noticed on both the official web UI and Thunder that the permalinks don't always scroll to the right comment. Lemminator only shows the relevant part of the conversation, e.g. https://lemminator.netlify.app/c/lemmyapps/post/3824810/comment/2824106.
The former. The comment reply contains a
pathparameter listing the IDs of all its ancestors. I take its direct ancestor and fetch it.What error were you seeing? If it's unrelated to Lemmy.world downtime, I might be able to help.
Interesting, I hadn't considered that before.
Suppose I modified Lemminator's search bar so you could paste a link like https://lemmy.ml/comment/1234 or https://lemmy.ml/post/5678 in it and press Enter to navigate to the relevant comment/post within the web UI. I could automatically infer that these are permalinks from other instances. Would that help at all?
The link is https://lemminator.netlify.app/. While it's still very much a work in progress, basic navigation and upvote/downvote are already working.
You're hitting the nail on the head. Reddit-style websites are familiar to a lot of people, but we need to do a better job of explaining instances and federation. Not with text or technobabble, but with a UI that's so intuitive it almost speaks for itself.
Prior to starting my own web UI I considered becoming an Alexandrite contributor. I like how colorful it is compared to the regular web UI. My vision is too different from a technical, design and UX perspective though, so I still think it's worth pursuing a separate effort. I hope it'll pay off.
Thank you! There's obviously still quite a way to go, but I'm hoping I or someone else will get there eventually.
I agree that defaults matter a lot. You get only one chance to make a first impression, and most people will probably decide within a few seconds whether Lemmy is worth exploring. We need to get those users excited to explore the platform.
Granted, some people may be scared that it's going to "dumb down" Lemmy. But Lemmy will always continue to be about freedom of choice: you pick an instance you like, instances can offer any selection of web UIs they want, and you pick from the offered web UIs.
A readonly prototype is available at https://lemminator.netlify.app/ right now ;)
Its working title is Lemminator. You can try a readonly prototype at https://lemminator.netlify.app/ right now.
I have a readonly prototype up at https://lemminator.netlify.app/!
The prototype is live at https://lemminator.netlify.app/ now! You'll notice that it's still readonly, so not quite ready to be a daily driver, but gotta start somewhere.
Thanks, I've settled on AGPL as well. I expect to release the source code somewhere in the coming days.
Not sure I'd make the width cover the full middle section, but I agree that search needs to play a more prominent than in Lemmy's official web UI. The related post search is an interesting suggestion I hadn't considered yet!
I don't have macOS/iOS available to test on, but in theory it should. I have a prototype up and running at https://lemminator.netlify.app/.
I'll take it into consideration! My first focus will be on enabling more basic functionality like upvoting, downvoting and commenting. Right now it's still read-only.
No worries. Here's to freedom of choice!
Yes. Maybe GPL, maybe MIT, maybe something else. But some flavor of open source license.
Awesome. Read-only browsing is fairly stable at this point, but I think I'll need to have basic account interactions like upvote, downvote and comment implemented before I have a minimum viable product. In general, I prefer to polish the experience before expanding the feature set.