Federation, access and general concerns

Deebster, 11 months ago

I've seen this between other instances, so it's just just here but... my subscriptions to comms on lemmy.ml are showing as "Subscribe Pending" including !rust which has been like this for days. However, I still see the posts show on my homepage, and appear to be able to view and interact.

So I have two questions:

• What does subscribe do? e.g. are my posts visible on lemmy.ml I've just tried posting from here and my posts are visible from there so what exactly changes once subscription completes?
• What's the problem and how do we fix it? (Depending on the answer to #1 maybe the fix is just "ignore it")

admin, 11 months ago

However, I still see the posts show on my homepage, and appear to be able to view and interact

It's quite likely that your subscribe went through, mind sharing your findings by looking at the network tab in developer console on your browser.

What does subscribe do? e.g. are my posts visible on lemmy.ml I’ve just tried posting from here and my posts are visible from there so what exactly changes once subscription completes?

It simply makes communities on other instances show up in your subscribed feed. Similar to how you join a subreddit (the difference on lemmy is that the subreddit aka community is hosted on a separate instance).

What’s the problem and how do we fix it? (Depending on the answer to #1 maybe the fix is just “ignore it”)

My suspicion is that its websocket related, I've seen similar behavior when testing locally. The best you can do is maybe browse github for potentially relevant issues and see if you can help, otherwise please just be patient while things get more stable :)

Deebster, 11 months ago

Today seems to work better. TL;DR: to fix subs, unsubscribe, wait 20-60 seconds, subscribe.

---

I tried un- and re-subscribing to !rust (no pause) and grabbed the websocket messages.

Unsub

Sent:

{
    "op": "FollowCommunity",
    "data": {
        "community_id": 8,
        "follow": false,
        "auth": "x"
    }
}

Received: op: FollowCommunity response with data.community_view.subscribed = NotSubscribed

Resubbed

Sent: op: FollowCommunity msg with data.follow = trueReceived: op: FollowCommunity response with data.community_view.subscribed = NotSubscribed

Then I tried on a small sub (to test a theory) and I got two responses, the second being shortly after the first but saying .subscribed = Subscribed.

Then I retired for !rust with a delay between unsub and resub and this time I got the two responses, the first being the normal NotSubscribed response and the second Subscribed coming 22 seconds later.

I'm wondering if there's some batch processing or something that I was falling foul of by being too quick.

RoundSparrow, 11 months ago

lemmy is…alpha software at best imho.

lemmy_server development team needs some Database Management Experts to identify the key SQL queries and optimize them, possibly denormalize data and suggest wheres application caching can be done.

It looks to me like /communities list is fetched from SQL every time a user brings up that page, that data could be at least cached for 2 minutes in the Rust code. Or even add a trigger to generate a flat table when a new insert is done (addition of a new community).

So far, there hasn't really been but a couple people looking at the SQL problem of scaling:

https://github.com/LemmyNet/lemmy/issues/2877

RoundSparrow, 11 months ago

Any rust developers willing to update the API interfaces to the open source lemmy-lite application? https://github.com/IronOxidizer/lemmy-lite

It doesn't use websockets, it uses the HTTP API