Yes, when you open the homepage of your instance in a browser and scroll to the bottom, it should say something like “BE: 0.18.4”.
If it says that and you still get this bug, it’s a new one.
Yes, when you open the homepage of your instance in a browser and scroll to the bottom, it should say something like “BE: 0.18.4”.
If it says that and you still get this bug, it’s a new one.
Which Jerboa and Instance backend versions are you seeing this with? There was an issue in the backend that could produce this behavior but should be fixed in 0.18.4: https://github.com/LemmyNet/lemmy/pull/3823
Yes, that’s what this check (and the later introduced changes) are meant for. On the reasoning why this configuration is not desired I can’t comment.
The check giving this error is pretty old, so it seems that you got it to work was not intentional: https://github.com/LemmyNet/lemmy/blame/63d3759c481ff2d7594d391ae86e881e2aeca56d/crates/api_common/src/utils.rs#L539
As far as I can see, 0.18 and its release candidates only added additional checks preventing such an instance to be set up in the first place.
I’m not sure what exactly you’re asking, but I’ll assume it’s not the standard “I can’t find this remote community” question, as your fourth search result is from the exact community you’re searching for… and has a direct clickable link to the community as federated to your instance (in green).
If you want a direct link as a search result to the community, search for it’s URL on its home instance, e.g. here https://lemmy.ml/c/lemmy_support
You can get this via the link under the community header on the left, where it says “Lemmy Support” and underneath has the hyperlink “[email protected]”. Click that link or copy its URL.
It has nothing to with you having to accept it, it’s the instance itself having to confirm the subscription request. That doesn’t work reliably atm: https://github.com/LemmyNet/lemmy/issues/3203
This will be fixed by the same PR as the number thing. Really looking forward to the next release of the app, there have been a lot of fixes and improvements.
I understand the sentiment, and everyone of course has the right to do this with the content they posted, but please consider:
The only thing this probably achieves is fucking over people googling for specific information in the future. How often have I searched for some really specific problem or information, only to find a thread in some niche subreddit from years ago with exactly what I needed?
For Reddit itself it’s trivial to keep previous versions of comments. Also deleted posts can just be flagged as ‘hidden’ and still remain in the database. They already have your content and won’t be giving it up. So please consider leaving it available for the public as well.
That’s a good idea! I understand the sentiment of leaving a final “fuck you” to Reddit, but at the same time the thought of losing the treasure trove of accumulated knowledge stored there pains me.
I was thinking of something like that too, but probably never would’ve gotten around to implement it myself, so thanks! Could you put your script on Github or something maybe?
Also it would be great if it could also copy at least top-level comments by OP, because that’s often used for linking to a source.
That’s how I interpret the post pinned to their front page asking users to go somewhere else: https://lemmy.ml/post/1147770
I don’t think lemmy.ml is accepting new users currently. Choose another instance (server) from the recommended ones at https://join-lemmy.org/instances
It doesn’t really matter much which one, you will still be able to interact with communities across different instances.
I think that might just be due to different Markdown engines supporting different feature sets. But not having a consistent way to tag spoilers really sucks.
Edit: another thing that’s bugging me about the Markdown engine in Jerboa is that it interprets basically any number as a clickable phone number: 123
They are separate. Think of community names like email addresses: [email protected] is different from [email protected]
Similarly, [email protected] is different from [email protected]
I’m commenting here from another instance (feddit.de) where I’m logged in and this community is available at https://feddit.de/c/[email protected]
Similarly, you can just access communities from other instances here, e.g. https://lemmy.world/c/[email protected]
Then ask your instance admin to update to 0.18.4. I don’t see this bug using the same Jerboa version on my home instance, which has already updated.