Posting this in light of a recent one week Reddit ban I earned for shitting on US police, as I'm sure many of us have gotten in recent weeks.
So I've spent the past few months working on a self hostable, federated, Reddit alternative called Lemmy, and it's pretty much ready to go. Unlike here we'd have ultimate control over all content, and would never have to self censor.
Obviously as communists, we agitate where the people are, so we should never abandon Reddit entirely, but it's been clear to all of us from day one, that communities like this stand on unsteady ground, and could be banned or quarantined at any moment by the white supremacist Reddit admins. This would be both a backup and a potentially better alternative. Moderation abilities are there, as well as a slur filter.
I wanted to ask ppl here if they'd like me to host an instance, and mod all the current mods here.
The instance that post mentions at the end became Lemmygrad. Lemmy.ml and Lemmygrad are the same people. This was their first post announcing Lemmy as a real thing you could go use. (It's also why a good chunk of the Threadiverse is absolutely infested with tankies.)
I never agitated for a fork because generally the Lemmy devs do an okay job at keeping their politics separate from their software. But the more I look at their attitudes and (frankly) the hazing they do towards contributors, the more I'm thinking that it may be better to push for an outright fork of Lemmy, give it a better name, a saner dev team, and excise the original devs entirely. Even if we ignore their politics (which is hard to do, but can be done), they've simply not been the best stewards of the project - it's succeeded in spite of them, not because of them.
That said, I think Lemmy as a piece of software is generally okay. Kbin has more long-term promise, I feel, but Kbin has its own issues and is much rougher around the edges. A lot of the issues Kbin has have already been sorted out by Lemmy, so I think it might be best to make a Lemmy fork and bring in features from Kbin into it (alongside performance fixes and whatnot that the Lemmy devs refuse to action on).
Why are people obsessed with communities having the same domain name as their login? How do you expect these communities to deal with moderation and admin policies?
Here are some ideas for solutions to the real issues:
Add smart cross posting like on Reddit where interacting with a cross post happens on the community where it was created.
Develop mesh federation instead of a star topography. There would still only be one community with a unique name, but instances could share changes between each other, not just with the host.
Provide a true cross instance community search that is integrated in the primary UI. It would need to provide better metrics for like-named communities so that users can make an informed choice.
Admins need to stop land-grab communities. There needs to be a commitment to moderating, maintaining and growing the community. They could start by purging Reddit general interest knock-offs with fewer than 10 subscribers.
Add support for instance relative links not only to communities, but comments and posts.
In general, I think user focused instances should be separate from community focused instances, but that’s a different rant
I’m subscribed to four communities named "fediverse@"something. Yes, it’s a bit annoying. But it’s also good to have backups, in the sense that I never know which instance might defederate from my own or from others who also use these communities.
Not sure what the point of this post is. Do you want people to vote on which to keep, and which to discard? They already do that. People subscribe and unsubscribe, post or don’t, as they please. Apparently, we continuously vote on having four (probably even more) redundant communities.
I was trying to address a point that is frequently raised by people that gave Lemmy a try but are not planning to stay: seeing the same content posted across a few similar communities hinders content discovery, and just provides a worse browsing experience than centralized solutions like Reddit.
Not trying to be mean, but … you’re making a post about redundancy because other people make posts about redundancy? :D
In these other posts, a frequent answer is: Reddit isn’t that much different. A popular example is /r/gaming or /r/games or whatever. Apparently there are multiple subs for the same topic, sometimes with little to no differences.
Then some people object “but that’s not the same, they have different names”, to which others reply “on lemmy, the full name includes the instance, so we don’t have same name communities here, either”.
I think, bottom line, the two platforms aren’t very different in this regard. On both, users can create new subs/comms even if the exact same content already exists. And they do. Sometimes both survive, sometimes not. On both, users decide “with their feet”.
One relevant difference might be that in the Fediverse, redundancy actually has value. It protects against defederation, unstable servers, servers disappearing.
I still see value in combining duplicates. When I see a new community popping up, and I know a very similar thing already exists, I might leave a note in the new community wether they might want to participate in the other community instead. Just in case they were not aware it exists.
But aside from the Fediverse-specific reasons for duplicates, there are additional general reasons, which is why we see the same phenomenon on reddit. For example, people might dislike the moderation in the ‘original’. Or one might allow bots, the other not.
While this is my point of view (“it’s a non-issue”), I also note it’s a topic which is frequently brought up. Apparently, it’s frequently seen as an issue. This may be rooted in perception (including the fact that reddit is monolithic, falsly leading to the misconception it would only have one sub for one topic, all while it still has plenty of redundant duplicates) and communication (I got the feeling the fediverse’s federated structure is sometimes over-emphasized and creates more worries than necessary).
We probably will get technical solutions like grouping on a user-view level. Maybe some apps already have that. GitHub issues exist.
Aside from technical solutions, people can vote with their feet. It is of course perfectly fine to address and re-address the topic. This might help consolidate similar communities. Personally, I think having a few redundant communities is healthy for the nature of the fediverse.
That would still create a fragmented comment situation. Ideally, the server should be aware of “sister communities”, so it could merge the comment threads, or at least tell the client to do so. But that has all kinds of moderation implications, as noted elsewhere.
In the end you’re either doing federation on community level (which would require another level of federation administration - you can’t just merge like-named communities from Any instance), or you’d have to convince 1 community to go read only and refer to the “defacto” community.
The first one has a lot of technical hurdles (servers and clients would have to adapt, and then community admins would be responsible for deciding who to federate their communities with). The second depends on mods giving up their community, which is unlikely and undesirable in case of defederation. Or option 3: keep the status quo, of course.
I think Lemmy should come up with a meta cross post type. Where the post only exists once, but it’s indexed in multiple communities, and moderators of those communities can remove the cross post. Without affecting the original post
Kind of like a symbolic link
If not that then give us the ability to have relative references to posts inside of Lemmy. Instead of referencing a URL to a specific instance, kind of like the ! Or @ for for community names and usernames.
Then across post could at least link to the canonical discussion for talking.
I think Lemmy should come up with a meta cross post type. Where the post only exists once, but it’s indexed in multiple communities, and moderators of those communities can remove the cross post. Without affecting the original post
Some discussion about how crossposts could work differently
If not that then give us the ability to have relative references to posts inside of Lemmy. Instead of referencing a URL to a specific instance, kind of like the ! Or @ for for community names and usernames.
<p>Group Processes &Intergroup Relations, Ahead of Print. <br />Public spaces that are named for or commemorate prejudiced historical figures may harm targets of prejudice. They can signal what a community believes or values and, consequently, may exacerbate targets’ perceptions of hostility, reduced safety, and low belongingness. Across six studies (n = 505 BIPOC [Black, Indigenous, and people of color]; n = 1,230 White U.S. university students), we examined: the effect of space names on target versus nontarget harms of hostility, safety, and belonging (Study 1), whether space names signal community beliefs (Studies 2a and 2b), whether perceptions of space names as community belief signals mediate BIPOC targets’ exacerbated harms in spaces with prejudiced namesakes (Study 3) as well as in response to a prejudiced space being renamed or having a name retained (Study 4). Finally, we examined White versus BIPOC perceptions of space renaming with respect to sincerity and mitigated harms (Study 5). Relative to nontargets, targets reported greater harms in spaces named for prejudiced figures, and some of these exacerbated harms were driven by perceived community belief signals. White individuals reported somewhat greater optimism than BIPOC individuals about harm mitigation as consequence of renaming. Results have implications for understanding the harms of symbolic prejudice, and considerations for organizations to foster genuine, beneficial renaming initiatives.</p>
<p><a href="https://journals.sagepub.com/doi/abs/10.1177/13684302231184371?ai=2b4&mi=ehikzz&af=R" target="_blank" rel="noopener">Read the full article ›</a></p>
<p>The post <a rel="nofollow" href="https://ifp.nyu.edu/2023/journal-article-abstracts/13684302231184371/">What’s in a name . . . and for whom? How public spaces named for prejudiced individuals impact targets of prejudice</a> was curated by <a rel="nofollow" href="https://ifp.nyu.edu">information for practice</a>.</p>
Hi, I’m setting up a public wiki using mediawiki and I’d like some help ensuring the server and mediawiki is safely setup before I start sharing it publicly. I installed it on Vultr using the mediawiki app from the Vultr Marketplace. Are there any things I should ensure before publicly sharing the link?...
It would be security theatre if it was done for security. I’m not doing it for security, though - it’s for my sanity when checking the logs. Unrestricted SSH simply attracts too many bots and the failed logins make it impossible to quickly grasp a picture of what’s happening.
In regards to limits - this is my rule file for iptables on my lemmy instance:
The 27-year-old man who police say shot and killed a California business owner over a Pride flag draped in her store appears to have had a yearslong history of posting disturbing — and often violent — anti-LGBTQ messages on social media....
Ah yes, “fear”, the notorious antonym for “attraction.”
Phobia is the opposite of philia; they’re Greek suffixes, and they meant, and still mean, “fleeing from” and “seeking out”; the connotation of “fear” arrived considerably more recently, because of psychiatric conditions being named … in Greek.
If you’re going to a pedantic dummy about etymology, at least take the time to learn a little before you dive in my dude.
For instance, you could object that “homophobia” originally referred to someone who irrationally avoided other humans, and then demand that words never change their meaning and immediately begin proudly speaking fluent proto Indo European.
If you asked a spokesperson from any Fortune 500 Company to list the benefits of genocide or give you the corporation’s take on whether slavery was beneficial, they would most likely either refuse to comment or say “those things are evil; there are no benefits.” However, Google has AI employees, SGE and Bard, who are more...
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !boneappletea
Meta post I’ve decided to make. I enjoyed the unixporn subreddit a lot when I used reddit more. I enjoy customizing my linux de as much as the next nerd....
Neither is your reply. When I saw your comment, it immediately occurred to me that you must be from hexbear.net. (My client hides the @instance.org part in usernames.) There was something inherently characteristic of hexbears in your comment. I clicked on your name to check, and voila - of course you were. Your comment is extremely condescending. This is how dreaded the userbase of hexbear.net is. I bet that at least 25 of your 30 upvotes are from other hexbears who upvotes anything from hexbears. I wonder why so many instances have decided to defederate from you.
oh shit I forgot liberals babies don’t have reading comprehension skills, even for things they wrote
okay, so you were replying to a poster named space_comrade from a mostly communist instance of lemmy and then you asked if they had gone so far left that they ended up in rightville
If anyone bothered to actually look at the SQL SELECT that Lemmy uses to list posts every time you hit refresh it would be blindingly obvious how convoluted it is. yet the community does not talk about the programming issues and instead keeps raising money for 64 core hardware upgrades without recognizing just how tiny Lemmy’s database really is and how 57K users is not a large number at all!
your original one, friend. I wouldn’t have argued this point if you had started here.
I mentioned “ORM” right in my first comment.
<span style="color:#323232;">SELECT
</span><span style="color:#323232;"> "post"."id" AS post_id, "post"."name" AS post_title,
</span><span style="color:#323232;"> -- "post"."url", "post"."body", "post"."creator_id", "post"."community_id", "post"."removed", "post"."locked", "post"."published", "post"."updated", "post"."deleted", "post"."nsfw", "post"."embed_title", "post"."embed_description", "post"."thumbnail_url",
</span><span style="color:#323232;"> -- "post"."ap_id", "post"."local", "post"."embed_video_url", "post"."language_id", "post"."featured_community", "post"."featured_local",
</span><span style="color:#323232;"> "person"."id" AS p_id, "person"."name",
</span><span style="color:#323232;"> -- "person"."display_name", "person"."avatar", "person"."banned", "person"."published", "person"."updated",
</span><span style="color:#323232;"> -- "person"."actor_id", "person"."bio", "person"."local", "person"."private_key", "person"."public_key", "person"."last_refreshed_at", "person"."banner", "person"."deleted", "person"."inbox_url", "person"."shared_inbox_url", "person"."matrix_user_id", "person"."admin",
</span><span style="color:#323232;"> -- "person"."bot_account", "person"."ban_expires",
</span><span style="color:#323232;"> "person"."instance_id" AS p_inst,
</span><span style="color:#323232;"> "community"."id" AS c_id, "community"."name" AS community_name,
</span><span style="color:#323232;"> -- "community"."title", "community"."description", "community"."removed", "community"."published", "community"."updated", "community"."deleted",
</span><span style="color:#323232;"> -- "community"."nsfw", "community"."actor_id", "community"."local", "community"."private_key", "community"."public_key", "community"."last_refreshed_at", "community"."icon", "community"."banner",
</span><span style="color:#323232;"> -- "community"."followers_url", "community"."inbox_url", "community"."shared_inbox_url", "community"."hidden", "community"."posting_restricted_to_mods",
</span><span style="color:#323232;"> "community"."instance_id" AS c_inst,
</span><span style="color:#323232;"> -- "community"."moderators_url", "community"."featured_url",
</span><span style="color:#323232;"> ("community_person_ban"."id" IS NOT NULL) AS ban,
</span><span style="color:#323232;"> -- "post_aggregates"."id", "post_aggregates"."post_id", "post_aggregates"."comments", "post_aggregates"."score", "post_aggregates"."upvotes", "post_aggregates"."downvotes", "post_aggregates"."published",
</span><span style="color:#323232;"> -- "post_aggregates"."newest_comment_time_necro", "post_aggregates"."newest_comment_time", "post_aggregates"."featured_community", "post_aggregates"."featured_local",
</span><span style="color:#323232;"> --"post_aggregates"."hot_rank", "post_aggregates"."hot_rank_active", "post_aggregates"."community_id", "post_aggregates"."creator_id", "post_aggregates"."controversy_rank",
</span><span style="color:#323232;"> -- "community_follower"."pending",
</span><span style="color:#323232;"> ("post_saved"."id" IS NOT NULL) AS save,
</span><span style="color:#323232;"> ("post_read"."id" IS NOT NULL) AS read,
</span><span style="color:#323232;"> ("person_block"."id" IS NOT NULL) as block,
</span><span style="color:#323232;"> "post_like"."score",
</span><span style="color:#323232;"> coalesce(("post_aggregates"."comments" - "person_post_aggregates"."read_comments"), "post_aggregates"."comments") AS unread
</span><span style="color:#323232;">
</span><span style="color:#323232;">FROM (
</span><span style="color:#323232;"> ((((((((((
</span><span style="color:#323232;"> (
</span><span style="color:#323232;"> (
</span><span style="color:#323232;"> "post_aggregates"
</span><span style="color:#323232;"> INNER JOIN "person" ON ("post_aggregates"."creator_id" = "person"."id")
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> INNER JOIN "community" ON ("post_aggregates"."community_id" = "community"."id")
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "community_person_ban"
</span><span style="color:#323232;"> ON (("post_aggregates"."community_id" = "community_person_ban"."community_id") AND ("community_person_ban"."person_id" = "post_aggregates"."creator_id"))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> INNER JOIN "post" ON ("post_aggregates"."post_id" = "post"."id")
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "community_follower" ON (("post_aggregates"."community_id" = "community_follower"."community_id") AND ("community_follower"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "community_moderator" ON (("post"."community_id" = "community_moderator"."community_id") AND ("community_moderator"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "post_saved" ON (("post_aggregates"."post_id" = "post_saved"."post_id") AND ("post_saved"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "post_read" ON (("post_aggregates"."post_id" = "post_read"."post_id") AND ("post_read"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "person_block" ON (("post_aggregates"."creator_id" = "person_block"."target_id") AND ("person_block"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "post_like" ON (("post_aggregates"."post_id" = "post_like"."post_id") AND ("post_like"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "person_post_aggregates" ON (("post_aggregates"."post_id" = "person_post_aggregates"."post_id") AND ("person_post_aggregates"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "community_block" ON (("post_aggregates"."community_id" = "community_block"."community_id") AND ("community_block"."person_id" = 3)))
</span><span style="color:#323232;"> LEFT OUTER JOIN "local_user_language" ON (("post"."language_id" = "local_user_language"."language_id") AND ("local_user_language"."local_user_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;">WHERE (((((((
</span><span style="color:#323232;"> ((("community"."deleted" = false) AND ("post"."deleted" = false)) AND ("community"."removed" = false))
</span><span style="color:#323232;"> AND ("post"."removed" = false)) AND ("post_aggregates"."creator_id" = 3)) AND ("post"."nsfw" = false))
</span><span style="color:#323232;"> AND ("community"."nsfw" = false)) AND ("local_user_language"."language_id" IS NOT NULL))
</span><span style="color:#323232;"> AND ("community_block"."person_id" IS NULL))
</span><span style="color:#323232;"> AND ("person_block"."person_id" IS NULL))
</span><span style="color:#323232;">ORDER BY "post_aggregates"."featured_local" DESC , "post_aggregates"."published" DESC
</span><span style="color:#323232;">LIMIT 10
</span><span style="color:#323232;">OFFSET 0
</span><span style="color:#323232;">;
</span>
If you are explicitly aware that different instances specialize in different concerns I can absolutely see the use for a feature like that, but most people want a feature of that sort just so they can “paper over” federation and pretend to have one giant community with one giant moderation policy / culture / priorities.
And that is before getting to the absolutely horrible idea of automatically generating multi-communities by merging communities with the exact same name regardless of their instance.
joins are better than in queries with potentially thousands of inserted IDs.
Given that more than 8 JOIN statements is something PostgreSQL specifically concerns itself with (join_collapse_limit). I hand-edit the query with a single IN clause and the performance problem disappears. 8 full seconds becomes less than 200ms against 5,431,043 posts. And that 200ms is still high, as I was extremely over-reaching with “LIMIT 1000” in case the end-user went wild with blocking lists or some other filtering before reaching the final “LIMIT 10”. When I change it to “LIMIT 20” in the subquery, it drops almost in half to 115ms… still meeting the needs of the outer “LIMIT 10” by double. More of the core query filtering can be put into the IN subquery, as we aren’t dealing with more than 500 length pages (currently limited to 50).
<span style="color:#323232;">SELECT
</span><span style="color:#323232;"> "post"."id" AS post_id, "post"."name" AS post_title,
</span><span style="color:#323232;"> -- "post"."url", "post"."body", "post"."creator_id", "post"."community_id", "post"."removed", "post"."locked", "post"."published", "post"."updated", "post"."deleted", "post"."nsfw", "post"."embed_title", "post"."embed_description", "post"."thumbnail_url",
</span><span style="color:#323232;"> -- "post"."ap_id", "post"."local", "post"."embed_video_url", "post"."language_id", "post"."featured_community", "post"."featured_local",
</span><span style="color:#323232;"> "person"."id" AS p_id, "person"."name",
</span><span style="color:#323232;"> -- "person"."display_name", "person"."avatar", "person"."banned", "person"."published", "person"."updated",
</span><span style="color:#323232;"> -- "person"."actor_id", "person"."bio", "person"."local", "person"."private_key", "person"."public_key", "person"."last_refreshed_at", "person"."banner", "person"."deleted", "person"."inbox_url", "person"."shared_inbox_url", "person"."matrix_user_id", "person"."admin",
</span><span style="color:#323232;"> -- "person"."bot_account", "person"."ban_expires",
</span><span style="color:#323232;"> "person"."instance_id" AS p_inst,
</span><span style="color:#323232;"> "community"."id" AS c_id, "community"."name" AS community_name,
</span><span style="color:#323232;"> -- "community"."title", "community"."description", "community"."removed", "community"."published", "community"."updated", "community"."deleted",
</span><span style="color:#323232;"> -- "community"."nsfw", "community"."actor_id", "community"."local", "community"."private_key", "community"."public_key", "community"."last_refreshed_at", "community"."icon", "community"."banner",
</span><span style="color:#323232;"> -- "community"."followers_url", "community"."inbox_url", "community"."shared_inbox_url", "community"."hidden", "community"."posting_restricted_to_mods",
</span><span style="color:#323232;"> "community"."instance_id" AS c_inst,
</span><span style="color:#323232;"> -- "community"."moderators_url", "community"."featured_url",
</span><span style="color:#323232;"> ("community_person_ban"."id" IS NOT NULL) AS ban,
</span><span style="color:#323232;"> -- "post_aggregates"."id", "post_aggregates"."post_id", "post_aggregates"."comments", "post_aggregates"."score", "post_aggregates"."upvotes", "post_aggregates"."downvotes", "post_aggregates"."published",
</span><span style="color:#323232;"> -- "post_aggregates"."newest_comment_time_necro", "post_aggregates"."newest_comment_time", "post_aggregates"."featured_community", "post_aggregates"."featured_local",
</span><span style="color:#323232;"> --"post_aggregates"."hot_rank", "post_aggregates"."hot_rank_active", "post_aggregates"."community_id", "post_aggregates"."creator_id", "post_aggregates"."controversy_rank",
</span><span style="color:#323232;"> -- "community_follower"."pending",
</span><span style="color:#323232;"> ("post_saved"."id" IS NOT NULL) AS save,
</span><span style="color:#323232;"> ("post_read"."id" IS NOT NULL) AS read,
</span><span style="color:#323232;"> ("person_block"."id" IS NOT NULL) as block,
</span><span style="color:#323232;"> "post_like"."score",
</span><span style="color:#323232;"> coalesce(("post_aggregates"."comments" - "person_post_aggregates"."read_comments"), "post_aggregates"."comments") AS unread
</span><span style="color:#323232;">
</span><span style="color:#323232;">FROM (
</span><span style="color:#323232;"> ((((((((((
</span><span style="color:#323232;"> (
</span><span style="color:#323232;"> (
</span><span style="color:#323232;"> "post_aggregates"
</span><span style="color:#323232;"> INNER JOIN "person" ON ("post_aggregates"."creator_id" = "person"."id")
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> INNER JOIN "community" ON ("post_aggregates"."community_id" = "community"."id")
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "community_person_ban"
</span><span style="color:#323232;"> ON (("post_aggregates"."community_id" = "community_person_ban"."community_id") AND ("community_person_ban"."person_id" = "post_aggregates"."creator_id"))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> INNER JOIN "post" ON ("post_aggregates"."post_id" = "post"."id")
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "community_follower" ON (("post_aggregates"."community_id" = "community_follower"."community_id") AND ("community_follower"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "community_moderator" ON (("post"."community_id" = "community_moderator"."community_id") AND ("community_moderator"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "post_saved" ON (("post_aggregates"."post_id" = "post_saved"."post_id") AND ("post_saved"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "post_read" ON (("post_aggregates"."post_id" = "post_read"."post_id") AND ("post_read"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "person_block" ON (("post_aggregates"."creator_id" = "person_block"."target_id") AND ("person_block"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "post_like" ON (("post_aggregates"."post_id" = "post_like"."post_id") AND ("post_like"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "person_post_aggregates" ON (("post_aggregates"."post_id" = "person_post_aggregates"."post_id") AND ("person_post_aggregates"."person_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> LEFT OUTER JOIN "community_block" ON (("post_aggregates"."community_id" = "community_block"."community_id") AND ("community_block"."person_id" = 3)))
</span><span style="color:#323232;"> LEFT OUTER JOIN "local_user_language" ON (("post"."language_id" = "local_user_language"."language_id") AND ("local_user_language"."local_user_id" = 3))
</span><span style="color:#323232;"> )
</span><span style="color:#323232;">WHERE
</span><span style="color:#323232;"> post_aggregates.id IN (
</span><span style="color:#323232;"> SELECT id FROM post_aggregates
</span><span style="color:#323232;"> WHERE "post_aggregates"."creator_id" = 3
</span><span style="color:#323232;"> ORDER BY "post_aggregates"."featured_local" DESC , "post_aggregates"."published" DESC
</span><span style="color:#323232;"> LIMIT 1000
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> AND
</span><span style="color:#323232;"> (((((((
</span><span style="color:#323232;"> (
</span><span style="color:#323232;"> (("community"."deleted" = false) AND ("post"."deleted" = false))
</span><span style="color:#323232;"> AND ("community"."removed" = false))
</span><span style="color:#323232;"> AND ("post"."removed" = false)
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> AND ("post_aggregates"."creator_id" = 3)
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> AND ("post"."nsfw" = false))
</span><span style="color:#323232;"> AND ("community"."nsfw" = false)
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> AND ("local_user_language"."language_id" IS NOT NULL)
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> AND ("community_block"."person_id" IS NULL)
</span><span style="color:#323232;"> )
</span><span style="color:#323232;"> AND ("person_block"."person_id" IS NULL)
</span><span style="color:#323232;"> )
</span><span style="color:#323232;">ORDER BY "post_aggregates"."featured_local" DESC , "post_aggregates"."published" DESC
</span><span style="color:#323232;">LIMIT 10
</span><span style="color:#323232;">OFFSET 0
</span><span style="color:#323232;">;
</span>
If it isn’t social hazing, then what is going on here? Why has this issue gone on since May and servers are crashing every day?
Former President Donald Trump’s supporters say they hold him as a source of true information over their family, friends, and religious leaders, according to a new CBS News/YouGov poll out on Sunday.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !bridgingthegap
Not open source, but I don't really care, I would like to know if it's genuinely fully decentralized. (wiremin.org)
From my experience so far, they do have some features and weakness is made or cause by decentralized sturcture. I am not an expert, needs help here.
deleted_by_author
deleted_by_author
deleted_by_author
T-Mobile - news, speedtests, discussions, and help with all things T-Mobile
T-Mobile lemmy.ml !t_mobile
Lemmy/Kbin Reinvestment Phase and Recruiting from Mastodon
cross-posted from: lemmy.blahaj.zone/post/2173435...
Sibling communities: A middle way
cross-posted from: sh.itjust.works/post/3508135...
Sibling communities: A middle way
There’s been an ongoing debate about whether communities should combine or stay separate. Both have significant disadvantages and advantages:...
Should we decide to have a main fediverse community or should we keep posting everything twice?
Hello everyone,...
Should we decide to have a main fediverse community or should we keep posting everything twice?
Hello everyone,...
Need help ensuring my public mediawiki is safe before launch
Hi, I’m setting up a public wiki using mediawiki and I’d like some help ensuring the server and mediawiki is safely setup before I start sharing it publicly. I installed it on Vultr using the mediawiki app from the Vultr Marketplace. Are there any things I should ensure before publicly sharing the link?...
Pride flag killing suspect appears to have a long history of anti-LGBTQ social posts (www.nbcnews.com)
The 27-year-old man who police say shot and killed a California business owner over a Pride flag draped in her store appears to have had a yearslong history of posting disturbing — and often violent — anti-LGBTQ messages on social media....
Google's AI Bots Tout 'Benefits' of Genocide, Slavery, Fascism, Other Evils (www.tomshardware.com)
If you asked a spokesperson from any Fortune 500 Company to list the benefits of genocide or give you the corporation’s take on whether slavery was beneficial, they would most likely either refuse to comment or say “those things are evil; there are no benefits.” However, Google has AI employees, SGE and Bard, who are more...
Hey, we should all really stop using racist slang to refer to customozation
Meta post I’ve decided to make. I enjoyed the unixporn subreddit a lot when I used reddit more. I enjoy customizing my linux de as much as the next nerd....
There is a drop in monthly active Lemmy users (from 65k to 57k) (lemmy.fediverse.observer)
It is probably due to a number of people stopping using their alts after some instance hopping....
Hey, I made a new lemmy instance focused on art and art discussion if you're interested in that. (lemmyloves.art)
I posted a bit ago on a different account, and yeah here we are. I actually set it up!...
Trump Voters Trust Ex-President More Than Their Family and Friends: Poll (www.newsweek.com)
Former President Donald Trump’s supporters say they hold him as a source of true information over their family, friends, and religious leaders, according to a new CBS News/YouGov poll out on Sunday.