RoundSparrow

joined 2 years ago
[–] RoundSparrow@lemmy.ml 0 points 2 years ago* (last edited 2 years ago)

Most common cause is people changing their language settings in their profile. It's a daily occurrence. The app really needs to tell people "25 messages not displayed because you are only viewing in Spanish".

 

cross-posted from: https://lemmy.world/post/3252643

lemmy.readme.io uploaded some great API documentation to get started making your own Lemmy client.

Proved very useful in making my iOS client Lunar

 

I'm starting lemmy-ui with:

LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy-alpha:8541 node dist/js/server.js

Running against the drone-lemmy instances created by lemmy_server's api-tests scripts. I'm running latest main checkout on both projects.

My browser gives me:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8536/api/v3/community/list?type_=Local&amp%3Bsort=TopMonth&amp%3Blimit=50&amp%3Bpage=1. (Reason: CORS request did not succeed). Status code: (null).

api-tests scripts build dev mode, I thought CORS was turned off? I've played around with adding LEMMY_CORS_ORIGIN=* - but it doesn't help.

EDIT: reading this post closer, I see 8536 vs. 8541. If I manually refresh my browser against lemmy-ui on port 1234, it works... but I wonder where 8536 is getting picked up?

Thank you and I hope you are having a great weekend.

 

Someone was asking about it in support, so I was curious to try it. The Rust code has HideCommunity, I even tried to bypass the JavaScript client and do a direct API call.

Does anyone see the function call to send a HideCommunity object?

Where it might be disabled in the Rust code? I know it goes all the way into the database and is on SELECT statements.

Thank you

 

For lemmy server testing and performance baseline measurement, I think it would be cool to have every API call exercised.

Anyone willing to create and share some JavaScript client code? Normally these are run with Jest via NodeJS - but we can make it an extra step to integrate into Jest. I'm just thinking someone doing front-end app work can do a well organized hit on every API surface.

You can skip the creation of a user if you want, that code is already in the testing

Probably ideal to organize moderator vs non-moderator.

Something like: edit profile with every option one at a time, create a community, edit it, create posts, edit, delete, undelete, reply, etc. Imagine you were doing interactive tests of a major upgrade and wanted to hit every feature and button.

Right now most of that testing is done in independent scripts, such as a user test: https://github.com/LemmyNet/lemmy/blob/main/api_tests/src/user.spec.ts

And you can see it only tests editing a profile is working, not that actual features change their behavior. Although I've started to add that for back-end behaviors like showing read/unread posts on the list. Front-end devs are the ones who know what end-users do and the fringe cases to look out for. Thank you.

[–] RoundSparrow@lemmy.ml 0 points 2 years ago

A reminder to move to smaller instances for a better experience

A reminder that this constant advice people blindly parrot to install and flock to smaller instance has now created something like 1000 new servers in 50 days that are poorly run and already going offline as quickly as they went online.

Github Issue 2910 is the kind of PostgreSQL problems that the developers ignored for months and people still defend the developer choices to have the code doing real-time counting of every single comment and post for numbers nobody needs to needs done in real-time.

PostgreSQL is voodoo to this project, they do everything they can to avoid going to !postgresql@lemmy.ml community and asking for help, learning 101 about how to fix their SQL TRIGGER logic like Github Issue 2910 spelled out June 4.

 

Reference, June 4, 2023: https://github.com/LemmyNet/lemmy/issues/2910

Questions:

  1. Lemmy.ml was crashing every 10 minutes of every single day since May 25. Do you dispute this claim I make? Server log Evidence?

  2. June 4 issue 2910 was on Github and the same developers who run lemmy.ml put a tag on the issue June 4.

  3. Did it say server-crashing topic?

  4. Were you aware of the end-of-June Reddit API change?

  5. When was the issue fixed, date and who?

  6. Did you ask PostgreSQL communities on Lemmy for help? Which posts?

  7. Is lemmy.ml a developer run instance? Is this your idea of "supported" example of Lemmy's rust lemmy_server code?

Please explain. Like PostgreSQL EXPLAIN?

Was this what was given as an Issue 2910 to you on June 4, 2023?

 

Would fight or flight kick in with their behavior in avoiding the critical deepest (crash-causing, lost-data) software component name and identity? If the mistakes in such programming languages were causing multiple independent servers to melt down in CPU overload?

Can media machines traumatize developers, if there are extreme dehumanization contents and pornography stored in that back-end critical component? If the avoided programming language and logical errors in their own responsibilities utilized the word "TRIGGER" (programming syntax), could that induce social anxiety behavior?

 

Is .moderators supposed to be on GetCommunity() result? I can't seem to find it in lemmy_server api_tests context. All I'm getting is languages and community_view

EDIT: Wait, so there is a "CommunityResponse" and a "GetCommunityResponse", object? What call do I use to Get a GetCommunityResponse object?

https://github.com/LemmyNet/lemmy-js-client/blob/2aa12c04a312ae4ae235f6d97c86a61f58c67494/src/types/GetCommunityResponse.ts#L7

view more: next ›