Hehe, right! (technically). Context matters! When talking about fruit, people usually don’t include stellar objects when weighing their options. Still true when taking in consideration that “apples to oranges” is usually metaphorical and not really about fruit.

I like that, especially this insight:

when two things have very few attributes in common or the attributes they can be compared on are very broad, general or abstract, it is harder to compare them.

A melon and a pogo stick are harder to compare, for their defining attributes hardly overlap except on a very abstract way.

Good on you to say “harder to compare” :D

it’s all semantic subjectivity. Poetry compares dissimilar things and equates unequal concepts all the time.

Another thing worthwhile to point out; subjectivity. I guess that part bothered me too. “cannot be compared” attempts to establish some kind of objective truth, whereas it only can be a subjective opinion.

The reference to poetry was nice, too.

My point works just as well with an arbitrary amount of options. Someone could say “These quintillion things cannot be compared”.

The number of options is irrelevant to what I tried to address. Though my examples were only pairs, so sorry for causing confusion.

Thanks for taking the time to write this detailed reply. I guess you’re right about the equivocation and I can see the irony :D

Though I have not fully understood yet. Following your example, the two different concepts are …

• in case A, we compare the value of a property (different top speed)
• in case B, we compare the purpose or context-dependend usefulness of an attribute (different types of liquid container holders)

What blocks me from fully agreeing is that still, both are comparisons. And they don’t feel so different to me that I would call them different concepts. When I look up examples for equivocations, those do feel very different to me.

I still guess you’re right. If you (or someone else) could help me see the fallacy, I’d appreciate.

Agreed, yeah. Guess I was taking the word too literally.

Because religion evolved to thrive in us.

It’s like a parasite, and our mind is the host. It competes with other mind-parasites like other religions, or even scientific ideas. They compete for explanatory niches, for feeling relevant and important, and maybe most of all for attention.

Religions evolved traits which support their survival. Because all the other variants which didn’t have these beneficial traits went extinct.

Like religions who have the idea of being super-important, and that it’s necessary to spread your belief to others, are ‘somehow’ more spread out than religions who don’t convey that need.

This thread is a nice collection of traits and techniques which religions have collected to support their survival.

This perspective is based on what Dawkins called memetics. It’s funny that this idea is reciprocally just another mind-parasite, which attempted to replicate in this comment.

An (intuitively) working search would be a great step ahead. It should find and show things if they exist, and only show no results if they do not. That a plethora of external tools exist to meet these basic needs shows both how much this is needed, and how much it is broken.

I also feel I have more luck finding communities if searching for ‘all’, instead of ‘communities’. Don’t make me add cryptic chars to my search to make it work. Do that for me in the background if necessary.

It’s been long since I’ve been using it, but iirc, it’s impossible or painful to search for a specific community in your subscribed list.

From the title, I had a question and found the answer in the FAQ:

What’s an unconference?

An unconference is a conference in which the participants – rather than the organizers – decide which sessions happen each day and on which topics. In the many years we have been organizing unconferences, we have found that for complex subjects like the Fediverse, attendees get more value (and fun!) out of unconferences than from traditional conferences. Sounds disorganized? It did to us, too, until we actually experienced our first one. So don’t worry, it will be fine :-)

Here are some suggestions for how to prepare for an unconference.

And this is another issue which hinders discoverability. It’s nice there are tools and workarounds but their existence also signals the issue exists.

I didn’t say able to locate I said there being a list.

Are you confusing comments?

I see this in the referred comment:

having the capability to locate

While the word “list” does not appear.

But mostly I think we should try to read the message, not focus on single words.

Adding a comment so people can experiment more in this thread.

Exactly this. It’s often about finding the right balance between technically optimal, and socially feasible (lacking the right phrase here).

The nerds brimming with technical expertise often neglect the second point.

Oh - wow! I was about to complain about how https://join-lemmy.org/ is a shining bad example in this regard, talking about server stuff right away and hiding how Lemmy actually looks until page 3, but apparently they changed that and improved it drastically. Cool, good job!

Anyways.

For collaborative projects especially, it is important to strike a balance between tech and social aspects. Making poor tech choices will put people off. But making your project less accessible will also result in less people joining. It’s crucial to find a good balance here. For many coming from the tech side, this usually means making far more concessions to the social side than intuitively feels right.

Just a guess: to prevent bots from scraping the full content?

I find the plateau quite puzzling (lemmy.world, but the total looks very similar):

There was quite a steep increase, and then it suddenly stopped.

I would rather expect it to slow down, than to stop that abruptly.

We’re looking at a fairly large group of people making a decision to create an account on Lemmy. There are plenty of reasons to expect it to be fuzzy. Even if they all responded to one particular event in time, some would have done so immediately, others the next day, few more even later.

Yes, that’s true, but the number probably actually declined for a similar reason.

Some created multiple accounts, others tried multiple platforms. Some were happy with lemmy and stayed, others did not.

Right, it does display a karma value in the user profile page (not my own, but for others). Regardless from which instance that user is.

It does not display user karma in threads, regardless on which instance. Does your experience differ?

Lemmy.ml Karma Calculator

Display Lemmy.ml Karma.

Seems to not be so useful outside of lemmy.ml

Reddit was using karma for a long time and people stayed. The exodus happened when reddit announced charging for using their API, and everything that came along. Karma was no significant part of that story.

When people “farm” for fake internet pointe by appealing to the oppinions of everyone else it leads to people just expressing one “right” (popular) oppinion.

We have the same result already, for several reasons. One is, we do have karma within threads.

Another is, people will get backlash for voicing the “wrong” opinion even if there is no point system. People happily reply to correct someone.

In any case, performance is just one factor. For a FOSS project to be successful long term it needs contributions from other developers and with the massive pool of Python developers there are, hopefully I’ll be getting some help soon. Also along those lines I have deliberately chosen:

to code as simply and stupidly as possible, to make it accessible to most skill levels.
No complicated frameworks, fancy algorithms, or esoteric design patterns. Model View Controller, baby.
No frontend build process or tool chain (vanilla JS only. No npm).
Few third party dependencies, only Redis and Postgresql. Mostly.

All this makes setting up an initial development environment, finding the bit you want to change and testing it out fairly quick and easy.

Sounds very wise to make it as accessible as possible. And you basically get super maintainable code as a side product!