RoundSparrow @ RoundSparrow @lemmy.ml

"Finnegans Wake is the greatest guidebook to media study ever fashioned by

---

Read more

Posts

127

Comments

598

Joined

2 yr. ago

Moderating

---

report a bug to lemmy about the broken quoting.

I have, weeks ago.

Consider posting to the official rust playground and creating a shared link.

I did share a link to GitHub, is that not good enough or something? Here is a screen shot for you.

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".

Recently I’ve noticed my feed has become almost entirely the main meme instance. The algorithm gives me 4 meme posts then a technology post then load more memes

Yes, same issue, and I'm using lemmy-ui...

Lemmy's backend Top/Active/Hot are pretty primitive. I'm experimenting with some ways to weigh smaller less-popular communities... because +20 vote on meme topics is noise, but +20 on some focused community can be a big deal. hot_rank doesn't take that into account and just looks at published date and score. It's pretty tricky to get new things into the backend, so it may be a while.

I personally would need to dig into testing and code again to give answers with confidence. What I'm trying to say more than anything is... don't assume. The level of mistakes in Lemmy's more technical back-end code are pretty high from my experience, especially when it comes to multiple servers involved (comment deletes not being sent to all servers was a situation I tracked down). What I do know is that there is very little written out there about people actually tearing it apart and showing what works... a lot of stuff gets logged in server logs as errors that almost nobody can explain. Either it's mistakes in apub JSON or other non-lemmy servers, or older versions of Lemmy, etc.

When you say packages get forwarded to whatever instance wanted (if I understand correctly) you don’t “unpack” (e.g check if it’s a valid request)

the pack metaphor isn't that great. But it is signed, and the receiving server checks a signature. But I really have not seen anyone discuss how those signatures are exchanged in the first place, and I've seen people say they re-installed their entire instance - which I assume generates a new set of signing keys for the same domain name.... and I know Lemmy starts with 1 in index for post, comment, person - and would end up generating the same numbers for different content.

I haven't seen much eye towards auditing any of this works, and if it even is a good design. Even 2 months ago there were some aggressive timeouts that were causing delivery to fail. And when something fails, the person who comments or posts doesn't get notified....

There is some deep stuff in lemmy., every community has a private key/public key pair, as does each person - but I'm not even sure that is used at all and was an ambition. I rarely see the topic actually come up and I've been listening for this kind of deeper technical topics... and created !lemmyfederation@lemmy.ml to try and better organize it.

Thanks again, and sorry for the ramblings.

I'm pretty much rambling myself... my repeat point is: don't assume. I would not describe Lemmy as battle-hardened against attacks or spoofing that someone can find to bypass the current logic.

I wouldn't trust that assumption, goarmy.com

It’s still early days

Lemmy has been on GitHub since February 2019, over four years. It isn't new at all. Several instances go way back.

The answer is: ORM.

Like normal people! :D Go to another instance, if you find something interesting

So "normal people" would go read another instance just to bring a single comment or post over. They may as just well join the other instance. Which is what I see actually happening.... Many of these lemmy accounts are the same person duplicated to route around crashes.

But it’s a little bit sad, that you’ve never done this and only look at all.

If you had any clue what I have been personally doing with lemmy for the past 90 days, you would laugh at yourself. I've been logging in to several different Lemmy servers every single day for months and posting about my observations... such as when a big instance put new user interfaces online, upgrade their backend, crash on their home page, etc.

i’d hope the query planner can still do something reasonable.

PostgreSQL specifically guards against queries with more than 8 joins... and Lemmy plows right past that.

Having worked with lemmy_server code for months, I wouldn't trust it in practice. Unless someone produces a pretty through test to validate that it actually works as intended when out-of-band data delivery attempts are made. And for discussion sake, I am assuming comment and posting "messages", and not private messages... which is a whole different set of behaviors.

when a user homed on lemm.ee comments on a post where the community is hosted on lemmy.world, it would get delivered to lemmy.ml by lemmy.world, not the origin lemm.ee instance.

Messages are sent with a digital signature that only the original instance could craft.

I don't think the actual message carries a signature from the origin instance, in this case lemm.ee - I could be wrong, because it may not unpack and repackage it before forwarding to subscribed instance servers. But there are some very short timeouts on these signatures and HTTP connections, and I think it does unpackage it and repackage a public comment message.

I think lemmy.ml would need to go fetch the profile for the then unknown user to be able to get the display name and other details of the lemm.ee comment creator to display on the comment. The signature for the comment I think would actually only validate lemmy.world to lemmy.ml - and if lemmy.ml already has the profile of the lemm.ee user stored locally it may not verify it (and could be an entirely different install with the same username). But I don't think many have ventured into study the code in these areas. The whole process hasn't been examined that much and I wouldn't be surprised at all if there are issues with post and comment getting dropped because servers aren't all reachable at the right times for these steps.

How exactly do I deactivate the “All Feed” to not pollute my server and avoid distractions to the users, but let them comment on external posts

How would they ever find the external posts to comment on in the first place?

Personally I think the issue is more that there is blind loyalty to team sports in USA culture, and no matter how many bad things are documented about a specific person (Donald Trump, Richard Nixon)... people are loyal to the image of that person, the brand and logo. People are raised in the USA to be inundated with breakfast cereal and toy company logo/brand recognition. It's a faith system. Breakfast cereals and fast-food "Happy plates" that fund a lot of children's TV are incredibly unhealthy and profit machines - and parents think this is psychologically healthy.

Politics will eventually be replaced by imagery. The politician will be only too happy to abdicate in favor of his image, because the image will be much more powerful than he could ever be. -Marshall McLuhan

It makes sense, but there are indexes.

As the subject of the post says... it is JOIN behavior that's the problem. The queries work perfectly fine when you ask for posts without doing JOIN to a bunch of empty tables.

Do you have any opinions on how they should work?

given lemmy's heavy focus on purging a user's content on account delete, I think comment links should include the username.

lemmy.world/the_username@home_instance.tld/comment/xxxx

This also gives self-promotion to the person, a sense of identity on their content.

A couple weeks ago there was a pull request to make it default, https://github.com/LemmyNet/lemmy/pull/3743

But i don't think it's in now.

cool. I'm in the camp that the feature causes more problems than is useful. Entirely hiding posts of another language would not be my choice, it should at least say "there are 5 comments you do not see because of your language preferences".

it does show the comments on incognito

That means it is tied to your login, something is set in your preferences so that you aren't seeing content.

Picking "undetermined" isn't the same as having never touched it. There is a steady stream of people who accidentally touch the language settings and say they don't see anything.

People have called out how confusing the whole thing is: https://lemmy.world/post/523012

Sorry I can't be specific on how to click and what works, I just know you aren't the first to get their account where it stops showing routine content.

Without more details, it's hard to know what you are describing. Do you mean comments from other people on posts you make? or your own comments?

I assume you are talking about the main webapp, lemmy-ui, and not a smartphone app or other front-end? The first thing to try is anonymous reading of the same post - are the comments there for incognito mode?

I'ts not uncommon for people on Lemmy to set their languages to something odd and and Lemmy will hide a lot of content.

Again though, that sounds like something that can be indexed.

I don't get what you are suggesting. There are INDEX.

The problem being addressed is that there is no WHERE clause that actually limits the posts.

JOIN is done on a table without first eliminating rows... and that worked OK when there was only 50,000 posts in the database, but now that it is over 1 million rows - it is causing major performance problems.

Better file a bug about that

Bug has been open for weeks. Doesn't seem to be a priority to undo the added HTML sanitation problems.

The code I pasted here on Lemmy is also on GitHub comment without being munged: https://github.com/LemmyNet/lemmy/pull/3865#issuecomment-1683324467

It's still mostly like the original function it is copied from, just some of the logic has been successfully stripped out. But it's probably worth looking at the bigger picture of just how much of the Rust conditional logic goes into building this SQL statement.

You might have to denormalize the comment count (put it in a column in the threads table

When browsing a community, the concern is 'post', not 'comment' or threads. So this doesn't really come into play. If anything, Reddit/Lemmy style system is focused on the latest vote count, not the number of comments....