diamond

joined 1 year ago
[–] diamond@beehaw.org 2 points 1 year ago

Yeah, it's at https://slemmy.libdb.so, the source code is also on my github!

Heads up, it doesn't currently work with Lemmy v0. 18.0. PR https://github.com/LemmyNet/lemmy/pull/3301 tracks this. If you or anyone can contribute to this, please do!

[–] diamond@beehaw.org 4 points 1 year ago (3 children)

I use the one that I made! It was made rather early on before most of these apps became popular, but if it's my own app, I can make it however I want...

[–] diamond@beehaw.org 4 points 1 year ago (1 children)

+1 on SchildiChat here as well.

I used to use FluffyChat but it would corrupt its internal SQLite database randomly. That happened a couple of times so I just stopped using it entirely.

[–] diamond@beehaw.org 3 points 1 year ago

I'm adding this into my Lemmy client's README.

[–] diamond@beehaw.org 18 points 1 year ago

Shameless plug (sorry) but I'm working on one too! It's a web app that works on both desktop and mobile: https://slemmy.libdb.so.

It is a free-time kind of project (I work on it after my actual working hours), so it might not grow at the same pace as other newer apps, but I'm trying!

Source code is at https://libdb.so/slemmy, AGPLv3 license.

[–] diamond@beehaw.org 3 points 1 year ago

No plans for a Docker image atm but you should be able to easily host this using any web server! It just needs to be built, and I might make a Github Action to automate that.

For now, the site is fully static and doesn't require any server so you can just use the one hosted on Netlify.

 

Hi hi, I know I posted about this yesterday-ish, but Slemmy is now deployed! Head to https://slemmy.libdb.so to give it a try! Simply make a profile with your favorite instance and continue!

If you haven't seen yesterday-ish's post, here are some screenshots of Slemmy: https://imgur.com/a/KJqKuiF

Unfortunately, there's no signing in yet, so you can't do much besides reading posts. I'm actively working on this, though!

The project's source code is at https://github.com/diamondburned/slemmy. Its README contains the current features and what is planned for now. I started on this project not even a week ago, so it's likely unstable and not ready for heavy use yet. Please open an issue if you encounter any bugs, I would really appreciate it!

[–] diamond@beehaw.org 1 points 1 year ago

Yup! Each profile will eventually be its own (possibly anonymous) account that belongs to an instance, something like this:

profile screenshot

[–] diamond@beehaw.org 3 points 1 year ago (1 children)

Whoops! I forgot to update it.

 

This app will mostly be intended for reading, but it'll support multiple profiles, upvoting and commenting.

I currently plan on targeting both desktop and phone usage, with some primitive touch gestures to make it easier. Unfortunately, since this is just a progressive web app, that's going to feel a bit scuffed.

The source code is at https://github.com/diamondburned/slemmy. It's currently not usable for production yet :( but I'm working on it!

[–] diamond@beehaw.org 0 points 1 year ago (1 children)

Huh, interesting. It seems that a WS connection to wss://beehaw.org/api/v3/ws works, but not wss://beehaw.org. I remember reading somewhere that the WS API will eventually be removed, though.

I'll continue development w/ the REST API until I feel like it's in a mostly-working state, and then I'll probably subject myself to the WS API after. Working with the REST API does feel a lot easier.

[–] diamond@beehaw.org 0 points 1 year ago (3 children)

Websocket handshakes are done over HTTP. The endpoint for Beehaw's WS API would be wss://beehaw.org/, so it's still going to use the same CORS policies as accessing the / (root) path.

[–] diamond@beehaw.org 1 points 1 year ago (1 children)

I had no idea that NGINX has Lua plugins. You'd probably want to check if Caddy has equivalents for those plugins though, or just implement them in Go yourself.

 

Hey Beehaw mods!

I'm currently working on a Lemmy web client, but the lack of proper CORS headers is preventing anything from working :(

I just wanted to ask if the appropriate CORS headers could be added to the front-facing proxy layer. If you're using Caddy, I believe something like this should do the trick:

reverse_proxy ... {
  header_down Access-Control-Allow-Origin *
  header_down Access-Control-Allow-Methods *
  header_down Access-Control-Allow-Headers *
}

Relevant issue: https://github.com/LemmyNet/lemmy/issues/3109

view more: next ›