Briskfall

I found out in another thread that it is NOT intended behavior here https://kbin.social/m/youshouldknow@lemmy.world/t/56323/YSK-that-you-can-edit-titles-on-Lemmy-unlike-Reddit#entry-comment-241691

Which means that hopefully, there should be a fix underway... I hope🥲.

I've had better results searching through the instances themselves because Google doesn't always index the keywords on time. On caveat of this method is that if the instance doesn't have the syncing out the instance where the info is from being propagated, then this trick would not work

While I'm not entirely sure about why things are set up the way they are, I guess that it was done on purpose seeing your response. Now, if explaining the why's and how's of this design is too much of a sensitive topic, I'm okay with dropping my questions and just going along with the ride 👍.

If it's possible as a compromise, how about consider displaying both "the origin of the magazine" (instance) and the "name of the magazine", rather than the existing format where kbin.social appears after the title, followed by just the "name of the magazine" (omitting the original instance from which it hails).

For example, the current layout is:

TITLE

(kbin.social)

PREVIEW OF BODY TEXT

USER, 33 minutes ago to NAME_OF_MAGAZINE_WITHOUT_ORIGINAL_INSTANCE (like meta)

My suggestion is to include an option for displaying it like this (I do understand that it might be a clutter to some, but it would be a nice feature for others facing the same qualms as I do):

TITLE

(kbin.social)

PREVIEW OF BODY TEXT

USER, 33 minutes ago to NAME_OF_MAGAZINE_WITH_ORIGINAL_INSTANCE (like META@LEMMY.ML)

To provide some context, I came across a post on either main or meta on the front page. It had kbin.social listed below the title along with the "name of the magazine," but the original instance name was missing. I was about to express my confusion since it didn't align with my experience on kbin.social, but upon double-checking the URL, I realized the post was not related to kbin.social at all. This "issue" generated by the behavior seems to mainly affect mags like main and meta posts, but considering these posts do often appear on the front page (since I've enabled other instances to discover more exciting content), I think that it's issue worth exploring.

Hopefully in the meantime, I've figured better ways to work around this issue (to verify the instance of the magazine) on mobile ( apart from checking the address bar), which are to

• click on the hamburger menu or
• to scroll to the page's end.

Oh no, not a Pay to Win x HostileArchitecure collaboration!!

This is giving me peak ABoringDystopia vibes...

Uh wow this is the first time I've seen summoning the instance in reverse (what I'm aware of so far) and it feels like black magic on the other end... My head hurts now hahaha 😵‍💫

Just found out a while ago that it varies by instance, e.g. for kbin.social, it's not good to add the exclamation mark and just leave it as community@instance bare.

I used to not do it, but I've been influenced by Bing after talking to it for so long during the closed beta (I guess that this is an effect of subconsciously mirroring it so that I don't get kicked out before the 5 turn limit back in the days haha 😂)

Then again, in diverse online communities, there are various styles and voices that are eventually formed to be what's "acceptable" be the general consensus. As Lemmy is very new, it has yet to find its voice yet... I think 🤔.

I think that giving too many choices to users who are already confused by the concept of federation and instances will enhance their paralysis of making choice due to cognitive overload (See https://en.m.wikipedia.org/wiki/Overchoice ).

I've found out kbin.social the easiest to get used to (end-user wise).

Damn I was looking forever how to get some communities working. Thanks!

This is definitely a much needed information during onboarding (not sure if it was included already or if I've missed it).

How long does it usually take for google to index websites? Because I tried the string lemmy site:lemmy.ml after:2023-06-15 and only one post turned up for me and it was Memes... the current state of affairs does not seem promising 😔 And if I tried with another instance with the same keywords lemmy site:kbin.social after:2023-06-15 nothing even turned up.

I wonder though, will search engines adapt to Lemmy and its fediverse system? Or will search engines die? Or will we see dedicated search engines to search through the fediverse?

Unfortunately, I've been getting some 404 not found of some communities/magazines of some instances that are not from the instance I'm using, e.g. I'm using kbin.social at the current posting account, but let's say that I tried to access something like https://sh.itjust.works/c/skincareaddiction there's no issues whatsoever (since it's the main instance where that community spawned off) but if I tried https://kbin.social/m/skincareaddiction@sh.itjust.works then I would get the aforementioned error code. I find it pretty inconvenient that caching/indexing of certain less popular (which I assume is what is happening) community working clunkily, it feels not as reliable than using a centralized service, but I guess that this is the price to pay for a decentralized system.

Two, but only because I can't log into the other fediverse instance that I've registered (sh.itjust.works).