These issues have been obvious for months, lemmy.ml wasn't sharing the server logs Now at least there are multiple sites with a modest amount of data who see these issues: https://github.com/LemmyNet/lemmy/issues/4017
RoundSparrow 12 months ago • 100%
One really wonders where the priorities of this project really lie? https://www.reuters.com/world/us-accuses-china-global-media-manipulation-2023-09-28/
Is there something special about the 28th day of the month and precisely 90 days? A very obvious server-crashing / denial of service problem was called-out in Lemmy code two days before the Reddit deadline. https://github.com/LemmyNet/lemmy/issues/3394 Observations: 1. Why would anyone think 5 is a good design for production in the first place. It puts into question the developers for over 4 years of experience - they clearly understand the technical issue - it is the same coding / parameter issue for any programming language. What is the motivation / priority here? 2. lemmy.ml developer-run server (then the Lemmy server with the most data) was crashing from PostgreSQL overloads May and June 2023 every day... 3. there were active countdowns to the July 1 Reddit API change, This was June 28. 4. The change takes about 30 seconds to code, by no means is it difficult to understand. But it must be approved by the core developers of over 4 years on the project... and even notify live sites to urgently edit the Rust source code and re-compile. (And why not move this value to an environment variable that can be set without recompiling Rust code?) June 28 issue opened / code created July 1 Reddit API deadline September 28 code published 90 days to change what has contributed to lemmy.ml, beehaw, lemmy.world - and the entire network of Lemmy servers crashing constantly from Lemmy overload. Almost as bad as GitHub Issue 2910 being ignored all month of June 2023! https://github.com/LemmyNet/lemmy/issues/3394
RoundSparrow 12 months ago • 100%
On a positive note, an actual concern for data integrity expressed by core developer!
"This is a major issue with moderation, we should consider publishing the fix in an 0.18.5 release."
https://github.com/LemmyNet/lemmy/pull/3988
Although the project has an obsession over deleting data. Removing data. For communist flag waving project leaders, why is there such a focus on messages being deleted/removed? Why isn't it more like WIkipedia where commons is emphasized and terms-of-service emphasize that this is primarily a public forum and contributing to commons (communism?! hello?).
RoundSparrow 12 months ago • 100%
The lack of care for data and actually noticing data on the site keeps being demonstrated. Issue has been ignored for months - and was newly introduced bug when all the post Reddit API change was going on...
Just opened today, people repeating it, which the site creators do not repeat these easily solved bugs as priorities. Why not have a "top 20 bugs" and organize them 2 ways, easy of fix and importance of fix. https://github.com/LemmyNet/lemmy/issues/3987
RoundSparrow 12 months ago • 100%
RoundSparrow 12 months ago • 100%
2023-09-22
Communications... still really odd how May, June, July there was so little: https://sh.itjust.works/post/5652703
The claims to support Reddit level performance without listening to what Reddit has to say about PostgreSQL scaling from more than a decade ago is... still really bad. They still claim 'high performance' on the front page of the project as they have for a long time, when it isn't because it lacks any caching and there are still bugs lurking in database due to lack of testing with significant data.
Claiming that federation scales to Reddit when Reddit is a single-site (and has no federation equivalent) is pretty odd performance claim.
A change in direction for the project this week? Maybe the reputation of stability on lemmy.world and people realizing that the amount of activity really wasn't that high - and lemm.ee shutting out images. Most of all, Beehaw's criticism maybe finally resonated. Beehaw was online a full year before Reddit - and saw just how long-term issues were not being addressed... maybe that is what it took. It is worth keeping a positive eye on things.
RoundSparrow 1 year ago • 100%
The logging that comes out of the Rust code on errors really says it all. Over 4.5 years of coding on the same project and running it on the live public Internet at lemmy.ml - and there is no way for a site operator/admin to view the Rust code failure logs without having to do all that independently (and no recommendations on the importance of viewing logs). And when GitHub issues get posted with log problems, the developers with all the Rust code experience ignore them.
RoundSparrow 1 year ago • 100%
This gem of a quote: "That index is great, I didn't see that because on my database I guess the person table is too small for it to matter." https://github.com/LemmyNet/lemmy/pull/3960
That's exactly the problem with the whole project, no data, not concerned about data, ignoring all the problems on lemmy.ml since April despite 4 years of experience... data is not the focus of the project developers. lemmy.ml ran for 4 years on public Internet with nearly zero data. Not even a couple hundred megabytes of data.... and no testing and observation of problems with scaling and more data. It seems like they have 4 years of experience that isn't experience... just like Beehaw has shown with moderation experience and tools.
They ignored Issue 2910 for months during the critical Reddit API issue period, it worked fine with no data in the system, but was surely crashing lemmy.ml lemmy.world beehaw and all my test systems once even a modest amount of data is populated (it really does not take much)!
RoundSparrow 1 year ago • 100%
data loss... this has been going on for more weeks than I can count, and the developers with over 4 years experience are not the ones fixing such data-damage/data-loss bugs... just has been the pattern since Issue 2910 was ignored for months.
It seems api_tests is unstable, failing around half the time.... been that way for days it seems.
RoundSparrow 1 year ago • 100%
Yesterday, you probably saw this informal post by one of our head admins (Chris Remington). This post lamented some of the difficulties we’re running into with the site at this point, and what the future might hold for us. This is a more formal post about those difficulties and the way we currently see things.
Up front: we aren’t confident in the continued use of Lemmy. We are working through how best to make the website live up to the vision of our documents—and simply put, the vast majority of the limitations we’re running into are Lemmy’s at this point. An increasing amount of our time is spent trying to work around or against the software to achieve what we want rather than productively building this community. That leaves us with serious questions about our long-term ability to stay on this platform, especially with the lingering prospect of not having the people needed to navigate backend stuff.
Long-time users will no doubt be aware of our advocacy for moderator tools that we think the platform needs (and particularly that we need). Our belief in the importance and necessity of those tools has only hardened with time. Progress of those tools, however—and even organizing work on them—has been pretty much nonexistent outside of our efforts from what we can see.[1] In the three months since we started seriously pushing the ideas we’d like to see, we’re not aware of any of them being seriously considered—much less taken up or on the way to being incorporated into Lemmy.
In fact: even within the framework of Lemmy’s almost nonexistent roadmap and entirely nonexistent timetable on which to expect features it has been made clear to us that improving federation or moderation on the platform are not big priorities.[2] We have implicitly been told that if this part of the software is to improve we will need to organize that from scratch. And we have tried that to be clear. Our proposal is (and has been) paying people bounties for their labor toward implementing these features, in line with paying all labor done on our behalf—but we’ve received mixed messages from the top on whether this would be acceptable. (Unclear guidance and general lack of communication is symptomatic of a lot of our relation with the Lemmy devs in the past few months.)
Things aren’t much better on the non-moderator side of things. The problems with databases are almost too numerous to talk about and even Lemmy’s most ardent supporters recognize this as the biggest issue with the software currently. A complete rewrite is likely the only solution. Technical issues with the codebase are also extensive; we’ve made numerous changes on our side because of that. Many of the things we’re running into have been reported up the chain of command but continue to languish entirely unacknowledged. In some cases bugs, feature requests, and other requests to Lemmy devs have explicitly been blown off—and this is behavior that others have also run into with respect to the project. Only very recently have we seen any overtures at regular communication—and this communication has not hinted at any change in priorities.
All of what was just described has been difficult to get a handle on—and having fewer users, less activity, and more moderators has not done a whole lot to ease that. We honestly find that the more we dig and the more we work to straighten out issues that pop up, the more pop out and the more it feels like Lemmy is structurally unsound for our purposes. (One such example of what we’re working with is provided in the next section.)
In summary: we believe we can either continue to fight the software in basically every way possible, or we can prioritize building the community our documents preach. It is our shared belief that we cannot, in the long-term, do both; in any case, we’re not interested in constantly having to fight for basic priorities—ones we consider extremely beneficial to the health of the overall Lemmy network—or having to unilaterally organize and recruit for their addition to the software. We are hobbyists trying to make a cool space first and foremost, and it’s already a job enough to run the site. We cannot also be surrogates for fixing the software we use.
PenguinCoder: A brief sketch of the technical perspective I’ve said a few words about this topic already, here and here. Other Beehaw admins have also brought some concerns to the Lemmy devs. Those issues still exist. To be clear: this is a volunteer operation and Lemmy is their software; they have a right to pick and choose what goes into it and what to put a priority on. But we have an obligation to keep users safe and secure, and their priorities increasingly stifle our own.
In the case of this happening for open source projects, the consensus is to make your own fork. But:
The problem with forking Lemmy is in starting from all the bad that is inherently there, and trying to make it better. That is way more work than starting fresh with more developers. IE, not using Rust for a web app and UI, better database queries from the start, better logging/functions from the start; not adding on bandaids. A fork of Lemmy will have all of Lemmy’s problems but now you’re responsible for them instead.
We don’t need a fork, we need a solution.
To give just one painful example of where an upstream solution is sorely needed: the federation, blocking, and/or removal of problem images.
You post an image to Beehaw. Beehaw sends your content out to every other server it’s federated with Federated server accepts it (beehaw.org is on their allowlist), or rejects it (beehaw.org is on their denylist) If the server accepts it, a copy of your post or comment including the images are now on that receiving server as well as on the server you posted it to. Federation at work. Mod on beehaw.org sees your post doesn’t follow the rules. Removes it from beehaw.org. The other instances Beehaw pushed this content to, do not get that notice to remove it. The copy of your content on Beehaw was removed. The copy of your content on other servers was not removed. The receiving federated instance needs to manually remove/delete the content from their own server For a text post or comment that’s removed, this can be done via the admin/mod tools on that instance For a post or comment including a thumbnail, uploaded images, etc; that media content is not removed. It’s not tracked where in Lemmy that content was used at. Admin removal of media commences. This requires backend command line and database access, and takes about a dozen steps per image; sometimes more. There are dozens of issues—some bigger, some smaller—like this that we have encountered and have either needed to patch ourselves or have reported up the chain without success.
Alternatives and the way forward If possible the best solution here is to stay on Lemmy—but this is going to require the status quo changing, and we’re unsure of how realistic that is. If we stay on Lemmy, it is probable that we will have to do so by making use of a whitelist.
For the unfamiliar, we currently use a blacklist—by default, we federate with all current and newly-created nodes of the Fediverse unless we explicitly exclude them from interacting with our site. A switch to a whitelist would invert this dynamic: we would not federate with anybody unless we explicitly choose to do so. This has some benefits—maintaining federation in some form; staying on Lemmy; generally causing less entropy than other alternatives, etc. But the drawbacks are also obvious: nearly everything described in this post will continue, blacklist or whitelist, because a huge part of the problem is Lemmy.
Because of that we have discussed almost every conceivable alternative there is to Lemmy. We are interested in the thoughts of this community on platforms you have all used and what our eventual choice is going to be, but we are planning on having more surveys in the future to collect this feedback. We ask that you do not suggest anything to us at this time, and comments with suggestions in this thread will be removed.
As for alternatives we’re seriously considering right now: they’re basically all FOSS; would preserve most aspects of the current experience while giving us less to worry about on the backside of things (and/or lowering the bar for code participation); are pretty much all more mature and feature-rich than Lemmy; and generally seem to avoid the issues we’re talking about at length here. Downsides are varied but the main commonality is lack of federation; entropy in moving; questions of how sustainable they are with our current mod team; and more cosmetic things like customization and modification.
We’re currently investigating the most promising of them in greater depth—but we don’t want to list something and then have to strike it, hence the vagueness. If we make a jump, that will be an informed jump. In any case logistics mean that the timetable here is on the order of months. Don’t expect immediate changes. As things develop, we’ll engage the community on what the path forward is and how to make it as smooth as possible.
Other administrators have probably vocally pushed for these things, but we’re not aware of any public examples we can point to of this taking place. Their advocacy has not produced results that we’re aware of in any case, which is what matters. ↩︎
Perhaps best illustrated by the recent Lemmy dev AMA. We’ll also emphasize that Beehaw’s admin team is not alone in the belief that Lemmy devs do not take mod tools or federation issues particularly seriously. ↩︎
RoundSparrow 1 year ago • 50%
What it comes down to me in May was that after 4 years of coding - if they knew they had scale problems (the queue system of federation and the PostgreSQL were both buggy and performing badly)...
The natural answer was to split the code out. Push more to lemmy-ui, such as adding caching to the API calls for "trending communities" and getSite call to NodeJS caching... something.
If they wanted to maintain their Rust approach to development, create a temporary app to get out of the problems and have a fresh approach. Nginx would allow even specific API paths to be redirected to another application. The read-only post and comment listings, community listings, could have been forked out.
The API is why people left Reddit. and Lemmy had an API and kbin did not have an API.
RoundSparrow 1 year ago • 100%
Clearly people liked many aspects about how Reddit presented information, as an information system. And there has been very little positive discussion on Lemmy about the good and what to keep. It's mostly been hate-filed expressions of "fuck spez" instead of "what worked well and why anyone cared positively in the first place".
Reddit 2013 and earlier was very different, 2013 was the year of Cambridge Analytica engaging populations.
RoundSparrow 1 year ago • 100%
25 years ago... When Islamic societies used hate and anger as ways to motivate street gangs, everyday people criticized the hate and anger.
But now it's become politicians and leaders all over the world in 2023 who are using them - without any need for Islam. Politicians and other leaders have had hate and anger professionally endorsed by Cambridge Analytica medical professionals now for over 10 years.
Again, we used to criticize Islamic people for using hate and anger to form street gangs and followers.
RoundSparrow 1 year ago • 100%
There are people with great social skills... but they aren't becoming leaders away from hate or exploitation of crowds. A social movement towards goodness is long overdue, but it doesn't seem to take hold.
Christianity in USA has degraded to be almost pure anti-science and out-group hate oriented. Sure, this was there all along since 1492 when it came to Americas from Europe. But it has become notably worse since 2012, and people don't seem alarmed that groups can be shifted that way... much like Germany in 1930.
There are no easy ways to measure these things, but there are warning signs when entire populations become motivated by hate and mocking.
RoundSparrow 1 year ago • 100%
On Reddit it became extremely popular to hate on Facebook by 2015, but very few would discuss why or how. It isn't as if Reddit was advertising-free and didn't have documented cases of grass-roots exploitation. The code and management of Reddit put a huge amount of time into trying to prevent vote manipulation (and make it a trade secret) - where none of that seems to be going on with ActivePub platforms. People notice where Reddit fails, but they don't seem to notice how hard the problem really is to solve when nobody cares about real identity.
Facebook people mostly used real names, real houses, real photos with their family. Reddit seems to really hate that for the mainstream audience, and that carries over to Lemmy in 2023.
People don't use fake identities to share secrets about companies by name, instead more often than not fake identities are used to pump garbage and copy old content and present it as new.
It's funny how when people talk about Facebook as bad, they never seem to mention the real identity aspects of many people on it who joined 12 or more years ago. And there is something kind of sick about a society where real identity and real problems have to be hidden to be accepted online. The thugs have kind of won.
YouTube you often know who the person is because so much is presented in the images and audio. Some of the small-time youtubers with only 700 views talking about technical topics are really the kind of sincere and earnest thing that have largely been abandoned.
Surfing memes of billionaires - be it Trump memes from his antics or Hollywood film memes or video games making billions of $ - and their memes... is dangerous. Trump rode on "high energy" and mocks scientific thinking. The crazy shark-frenzy trend-chasing of memes has become the cornerstone of Lemmy.
lemmy has had wave after wave of hate. Hate towards Reddit bring bitter and hate-filled emotions as the central core of Lemmy for many months. And hating on Elon Musk. And hating on this or that. It really has been an emotional Mob Mentality of hating things.
That's the kind of emotion Cambridge Analytica was spelling out to those who wanted to 'lead the masses', aka get votes - was packaging in 2013. Now it's all just accepted, the constant hate as a 'fun topic'. removed all the time.
Cambridge Analytica was well underway in 2013, now 10 years ago. People like to think that just because researchers find x on Twitter and y on Facebook - that that is the clearly documented cases - that the tactics and general psychology didn't copy everywhere. Cambridge Analytica is mostly famous for Facebook... but I don't view their direct targeting of individuals to be the long-term damage. The long-term damage is that they legitimized psycological manipulation, falsehoods, as a form of winning audiences. The were Psychology/Psychiatry professionals who applied human history and experience towards making people believe false things. Like a rebirth of Dr. AA Brill from 1929 on a new scale. The legitimization of it without any ethical uprising...
RoundSparrow 1 year ago • 100%
Self-evident is that the May through August opportunity from Reddit didn't work out, the over 4 years of experience from the key developers just didn't get applied to the project in much time. But there seems to be a recognition of technical issues more instead of just front-end apps / API smartphone apps... so maybe things will progress through the experience people have gained in having the code crash / lacking features.
It isn't the only social media software that isn't progressing, It isn't even just Twitter and Reddit, it's bottom-up society.
RoundSparrow 1 year ago • 100%
https://beehaw.org/post/7618912 dust settles about code over past months
RoundSparrow 1 year ago • 100%
Written 2 weeks ago, pretty interesting: https://literature.cafe/comment/825554
RoundSparrow 1 year ago • 100%
It is the squandered experience of over 4 years of development that I've witnessed the most... the people who knew how to do the required changes to scale the app fed the problem apathy.
The only instance with significant creation activity that isn't all bot content... had to resort to cloudflare due to the data performance... and now the problems with that solution have started to be taken on... https://lemmy.world/post/4366376
RoundSparrow 1 year ago • 100%
"This is how the Fediverse works. There is so much bad practices, so much haphazardly implemented functionality and so much bad API documentation all over the place that I wonder why nothing has extremely exploded so far." - Dirk at lemmy.ml
Dirk's comment is from hee: https://lemmy.world/post/4128651
Dirk is from Germany, not American like I am - and joined the same server I did - creating this site. The core developers left lemmy.ml crashing for months - now it's working better because there is less activity - not because the code scales and is improved.
The terrible SQL from Rust and Diesel was why I never opened shop. I knew lemmy.ml was online for over 4 full years..
Another new front-end was the 2023 priority from all this. July 11 is when they started: https://github.com/LemmyNet/lemmy-ui-leptos
When a dozen independent projects are building front-end apps, the people with over 4 years of experience with the code take all that back-end experience and bottle it up. Instead of actually improving documentation and API testing surface... WITH ALL those YEARS of experience... off to start a new Rust-centered project. The advantage being that Rust can use the same Rust objects... but that doesn't do anything for the front-ends that don't use Rust, the smartphone apps, etc.
RoundSparrow 1 year ago • 100%
"For the longer term, I have some further ideas:
4) Invite-based registrations
I believe that one of the best ways to effectively combat spam and malicious users is to implement an invite system on Lemmy. I have wanted to work on such a system ever since I first set up this instance, but real life and other things have been getting in the way, so I haven’t had a chance. However, with the current situation, I believe this feature is more important then ever, and I’m very hopeful I will be able to make time to work on it very soon.
My idea would be to grant our users a few invites, which would replenish every month if used. An invite will be required to sign up on lemm.ee after that point. The system will keep track of the invite hierarchy, and in extreme cases (such as spambot sign-ups), inviters may be held responsible for rule breaking users they have invited.
While this will certainly create a barrier of entry to signing up on lemm.ee, we are already one of the biggest instances, and I think at this point, such a barrier will do more good than harm."
RoundSparrow 1 year ago • 100%
A new update on the situation: https://lemm.ee/post/5905754
"As shared by the lemmy.world team, over the past few days, some people have been spamming one of their communities with CSAM images. Lemmy has been attacked in various ways before, but this is clearly on a whole new level of depravity, as it’s first and foremost an attack on actual victims of child abuse, in addition to being an attack on the users and admins on Lemmy."
RoundSparrow 1 year ago • 75%
For a 4.5 year old project, Lemmy's two core developers have pushed the idea that corporate media is bad and this is the alternative.
But Lemmy had so little content prior to April 2023... I've see single-topic BBS systems with far more content...
Hate-of-reddit isn't exactly a foundation for original content out of goodness of people's heart. Hate of Threads from Meta, hate of X rename of Twitter. So much anger at Elon Musk, media systems in general that's been expressed on Lemmy these recent months.
RoundSparrow 1 year ago • 100%
looks like other servers shut down image hosting
"It will not possible to upload any new avatars or banners while this limit is in effect."
yha, moderation isn't just for posts and comments, and per-community moderation probably doesn't work so well when new communities can be created easily (the mod being the creator who puts in offensive material). And let's be honest, a lot of what has become routine shitposting and memes is "funny" because it tries to be offensive. Without Lemmy's technical growing pains, that might be able to fit in the puzzle, but now it's just people trying to normalize offense to keep new people from joining and roots from growing.
Reddit had built a ton of IP address and other fingerprinting even 13 years ago - being on an advertising network with partners like Google probably helps in identifying the same computer with multiple accounts...
yesterday .world had to turn off sign-up and even shut down shitposting community. This is basically the front-door of Lemmy. And as others are starting to notice, 60K users after all the people seeking better and trying out things isn't that many.. And there are seemingly a lot of people who use multiple servers given the technical instability of Lemmy's code... I am one of those people who spends 10 minutes a day on 4 servers, but I'm cutting back because content just isn't there and it's now often gaming topics and news making the rounds as duplicate stories over a 2 to 4 day period (besides memes) Social media in general... there was so much Facebook hate for the past 8 years... but not much betterment came of it. Today looking over Reddit, it hasn't really changed that much in the past 4 months... there was a group of dissatisfied people who don't seem to want to actually build something better - just want to protest Reddit. YouTube and TV advertising - that's a huge topic. YouTube does have a lot of small-time original creators, but is the money the reason why? You can''t make money on Reddit or Lemmy unless you have a business shop or something related to specialty topics (such as auto repair in a discussion community about same).
RoundSparrow 1 year ago • 100%
Unedited comment
RoundSparrow 1 year ago • 100%
comment
EDITED 0
RoundSparrow 1 year ago • 100%
Broken URL links because untested HTML sanitation... that then goes into a release and for weeks has been corrupting data.
At the same time, another change went in with how deleted and removed comments are delivered to clients. And if a person deletes a comment, now all the replies below that comment - even from other people - are no longer shown.
This is a fundamental data issue of the application! A change is made with the internal Rust code logic on how comments are deleted - and no client-side testing is done to make sure there are no side effects.
If B and C reply to A, and A deletes their comment, they all 3 have their comments black-holed by Lemmy. But an admin logged in would not see the change. But the change was made in the Rust code... the developers did not test it as normal end-users of the website... and they do not seem to login on Beehaw or other sites just to check the health and use of the application. It's like a business that never visits their customers and see what their engine is being used for. And it seems it has been that way for years...
Data doesn't matter... that's the attitude. People's comments just disappearing isn't noticed.
RoundSparrow 1 year ago • 100%
Managing data in 4 year old lemmy code...
There is an option in admin to purge data in a community. The UL isn't built for long-running SQL statements, so it is likely to not return after pressing the button if there are more than a couple thousands posts in the community... which is likely the reason one would purge it.
But the whole separation of local from non-local that Lemmy uses in the database. The purge has no option to preserve locally created data. So comments and posts from your local users get purged along with the community you followed from a remote server.
So if you follow memes@lemmy.ml - a very active community, one of the highest number of posts and comments in the Lemmy network - and Lemmy is crashing because of the poorly performing SQL code - you might opt to purge your local instance copy of that community to reduce the PostgreSQL crashes and storage consumption. A perfectly natural thing to need to do to manage a server running for years like lemmy.ml or Beehaw has....
Without an option to preserve posts and comments with local content, that means you are deleting what a user on your instance has created. it will disappear from their profile, they may go back looking for a copy of a post the created a couple weeks ago - and it's just gone! Your local instance may have only created 300 of of the 10,000 posts in that community - there is no option to preserve them or even not remove posts that your users had commented on.
This is a data-centered application, but it shows no learning of the kind of things a 4.5 year old Internet website and development project would show. And the developers who create the site do not seem to use Lemmy to even discuss moderation, tips for new instance operators, programming issues or bugs... Lemmy as a data and information system is not something they feel is up to the task or useful.
It isn't just the constant database crashes in Lemmy, GitHub issue 2910... https://github.com/LemmyNet/lemmy/pull/3708 On July 24, sanitation of HTML was added to the code. But the testing was not called for and it broken titles of postings, link parameter ampersands, discussion of programming code in code blocks It's data... and now it's very difficult to undo all the damaged data that has been put into the database for weeks now. Lemmy is a Link aggregator, and it damages Links now... the ampersand parameter deliminator in URL links is now broken because of this code not being tested. Why wasn't there a call for testing to something that was going to alter every new post and comment from both federation and Lemmy itself? how did such obvious things such as a ? parameter list in URL get overlooked... and then new bugfix release comes out after this was known as an issue - and still not fixed. Database crashing that results in lost data from unsaved post and comments, failure to deliver Federation data without any way client or server operators are notified, and damaged data as fundamental as URL website links... I'm all for code changes gong in fast, but the lack of actually testing things and spot-checking on Lemmy instead of just changing Rust code without really realizing that a link aggregator uses ampersand in URL links... and not asking people to help think of side-effects... Development process could even ask just a couple sites with more attentive operators to try out the code for a few days and ask people to report any problems before advising all sites to upgrade and break their URL links.
RoundSparrow 1 year ago • 100%
do you get this comment reply?
RoundSparrow 1 year ago • 100%
have a good weekend
RoundSparrow 1 year ago • 100%
test a bc
RoundSparrow 1 year ago • 100%
https://github.com/derivator/tafkars
This API proxy approach could be useful for more intelligent rate-filtering than built-in Lemmy has, API redirection for specific calls, and even the basis for spam filtering. I haven't seen people remark about the lack of spam on lemmy. On Reddt, I've seen routine bots hit communities with t-shirt selling spam, etc. I wonder if other parts of the federated network have had to implement spam filtering.
I had hoped to be able to do this with mostly API tricks and leveraging existing data structures within Lemmy's database... but I think it's proving that August 2023 isn't the right timing. I learned a lot by prototyping this and thinking about multi-person editing like moderators can do in a community...
RoundSparrow 1 year ago • 100%
I see you seek this kind of participation out. "On the internet, not everyone knows you’re an idiot." being your profile statement. And that I'm not the first Lemmy community you have come along to concerning your copyright topics. Are you being paid by copyright holders to do this or something? Is it is some project or business to make USA copyright convention a world wide standard, ignoring that even in Joyce's home focus of Ireland the work is no longer copyrighted?
Going around openly saying you are out to demonstrate other people are idiots... I think is a pretty well paved path to try and drag down societies in total.
“The chief deficiency I see in the skeptical movement is its polarization: Us vs. Them — the sense that we have a monopoly on the truth; that those other people who believe in all these stupid doctrines are morons; that if you're sensible, you'll listen to us; and if not, to hell with you. This is nonconstructive. It does not get our message across. It condemns us to permanent minority status.”
― Carl Sagan, The Demon-Haunted World: Science as a Candle in the Dark
RoundSparrow 1 year ago • 100%
Hello. I can help you try to understand, perhaps I can rephrase it. I have brain damage and my mental health is not that great, communication is a constant struggle for me.
- Beehaw has been around since January 2022 running Lemmy - well over a year before the Reddit surge
- Lemmy has major problems with scalability and causing sever crashes, notably I talked about GitHub issue 2910 opened on June 4, 2023
- Beehaw crashed daily - and nothing was done about the underlying problem in the code while critical weeks went by
- I have a lot of regret for watching this happen all June
- There was a small project on June 7 that was about making an API proxy that I feel I was distracted from and I regret being distracted.
- I am trying to make sense of why I underestimated all this and find the problems in my brain so I don't repeat it.
This is sharing of open thoughts... I don't have any faith in these words being something others are seeking out. It's exactly the kind of navel-gazing a lot of people find extremely repulsive. Where I'm living, people find the words of Donald Trump irresistible and repeatable, up to and including every other member of my family. I have no doubts that my perspective on what images and patterns of words people desire is way out from what many are seeking. I know well I'm in an echo chamber...
RoundSparrow 1 year ago • 50%
Naughty naughty! Look, I like what you are doing but you should be aware if you aren’t already that you are posting copywritten material.
It was copyrighted at one time....
These works go into the public domain in 2035,
Are you sure about that? Do you know about Europe's copyright dates? And further, are you basing that on 1939 copyright date... when I'm posting content from a decade earlier, 1928?
RoundSparrow 1 year ago • 100%
My regrets compounded when I sort of forgot about https://github.com/derivator/tafkars like everyone else did by early July... a month after it had been created... and it would have been a way for me to channel my skills instead of hoping the situation with Issue 2910 would turn around quickly. Even after 30 days, a few-hour fix to 2910 hadn't been put in.
Did I get caught up in all the "Fuck Spez" negativity of Lemmy community? Beehaw was the most positive and had been up for 17 months with their positive approach. Did I get sucked into the hate of Reddit and hate of Elon Musk emotions and not see it?
I really regret when I go back and see the June 7 creation of https://github.com/derivator/tafkars - that I didn't either think of it myself or jump in with contributions to a fully independent project that would offer a solution that didn't require the two entrenched developers of lemmy_server to change their pace or focus. Beehaw was on fire, and tafkars project would at least have been a way to view all this from an API perspective.
Did the negativity of hating Spez and corporate power - even the massive hate that everyone was screaming on Lemmy platform about Zuckerberg and "Threads" coming along on July 5... did it get into my head?
- May 20 2023 - a huge amount of hate surging with "Fuck Spez" and mod community planned outages protest
- June 30 the massive community hate towards Reddit
- July 5 - Zuckerberg and Threads. Massive hate response from the Lemmy platform.
- July 23 - Elon Musk pulls another massive change, the Twitter to X rename - a world-wide mind-fuck given how many news organizations have made Twitter one of the most-repeated words on the planet.
I should have been reading my Finnegans Wake and keeping my mind clear. The Reddit HiveMind clashes, the Lemmy platform HiveMind hate towards Threads and Twitter....
Beehaw is like a lighthouse in all the hate-oriented surges of people motivated by anger and hate, and I see now I lost my way in the competing waves of hate-focused HiveMind reactions.
RoundSparrow 1 year ago • 100%
Beehaw didn't really have that much data, they had a well-organized and decorated set of around 10 communities, they had built up a standard of content for over a year... and it just got smashed by the performance problems of even slight growth of data in the post, comments, and federated communities. Tthe site_aggregates UPDATE bug was hammering away too.. with nobody fixing and digging for similar TRIGGER logic problems that June 4's issue 2910 called out.
I regret that I put too much faith in open source ideals, that surely Issue 2910 was explicit enough - and no June 13 hardware upgrade is going to fix such faulty logic. There's two active people who were the ones who approved the code in the first place, they are there every workday, it takes only a few hours - even with testing - to get the faulty SQL trigger entirely removed or fix the logic. I don't know if I'll ever understand how Issue 2910 played out from June 4 to June 30 Reddit deadline, it still seems to be one of the oddest things I've witnessed... to see Beehaw in constant turmoil week after week over what amounts to an easily patched-out or fixed fault in the foundation of the code.
If I could go back to June 4, I would have better focused to this development project had been going on for well over 4 full years of active development and operations of lemmy.ml as an Internet website. I would just keep on eye on that one single Issue 2910 and take on a part of adding some tools to better document the performance of the API.
It crossed my mind, June 4 inspired me to install BulletinTree.com testing main GitHub code merges on June 8, but I painfully see now that should have focused on a small project that came up that most people ignored, but I didn't... right there on June 7.... https://github.com/derivator/tafkars
I regret I didn't take the idea of what tafkars had built and make a proxy agent for the Lemmy API. Start metering the Lemmy API performance response and format the data so that visualization tools could be used. maybe even add nginx proxy log processing as an alternate means to capture data if people didn't want to put an API proxy in place. But there are things the API proxy could do: respond to API calls with a useful error instead of just leave clients with no response or nginx timeout. And the API could even be coded as an emergency-fallback to go pull data directly form PostgreSQL if needed. And building it like tafkars does would require no disturbance of the two developers who had been building lemmy_server for over 4 years.
How did I not see this coming? on June 4 I thought that by June 26 such easily fixed issues like 2910 would be addressed and rolled out... the constant fires burning over at Beehaw were flashing red and the slow-motion train-wreck of it all kept playing out. Beehaw did their best to keep their chins up, but it had to have been a bad experience to welcome people and have it all unfold the way it did.
I canceled my plans for a general purpose Lemmy social media site, the code and network peers were so unstable because of Issue 2910 and similar problems. I had hoped to have a general BBS system, which is what I named Bulletin Tree (BBS reference) for. And instead I saw Beehaw which had been running for 17 months blowing up and having to put up new error messages on their home page...
regrets, no fun :(
June 4, 2023 is when I felt I had to get involved. And June 8, 2023 is when I crated my own testing-focused experimental Lemmy install that compiled Main from GitHub source and ready to test the changes I thought were surely going to come to the SQL because of GitHub issue 2910. I wanted to test the code that that developers who had been working and running lemmy.ml for over 4 full years - would surely address. It was June 4 with Issue 2910, the June 30 Reddit API cutoff deadline countdown was well under way. Lemmy.ml put in major hardware upgrades on June 13, 2023 - and I was puzzled why such an easy 2 or 3 hour fix for Issue 2910 wasn't put in... but I still had hope that everyone would see the pending countdown to June 30 API deadline and a fix could go in within 10 days - by June 23... for some slack time before June 30.. Watching Beehaw, up and running for 17 months on Lemmy - crashing constantly... I thought, surely the developers were seeing Issue 2910 happening over there... but June 28 came, June 29 came, June 30... nothing. With 4 years of experience on the Rust code base and such, they were the ones to fix Issue 2910.... but from June 4 to June 30, it just didn't happen.
part so ptee does duty for the holos we soon grow to use of an allforabit. Here (please to stoop) are selveran cued peteet peas of quite a pecuniar interest inaslittle as they are the pellets that make the tomtummy's pay roll. Right rank ragnar rocks and with these rox orangotangos rangled rough and rightgorong. Wisha, wisha, whydidtha? Thik is for thorn that's thuck in its thoil like thum- fool's thraitor thrust for vengeance. What a mnice old mness it all mnakes! A middenhide hoard of objects! Olives, beets, kim- mells, dollies, alfrids, beatties, cormacks and daltons. Owlets' eegs (O stoop to please!) are here, creakish from age and all now quite epsilene, and oldwolldy wobblewers, haudworth a wipe o grass. Sss! See the snake wurrums everyside! Our durlbin is sworming in sneaks. They came to our island from triangular Toucheaterre beyond the wet prairie rared up in the midst of the cargon of prohibitive pomefructs but along landed Paddy Wip- pingham and the his garbagecans cotched the creeps of them pricker than our whosethere outofman could quick up her whats- thats. Somedivide and sumthelot but the tally turns round the same balifuson. Racketeers and bottloggers. Axe on thwacks on thracks, axenwise. One by one place one be three dittoh and one before. Two nursus one make a plaus- ible free and idim behind. Starting off with a big boaboa and three- legged calvers and ivargraine jadesses with a message in their mouths. And a hundreadfilled unleavenweight of liberorumqueue to con an we can till allhorrors eve. What a meanderthalltale to unfurl and with what an end in view of squattor and anntisquattor and postproneauntisquattor! To say too us to be every tim, nick and larry of us, sons of the sod, sons, littlesons, yea and lealittle- sons, when usses not to be, every sue, siss and sally of us, dugters of Nan! Accusative ahnsire! Damadam to infinities! True there was in nillohs dieybos as yet no lumpend papeer in the waste, and mightmountain Penn still groaned for the micies to let flee. All was of ancientry. You gave me a boot (signs on it!) and I ate the wind. I quizzed you a quid (with for what?) and you went to the quod. But the world, mind, is, was and will be writing its own wrunes for ever, man, on all matters that fall
RoundSparrow 1 year ago • 100%
I can understand. Best of luck on what you do next.
RoundSparrow 1 year ago • 100%
take care.
RoundSparrow 1 year ago • 100%
If you truly start your site over with empty database... your post and comment id numbers and other things will clash... which kind of creates a mess. And obviously user accounts all have to be re-created. Sorry you ran into this mess.
Jute. 'Zmorde! Mutt. Meldundleize! By the fearse wave behoughted. Des- pond's sung. And thanacestross mound have swollup them all. This ourth of years is not save brickdust and being humus the same roturns. He who runes may rede it on all fours. O'c'stle, n'wc'stle, tr'c'stle, crumbling! Sell me sooth the fare for Humblin! Hum- blady Fair. But speak it allsosiftly, moulder! Be in your whisht! Jute. Whysht? Mutt. The gyant Forficules with Amni the fay. Jute. Howe? Mutt. Here is viceking's graab. Jute. Hwaad! Mutt. Ore you astoneaged, jute you? Jute. Oye am thonthorstrok, thing mud. (Stoop) if you are abcedminded, to this claybook, what curios of signs (please stoop), in this allaphbed! Can you rede (since We and Thou had it out already) its world? It is the same told of all. Many. Miscegenations on miscegenations. Tieckle. They lived und laughed ant loved end left. Forsin. Thy thingdome is given to the Meades and Porsons. The meandertale, aloss and again, of our old Heidenburgh in the days when Head-in-Clouds walked the earth. In the ignorance that implies impression that knits knowledge that finds the nameform that whets the wits that convey contacts that sweeten sensation that drives desire that adheres to attachment that dogs death that *removed* birth that en- tails the ensuance of existentiality. But with a rush out of his navel reaching the reredos of Ramasbatham. A terricolous vively- onview this; queer and it continues to be quaky. A hatch, a celt, an earshare the pourquose of which was to cassay the earthcrust at all of hours, furrowards, bagawards, like yoxen at the turnpaht. Here say figurines billycoose arming and mounting. Mounting and arming bellicose figurines see here. Futhorc, this liffle effingee is for a firefing called a flintforfall. Face at the eased! O I fay! Face at the waist! Ho, you fie! Upwap and dump em, ace to ace! When
Lemmy instance Beehaw staff on Monday, August 21 2023.... https://beehaw.org/comment/1018508 "From where I’m standing, I can’t really much has changed unfortunately… which really sucks… Lemmy.world has grown substantially meanwhile the moderation tools have not improved at all. All I can say about the moderation tools is that we now know that the tools suck more than they used to. Here’s a list of ***moderation problems*** that we have discovered since then: * If a Berson is reported on another instance, we never get the report. * If a mod is banned from the community they mod, they can still take mod actions * If you get site-banned from Beehaw while you are from another instance, you can still post on the community and people from that instance and kbin can see your posts * People from other instances can’t know who if someone is an admin on the instance they’re interacting with * People from other instances can’t see when we use the shield function to signal we’re talking “officially / as a mod” * The modlog is not chronological * The modlog breaks if you ban someone for more than 4 digit days. A banned user’s description is still visible so if they link to a scat image in their description, it is still visible to moderators. Despite these newly known problems, there have been exactly no improvement whatsoever to the moderation tools. It is honestly unsettling and terrifying." Context: Lemmyy has been on GitHub and in production at Lemmy.ml for over 4 years for the purposes of running and moderating a message forum / link aggregator. Beehaw has been online for over a year before the May 2023 Reddit influx.
where the liveries, Monomark. There where the mis- sers moony, Minnikin passe. Jute. Simply because as Taciturn pretells, our wrongstory- shortener, he dumptied the wholeborrow of rubba- ges on to soil here. Mutt. Just how a puddinstone inat the brookcells by a riverpool. Jute. Load Allmarshy! Wid wad for a norse like? Mutt. Somular with a bull on a clompturf. Rooks roarum rex roome! I could snore to him of the spumy horn, with his woolseley side in, by the neck I am sutton on, did Brian d' of Linn. Jute. Boildoyle and rawhoney on me when I can beuraly forsstand a weird from sturk to finnic in such a pat- what as your rutterdamrotter. Onheard of and um- scene! Gut aftermeal! See you doomed. Mutt. Quite agreem. Bussave a sec. Walk a dunblink roundward this albutisle and you skull see how olde ye plaine of my Elters, hunfree and ours, where wone to wail whimbrel to peewee o'er the saltings, where wilby citie by law of isthmon, where by a droit of signory, icefloe was from his Inn the Byggning to whose Finishthere Punct. Let erehim ruhmuhrmuhr. Mearmerge two races, swete and brack. Morthering rue. Hither, craching eastuards, they are in surgence: hence, cool at ebb, they requiesce. Countlessness of livestories have netherfallen by this plage, flick as flowflakes, litters from aloft, like a waast wizzard all of whirlworlds. Now are all tombed to the mound, isges to isges, erde from erde. Pride, O pride, thy prize! Jute. 'Stench! Mutt. Fiatfuit! Hereinunder lyethey. Llarge by the smal an' everynight life olso th'estrange, babylone the great- grandhotelled with tit tit tittlehouse, alp on earwig, drukn on ild, likeas equal to anequal in this sound seemetery which iz leebez luv.
ORM and SQL .. I mean it's lived up to the bad side of the reputation. It hides it. As someone said here: "Osiris on June 18, 2021 | unvote | parent | context | favorite | on: DenoDB I hate ORMs with the fury of a thousand suns. The problem is that I know SQL but now I have to spend a bunch of time trying to figure out how to convert SQL into ORM X just so it can convert it back to inefficient SQL. SQL mostly translates between various databases but ORMs are unique and you have to learn a new API for each one. I'm on a project using TypeORM and it has been fantastic at helping developers on my team make really bad schemas due to not understanding how to use TypeORM to make the right relationships. Currently I'm looking at pg-types because you just write SQL and it just helps by making some TypeScript types for you. (I have used ORMs in C#, PHP, and JavaScript and I hate all of them)." https://news.ycombinator.com/item?id=27547163
Unbelievable today the push-back on filtering by what is in-essence, the entire key to lemmy - published date
froriose. What a quhare soort of a mahan. It is evident the mich- indaddy. Lets we overstep his fire defences and these kraals of slitsucked marrogbones. (Cave!) He can prapsposterus the pil- lory way to Hirculos pillar. Come on, fool porterfull, hosiered women blown monk sewer? Scuse us, chorley guy! You toller- day donsk? N. You tolkatiff scowegian? Nn. You spigotty an- glease? Nnn. You phonio saxo? Nnnn. Clear all so! 'Tis a Jute. Let us swop hats and excheck a few strong verbs weak oach ea- ther yapyazzard abast the blooty creeks. Jute. Yutah! Mutt. Mukk's pleasurad. Jute. Are you jeff? Mutt. Somehards. Jute. But you are not jeffmute? Mutt. Noho. Only an utterer. Jute. Whoa? Whoat is the mutter with you? Mutt. I became a stun a stummer. Jute. What a hauhauhauhaudibble thing, to be cause! How, Mutt? Mutt. Aput the buttle, surd. Jute. Whose poddle? Wherein? Mutt. The Inns of Dungtarf where Used awe to be he. Jute. You that side your voise are almost inedible to me. Become a bitskin more wiseable, as if I were you. Mutt. Has? Has at? Hasatency? Urp, Boohooru! Booru Usurp! I trumple from rath in mine mines when I rimimirim! Jute. One eyegonblack. Bisons is bisons. Let me fore all your hasitancy cross your qualm with trink gilt. Here have sylvan coyne, a piece of oak. Ghinees hies good for you. Mutt. Louee, louee! How wooden I not know it, the intel- lible greytcloak of Cedric Silkyshag! Cead mealy faulty rices for one dabblin bar. Old grilsy growlsy! He was poached on in that eggtentical spot. Here
I've been pondering the way language works as an attribute in community. Right now there are two attributes to highlight: NSFW and "only moderators can post". There is an active pull request to add "only the home instance can allow posting", sort of a variation on the "only moderators" can post: https://github.com/LemmyNet/lemmy/pull/3889 Which is the 20 source file changes for the new feature. I envision that new attributes will keep coming up, and I see need for an additonal one to make cleaner the [!multipass@bulletintree.com](https://bulletintree.com/c/multipass) feature. # Observation A general 'attributes' table could be created like the existing language table. And then duplicate the logic in Community Edit for picking the languages associated with a community... except you are picking the attributes associated with a community. This could possibly cut down on the amount of lemmy_server code changes for each new attribute? I envision in the future there will be 'members only can post' (subscribed only), and variations of NSFW that people want to implement... and it could be done by not having to add new PostgreSQL columns to tables... and just a general scheme to insert a new registered attribute ID...
The design will route around and avoid ANY sharing of any personal information that is already in Lemmy. I don't want to get into new user preferences for opt-in - too many Rust changes and API changes that front-ends would have to implement. I'm specifically trying to make this project small enough that it can be implemented.
the duskrose has choosed out Goatstown's hedges, twolips have pressed togatherthem by sweet Rush, townland of twinedlights, the whitethorn and the redthorn have fairygeyed the mayvalleys of Knockmaroon, and, though for rings round them, during a chiliad of perihelygangs, the Formoreans have brittled the too- ath of the Danes and the Oxman has been pestered by the Fire- bugs and the Joynts have thrown up jerrybuilding to the Kevan- ses and Little on the Green is childsfather to the City (Year! Year! And laughtears!), these paxsealing buttonholes have quad- rilled across the centuries and whiff now whafft to us, fresh and made-of-all-smiles as, on the eve of Killallwho. The babbelers with their thangas vain have been (confusium hold them!) they were and went; thigging thugs were and hou- hnhymn songtoms were and comely norgels were and pollyfool fiansees. Menn have thawed, clerks have surssurhummed, the blond has sought of the brune: Elsekiss thou may, mean Kerry piggy?: and the duncledames have countered with the hellish fel- lows: Who ails tongue coddeau, aspace of dumbillsilly? And they fell upong one another: and themselves they have fallen. And still nowanights and by nights of yore do all bold floras of the field to their shyfaun lovers say only: Cull me ere I wilt to thee!: and, but a little later: Pluck me whilst I blush! Well may they wilt, marry, and profusedly blush, be troth! For that saying is as old as the howitts. Lave a whale a while in a whillbarrow (isn't it the truath I'm tallin ye?) to have fins and flippers that shimmy and shake. Tim Timmycan timped hir, tampting Tam. Fleppety! Flippety! Fleapow! Hop! In the name of Anem this carl on the kopje in pelted thongs a parth a lone who the joebiggar be he? Forshapen his pigmaid hoagshead, shroonk his plodsfoot. He hath locktoes, this short- shins, and, Obeold that's pectoral, his mammamuscles most mousterious. It is slaking nuncheon out of some thing's brain pan. Me seemeth a dragon man. He is almonthst on the kiep fief by here, is Comestipple Sacksoun, be it junipery or febrew- ery, marracks or alebrill or the ramping riots of pouriose and
https://stackoverflow.com/questions/74295698/how-to-make-a-select-where-exists-query-with-diesel
When reading news, I want to know which website goes with the headline... just seeing a link to archive.org doesn't give that information. Cross-posting should be based on source URL, not the various archive sites hosting copies.
hadde a wickered Kish for to hale dead turves from the bog look- it under the blay of her Kish as she ran for to sothisfeige her cow- rieosity and be me sawl but she found hersell sackvulle of swart goody quickenshoon and small illigant brogues, so rich in sweat. Blurry works at Hurdlesford. (Silent.) 566 A.D. At this time it fell out that a brazenlockt damsel grieved (sobralasolas!) because that Puppette her minion was ravisht of her by the ogre Puropeus Pious. Bloody wars in Ballyaughacleeagh- bally. 1132. A.D. Two sons at an hour were born until a goodman and his hag. These sons called themselves Caddy and Primas. Primas was a santryman and drilled all decent people. Caddy went to Winehouse and wrote o peace a farce. Blotty words for Dublin. Somewhere, parently, in the ginnandgo gap between antedilu- vious and annadominant the copyist must have fled with his scroll. The billy flood rose or an elk charged him or the sultrup worldwright from the excelsissimost empyrean (bolt, in sum) earthspake or the Dannamen gallous banged pan the bliddy du- ran. A scribicide then and there is led off under old's code with some fine covered by six marks or ninepins in metalmen for the sake of his labour's dross while it will be only now and again in our rear of o'er era, as an upshoot of military and civil engage- ments, that a gynecure was let on to the scuffold for taking that same fine sum covertly by meddlement with the drawers of his neighbour's safe. Now after all that farfatch'd and peragrine or dingnant or clere lift we our ears, eyes of the darkness, from the tome of Liber Li- vidus and, (toh!), how paisibly eirenical, all dimmering dunes and gloamering glades, selfstretches afore us our fredeland's plain! Lean neath stone pine the pastor lies with his crook; young pric- ket by pricket's sister nibbleth on returned viridities; amaid her rocking grasses the herb trinity shams lowliness; skyup is of ever- grey. Thus, too, for donkey's years. Since the bouts of Hebear and Hairyman the cornflowers have been staying at Ballymun,
Yes, inspired by... https://www.youtube.com/watch?v=9jWGbvemTag ------------------------------ ---------------------------------- Lemmy MultipPass is a proposal to implement a system for: 1) sharing subscribed communities list publicly. 2) Creating specific MultiPass community lists that are not owned by any one person but instead managed like a Community with multiple moderators. You may know the concept of “MultiPass” as “MultiReddit”, multiple subreddit viewing. Basically a way to build a subscribe community list that is shared. Right now, Lemmy 0.18.4 era has only you personal subscribe list or a single community.
sound of Irish sense. Really? Here English might be seen. Royally? One sovereign punned to petery pence. Regally? The silence speaks the scene. Fake! So This Is Dyoublong? Hush! Caution! Echoland! How charmingly exquisite! It reminds you of the outwashed engravure that we used to be blurring on the blotchwall of his innkempt house. Used they? (I am sure that tiring chabelshovel- ler with the mujikal chocolat box, Miry Mitchel, is listening) I say, the remains of the outworn gravemure where used to be blurried the Ptollmens of the Incabus. Used we? (He is only pre- tendant to be stugging at the jubalee harp from a second existed lishener, Fiery Farrelly.) It is well known. Lokk for himself and see the old butte new. Dbln. W. K. O. O. Hear? By the mauso- lime wall. Fimfim fimfim. With a grand funferall. Fumfum fum- fum. 'Tis optophone which ontophanes. List! Wheatstone's magic lyer. They will be tuggling foriver. They will be lichening for allof. They will be pretumbling forover. The harpsdischord shall be theirs for ollaves. Four things therefore, saith our herodotary Mammon Lujius in his grand old historiorum, wrote near Boriorum, bluest book in baile's annals, f. t. in Dyffinarsky ne'er sall fail til heathersmoke and cloudweed Eire's ile sall pall. And here now they are, the fear of um. T. Totities! Unum. (Adar.) A bulbenboss surmounted up- on an alderman. Ay, ay! Duum. (Nizam.) A shoe on a puir old wobban. Ah, ho! Triom. (Tamuz.) An auburn mayde, o'brine a'bride, to be desarted. Adear, adear! Quodlibus. (Marchessvan.) A penn no weightier nor a polepost. And so. And all. (Succoth.) So, how idlers' wind turning pages on pages, as innocens with anaclete play popeye antipop, the leaves of the living in the boke of the deeds, annals of themselves timing the cycles of events grand and national, bring fassilwise to pass how. 1132 A.D. Men like to ants or emmets wondern upon a groot hwide Whallfisk which lay in a Runnel. Blubby wares upat Ub- lanium. 566 A.D. On Baalfire's night of this year after deluge a crone that
Ok, taking a total fresh approach based on all the months I've been reading people's suggestions and [!lemmywishlist@lemmy.ml](https://lemmy.ml/c/lemmywishlist) kind of things.... # All / All Remote / Local / Remote Specific-Isntance I think server operators should at minimum want the ability to view Remote-only, and even per-instance. Further, I think proxy of API to a community should be something to head towards... where a Lemmy API call can be forwarded as an API call on another Lemmy server for a specific community. # Small, Medium, Large, Trending, Featured Community Some stock multi-community lists, some of which are dynamically generated like Small / Medium / Large based on number of active posts, users, or other tunable parameters. Encourage people to engage in topics that they normally would not see... # Multi-community sharing I think foundation is that it should use words and not numbers. Right now, the entire Lemmy system is built upon using localized index numbers for community. Even if it just becomes a JSON blob to throw into PostgreSQL and recall by name... Maybe have them like communities. And people can subscribe/unsubscribe to a specific list. And the list can have moderators who regulate it (editors). And an option to clone a list to new name. /mc/ multi-community, name. And no ID numbers. A Trigger or something would have to build the ID numbers in the background. And a browser of these, much like communities are browsed... and maybe even voting on them. Lemmy doesn't have voting on communities - subscribe alone - but sometimes you don't want to subscribe because they have too much content - but you would still vote for it or recommend it.
Weeks ago I had my moment of facing the attitude of keeping all this secret. Just casually mention join_collapse_limit was tried behind-the scenes a month ago, then why are there zero post or comments in the entire Lemmy search for join_collapse_limit? I searched the entire GitHub project - no mention of join_collapse_limit. But Ready on the Spot to reveal the secret private communications tried join_collapse_limit log ago. You know what join_collapse_limit is telling yo8u? Too many JOIN is a performance problem! The entire ORM Rust code and reliance on new JOIN is going to lead to other unpredictable performance problems that varies when there are 10,000 posts vs 2 million posts! And that's exactly the history of 2023... watching the code performance wildly swing based on the size of communities being queried, etc. What I see is that pull request for ideas get created only after noise is made on a subject. There is a lack of openness to make mistakes in public. For me,** the server crashes are what annoys me**, not human beings working on solutions. But for most of the people on the project, what seems to anthem is needing to have proper tabs vs. spaces on source code and even adding layers of SQL formatting tools in the middle of what clearly can be described as an SQL performance crisis. Things keep getting broken: the HTML sanitation took a few hours to add to the project but now weeks of broken titles, HTML code blocks, even URL parameters are now broken on everyday links. The changes to delete behavior have orphaned comments and that has gone on for weeks now.
Instead of tied to a person, a block or subscribe list would be a sharable entity. Special virtual lists: 1. All local 2. All remote 3. All local + remote 4. None 5. NSFW 6. Other than NSFW 7. Private community 8. Other than Private community
Reddit traditionally did not purge comments and posts when a user deleted their account. Prior to the API protest in May/June 2023, it was common to encounter posts and comments by [deleted] that were still fully readable. Lemmy has encouraged total deletion of content upon account removal. I think a community should have retention policy: 1. How much old data to retain for performance reasons. communities like memes seem to churn and repeat content in variations - do people really read memes from 60 days ago? 2. Allow retention in technical and specialized topics for search engine / historic stability. A policy that 'posting in this community will not be deleted upon account deletion'. Maybe the user has to consent to this with a prompt on their first post or comment? 3. Remote instances may not want to retain years of content and purge it to only keep the most recent 30 or 60 days for storage and liability reasons, etc. So settings per-community on retention / automatic removal....
Some learning about JOIN filled queries like the SELECT that is used to list post_aggregates table when browsing postings on Lemmy. https://dba.stackexchange.com/questions/155972/postgres-join-conditions-vs-where-conditions "Logically, it makes no difference at all whether you place conditions in the join clause of an INNER JOIN or the WHERE clause of the same SELECT. The effect is the same. (Not the case for OUTER JOIN!)" Learning about join_collapse_limit
for in the byways of high improvidence that's what makes life- work leaving and the world's a cell for citters to cit in. Let young wimman run away with the story and let young min talk smooth behind the butteler's back. She knows her knight's duty while Luntum sleeps. Did ye save any tin? says he. Did I what? with a grin says she. And we all like a marriedann because she is mer- cenary. Though the length of the land lies under liquidation (floote!) and there's nare a hairbrow nor an eyebush on this glau- brous phace of Herrschuft Whatarwelter she'll loan a vesta and hire some peat and sarch the shores her cockles to heat and she'll do all a turfwoman can to piff the business on. Paff. To puff the blaziness on. Poffpoff. And even if Humpty shell fall frumpty times as awkward again in the beardsboosoloom of all our grand remonstrancers there'll be iggs for the brekkers come to mourn- him, sunny side up with care. So true is it that therewhere's a turnover the tay is wet too and when you think you ketch sight of a hind make sure but you're cocked by a hin. Then as she is on her behaviourite job of quainance bandy, fruting for firstlings and taking her tithe, we may take our review of the two mounds to see nothing of the himples here as at else- where, by sixes and sevens, like so many heegills and collines, sitton aroont, scentbreeched ant somepotreek, in their swisha- wish satins and their taffetaffe tights, playing Wharton's Folly, at a treepurty on the planko in the purk. Stand up, mickos! Make strake for minnas! By order, Nicholas Proud. We may see and hear nothing if we choose of the shortlegged bergins off Corkhill or the bergamoors of Arbourhill or the bergagambols of Summerhill or the bergincellies of Miseryhill or the country- bossed bergones of Constitutionhill though every crowd has its several tones and every trade has its clever mechanics and each harmonical has a point of its own, Olaf's on the rise and Ivor's on the lift and Sitric's place's between them. But all they are all there scraping along to sneeze out a likelihood that will solve and salve life's robulous rebus, hopping round his middle like kippers on a griddle, O, as he lays dormont from the macroborg of Holdhard to the microbirg of Pied de Poudre. Behove this
Lemmy's PostgreSQL was developed with this philosophy, intentional or otherwise: 1. Real-time client connection and notification via websocket that gets every single action that passes through PostgreSQL. One upvote, instantly sent to client. One new comment, instantly appeared on Lemmy-ui with version 0.17.4 2. INSERT overhead for PostgreSQL. As soon as a Lemmy post or comment is done, a parallel post_aggregate and comment_aggregate row is created. 3. INSERT counting overhead. Extreme effort is made by Lemmy to count things, all the time. Every new INSERT of a comment or post does a real-time update of the total server count. This is done via a SQL UPDATE and not by just issuing a COUNT(*) on the rows when the data is requested. 4. No archiving or secondary storage concept. PostgreSQL has it in the main tables or nothing. 5. Raw numbers, local and unique for each instance, for comment and post. But community name and username tend to be more known than raw numbers. 6. Sorting choices presented on many things: communities, posts, comments. And new methods of sorting and slicing the data keep being added in 2023. 7. No caching of data. The developers of lemmy have gone to extremes to avoid caching on either lemmy-ui or within the Rust code of lemmy_server. Lemmy philosophy favors putting constant connection to a single PostgreSQL. 8. User preferences and customization are offloaded to PostgreSQL do do the heavy lifting. PostgreSQL has to look at the activity of each user to know if they have saved a post, previously read a post, upvoted that post, or even blocked the person who created the post. 9. Language choice is built into the system early, but I see no evidence it has proven to be useful. But it carries a high overhead in how many PostgreSQL database rows each site carries - and is used in filtering More often than not, I've found end-users confused why they can't find content when they accidentally turned off choices in lemmy-ui 10. All fields on SELECT. Throughout the Rust Diesel ORM code, it's every field in every table being touched. 11. SELECT statements are almost always ORM machine generated. TRIGGER FUNCTION logic is hand-written.
The three of crows have flapped it southenly, kraaking of de baccle to the kvarters of that sky whence triboos answer; Wail, 'tis well! She niver comes out when Thon's on shower or when Thon's flash with his Nixy girls or when Thon's blowing toom- cracks down the gaels of Thon. No nubo no! Neblas on you liv! Her would be too moochy afreet. Of Burymeleg and Bindme- rollingeyes and all the deed in the woe. Fe fo fom! She jist does hopes till byes will be byes. Here, and it goes on to appear now, she comes, a peacefugle, a parody's bird, a peri potmother, a pringlpik in the ilandiskippy, with peewee and powwows in beggybaggy on her bickybacky and a flick flask fleckflinging its pixylighting pacts' huemeramybows, picking here, pecking there, pussypussy plunderpussy. But it's the armitides toonigh, militopucos, and toomourn we wish for a muddy kissmans to the minutia workers and there's to be a gorgeups truce for happinest childher everwere. Come nebo me and suso sing the day we sallybright. She's burrowed the coacher's headlight the better to pry (who goes cute goes siocur and shoos aroun) and all spoiled goods go into her nabsack: curtrages and rattlin buttins, nappy spattees and flasks of all nations, clavicures and scampulars, maps, keys and woodpiles of haypennies and moonled brooches with bloodstaned breeks in em, boaston nightgarters and masses of shoesets and nickelly nacks and foder allmicheal and a lugly parson of cates and howitzer muchears and midgers and maggets, ills and ells with loffs of toffs and pleures of bells and the last sigh that come fro the hart (bucklied!) and the fairest sin the sunsaw (that's cearc!). With Kiss. Kiss Criss. Cross Criss. Kiss Cross. Undo lives 'end. Slain. How bootifull and how truetowife of her, when strengly fore- bidden, to steal our historic presents from the past postpropheti- cals so as to will make us all lordyheirs and ladymaidesses of a pretty nice kettle of fruit. She is livving in our midst of debt and laffing through all plores for us (her birth is uncontrollable), with a naperon for her mask and her sabboes kickin arias (so sair! so solly!) if yous ask me and I saack you. Hou! Hou! Gricks may rise and Troysirs fall (there being two sights for ever a picture)
of the lipoleums, Toffeethief, that spy on the Willingdone from his big white harse, the Capeinhope. Stonewall Willingdone is an old maxy montrumeny. Lipoleums is nice hung bushel- lors. This is hiena hinnessy laughing alout at the Willing- done. This is lipsyg dooley krieging the funk from the hinnessy. This is the hinndoo Shimar Shin between the dooley boy and the hinnessy. Tip. This is the wixy old Willingdone picket up the half of the threefoiled hat of lipoleums fromoud of the bluddle filth. This is the hinndoo waxing ranjymad for a bombshoob. This is the Willingdone hanking the half of the hat of lipoleums up the tail on the buckside of his big white harse. Tip. That was the last joke of Willingdone. Hit, hit, hit! This is the same white harse of the Willingdone, Culpenhelp, waggling his tailoscrupp with the half of a hat of lipoleums to insoult on the hinndoo see- boy. Hney, hney, hney! (Bullsrag! Foul!) This is the seeboy, madrashattaras, upjump and pumpim, cry to the Willingdone: Ap Pukkaru! Pukka Yurap! This is the Willingdone, bornstable ghentleman, tinders his maxbotch to the cursigan Shimar Shin. Basucker youstead! This is the dooforhim seeboy blow the whole of the half of the hat of lipoleums off of the top of the tail on the back of his big wide harse. Tip (Bullseye! Game!) How Copen- hagen ended. This way the museyroom. Mind your boots goan out. Phew! What a warm time we were in there but how keling is here the airabouts! We nowhere she lives but you mussna tell annaone for the lamp of Jig-a-Lanthern! It's a candlelittle houthse of a month and one windies. Downadown, High Downadown. And num- mered quaintlymine. And such reasonable weather too! The wa- grant wind's awalt'zaround the piltdowns and on every blasted knollyrock (if you can spot fifty I spy four more) there's that gnarlybird ygathering, a runalittle, doalittle, preealittle, pouralittle, wipealittle, kicksalittle, severalittle, eatalittle, whinealittle, kenalittle, helfalittle, pelfalittle gnarlybird. A verytableland of bleakbardfields! Under his seven wrothschields lies one, Lumproar. His glav toside him. Skud ontorsed. Our pigeons pair are flewn for northcliffs.