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 Now • 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 Now • 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 Now • 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 Now • 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 Now • 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 Now • 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 Now • 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 Now • 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 Now • 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 Now • 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 Now • 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 Now • 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 Now • 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 Now • 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 Now • 100%
https://beehaw.org/post/7618912 dust settles about code over past months
RoundSparrow Now • 100%
Written 2 weeks ago, pretty interesting: https://literature.cafe/comment/825554
RoundSparrow Now • 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 Now • 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.
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).
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.
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...
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
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
RoundSparrow @ BT
RoundSparrow@ bulletintree.com"Finnegans Wake is the greatest guidebook to media study ever fashioned by man." - Marshall McLuhan, Newsweek Magazine, page 56, February 28, 1966.
I have never done LSD or any other illegal drugs, but I have read FInnegans Wake: www.LazyWake.com
Lemmy tester, "RocketDerp" is my username on GitHub