silas

Hi friends,

Unfortunately, I had some health issues in the family to deal with this month. I was hoping to have made more progress on Lemmynade by now to be able to release a public alpha for you all, but sometimes life throws curveballs.

Thankfully, everything has been taken care of and I’m back to working on this project again. I’ll continue to provided updates here and there when I can.

Thanks for hanging in there. I appreciate you all and can’t wait to share Lemmynade with you! In the meantime, enjoy the refined app icon :)

- silas

According to the Bun blog and changelog, Bun now supports SvelteKit! Bun is an incredibly fast JavaScript runtime, bundler, transpiler, and package manager — all in one. Similar to using npm, here’s how you can start a SvelteKit project with Bun:

$ bunx create-svelte my-app

Where are you all finding details on what features are included in each version of lemmy-js-client?

cross-posted from: https://programming.dev/post/1805918

Here’s a glimpse of the community view on Lemmynade! I’m ironing out all the kinks and killing off bugs in preparation for alpha release—specifically improving search, posting, and the desktop layout this week.

Security and privacy are and will always be top priority with Lemmynade. Instances are verified before logging in, your account tokens are highly-encrypted on your own device, and the only data collected by me is simple, anonymous, aggregated statistics. Anything related to your account in any way happens privately on the server-side instead of the client.

Stay tuned on the alpha release date by following [email protected], and as always feel free to ask questions below!

– silas

Here’s a glimpse of the community view on Lemmynade! I’m ironing out all the kinks and killing off bugs in preparation for alpha release—specifically improving search, posting, and the desktop layout this week.

Security and privacy are and will always be top priority with Lemmynade. Instances are verified before logging in, your account tokens are highly-encrypted on your own device, and the only data collected by me is simple, anonymous, aggregated statistics. Anything related to your account in any way happens privately on the server-side instead of the client.

Stay tuned on the alpha release date by following [email protected], and as always feel free to ask questions below!

– silas

Hey friends and followers,

Here’s a quick look at the comments section in Lemmynade. I’m working full-time on this project and getting more exited to share it with you each day!

Follow [email protected] for updates as Lemmynade gets closer to public testing

It’s been a while so I’d thought I’d post an update real quick.

Still hacking away at Lemmynade each day, and Lemmynade now has an icon! Most of the basic features are complete. My focus right now is boosting security and performance. I’ve also got a few more bugs to work out with comments to make sure they’re displaying nicely.

If you’re new here, Lemmynade is a beautiful, touch-friendly web app and public website for Lemmy. The goal is to make Lemmy more approachable, discoverable, engaging, and fun to use through a high-quality user interface.

Follow [email protected] for more, and let me know if there’s anything specific you hope to see in Lemmynade in the comments!

It’s been a while so I’d thought I’d post an update real quick.

Still hacking away at Lemmynade each day, and Lemmynade now has an icon! Most of the basic features are complete. My focus right now is boosting security and performance. I’ve also got a few more bugs to work out with comments to make sure they’re displaying nicely.

If you’re new here, Lemmynade is a beautiful, touch-friendly web app and public website for Lemmy. The goal is to make Lemmy more approachable, discoverable, engaging, and fun to use through a high-quality user interface.

Follow this community for more, and let me know if there’s anything specific you hope to see in Lemmynade in the comments!

I'm getting a "user_already_exists" error from /user/save_user_settings no matter what settings I try to change. The JWT is valid, and this is happening on multiple instances the same (programming.dev, lemm.ee, etc.) Anyone have any ideas why I'd be getting this? Here's my payload:

{
  show_bot_accounts: true,
  auth: token
}

Edit: This issue describes a bug where this happens when the avatar field is not included. Just tested it and that's the same problem I'm running into. I fixed it temporarily by passing the current avatar url.

I hope this is obvious, but I wanted to get it out there because of how important it is.

If your client allows user-entered Lemmy instances, ALWAYS verify that the instance is a valid Lemmy instance before sending credentials over. Otherwise, the user may have entered a url to an unknown server or site, and you will be sending their login credentials to a server that may be logging and storing the request or even intentionally trying to capture these credentials.

Instead, call getSite at the very least, or use a public list of verified servers before making the login request.

I would not be surprised if down the road malicious sites with similar domains to popular instances will be created to get login details of users who mis-typed their instance domain. It’s partially our responsibility to make sure our users are safe, so let’s keep this discussion going as we learn new ways to handle security concerns!