![](https://lemmy.world/pictrs/image/b6796b52-f56e-4310-be0d-f11e64ffe211.png)
![](https://lemmy.world/pictrs/image/eb9cfeb5-4eb5-4b1b-a75c-8d9e04c3f856.png)
deleted by creator
Developer fighting 502s from Lemmys Servers.
deleted by creator
Good idea! I’ll incorporate something like this in my own Lemmy App.
Off-topic question, but where can you see the stats?
Wow that’s really interesting.
Good idea. I’ll put that on the roadmap for my Lemmy app.
No. The ads from brave itself are only on new tabs and notifications.
I’m a FSE and I use GitHub copilot and Perplexity. I wouldn’t want to code without them anymore.
I want to get things done (especially when I’m at work) and not spent time reading docs or having 20 tabs of stackflow open. I’ve had enough of that lol.
I think everyone here knows copilot but perplexity is a lot smaller and newer. It’s basically like chatgpt but faster and it googles stuff, giving sources for each claim that I can read for myself.
For example, for my latest project I decided to give tailwind a try and instead of having to look through the docs for every little thing I just ask perplexity and it sums it up for me, even giving examples.
And I use copilot a lot for mundane tasks, for example when I write an API that takes an object of type Foo, Copilot auto Fills making variables and checking each for nulls and then I use that API in the frontend copilot already knows what I’m about to do and auto-fills the fetch.
I’m making an App for Lemmy and I’m planning on adding that feature. I also want to make it so you only have to register once and the App can register you to all the instances you choose automatically.
Edit: The Webapp is Nemmy, also the Community !nemmy@lemmy.world
Edit2: Please note that Nemmy is early Alpha, so not really useable as a daily driver yet.
Edit3: Changed Community link to proper format
Actually, I’m guessing wefwef is using the Js client, which usually returns a 503 or 500 when something goes to shit on the instance.
I’m also developing an app for Lemmy and the only solution I found was to just keep request the data until the instance finally gives in to the pressure and works.
So it’s less about “server is taking too long to respond” and more like “server responds instantly with a 503” because it’s overloaded and can’t handle any incoming requests.
I’m also guessing a lot of traffic comes from comments since the way of loading those is kinda stupid. (You load only the top layer and then for each comment you request the children, which sums up to a huge number of requests).
Lemmy should add more convenient APIs to reduce the amount of requests being made, maybe I’ll do that myself once I’m done with the app.
Sorry for the long ass text.
deleted by creator