Is this normal? Seems like “Hot” would refer to posts within the last ~6 hours or so…
Yeah, I’ve read the ‘hot’ is broken. Lots of bugs still to be ironed out. They’re working on it.
This is fixed in the upcoming 0.18 release
Go for new instead, its always fresh! Once the bugs get sorted hot will be the goto again.
I don’t like new due to the amount of hentai i see in there lol
Turn off your NSFW setting in your user profile.
Or just subscribe to communities you do want to see, then use the subscribed tab.
I’ve opened a GitHub issue asking for a way to hide NSFW communities in All (without having to turn off NSFW entirely)
I think the NSFW tag has to be more sharp, like only literal porn or gore is tagged NSFW. One of the most frustrating thing on r*ddit was that regular memes or text posts would get tagged as NSFW just for containing a swear word or something, so turning NSFW completely off would hide a ton of regular stuff too.
The problem with subscribing to communities at this point is the lack of content. I subscribed to a few different baseball communities, but none of them have anything other than maybe a welcome post or a few gameday posts without any comments. Communities are duplicated on a bunch of different instances too, which makes things a million times harder than it needs to be. I have no idea if one of the half dozen baseball communities I’m in now will make it big, if a new one entirely will make it big, or if they’re all doomed to never have content.
Eh, Reddit had similar problems in the earliest days. One will win out. Not ideal, but it will get better.
Be the one to post! Invite people to discuss, and crosspost to other relevant communities so more people know the comm exists!
People won’t post if no one’s posting. It’s a vicious cycle.
I’m trying to post at least once everyday on my local community to help build the interest. Someone has to make the content haha. Try to do the same. It doesn’t really matter which one you pick, just keep posting to it. You can subscribe to them all and comment on them all.
You know that is entirely fair haha. I was thinking the same thing when I first started but I realized you can block instances as they come up and you won’t see them anymore, now that I’ve done it awhile they rarely comeup.
you can block instances
Slight correction (not to be pedantic, we’re all learning here): you can currently block communities, but not instances. (Apparently being able to block instances at the user-level is coming)
Ah yes that’s right, I have to stop using instance and community interchangeably lol
deleted by creator
I just saw your post from 1m ago at the top of my feed sorting by Hot. Maybe it is lag
No, hot is confirmed broken in certain edge cases. Here’s the github issue about it. It’s gonna be fixed in v0.18
It’s gonna be fixed in v0.18
Copium. From what I’ve been hearing 0.18 is gonna be utopia and we’ll have flying cars.
Not sure what you’re on about, the PR with the fix is merged and ready for the next release version.
0.18 will also remove websockets which will improve performance and error handling, but it will likely have it’s own complications.
They’re building the plane as we’re flying and simultaneously boarding more passengers.
They’re building the plane as we’re flying and simultaneously boarding more passengers.
Quite the perfect analogy.
Definitely not xD
Won’t fix usability issues with being the first subscriber to a community from an instance, won’t add multi-community views, won’t add support for grouping same-name communities from different instances, won’t add moderator tools, won’t add more granular federation options like Mastodon has, won’t fix certain Mastodon -> Lemmy headaches they’re dealing with, won’t add different approval modes for users to instances, etc etc.
There’s still a lot of work remaining to be done. WebSocket-related bugginess and the rankings are on the docket though.
Heck, I want to be able To make groups of any amount of communities; same name or not so I have some more granular “subscription” views.
You can check out the 0.18 beta, https://beta.discuss.online
Weird, this 0.18 beta shows BE: 0.17.4 version number at the bottom.
The front-end UI is 0.18, it’s still running the current backend.
Which end handles those pesky front page feed updates? Do you know?
I think it’s the backend. I visited and already my page pushed a new 1 up vote post to the top.
Front end. You can see on my instance (https://thelemmy.club) that issue is fixed by a hotfix release someone made. It’s only a few lines of code, I don’t know what build the discuss.online beta is using exactly. I was pretty sure it was 0.18 which removes websockets, which makes that problem go away.
Yeah, I think something’s broke. I’ve been noticing the same thing and was wondering if it was just me. Maybe super lag from the influx of users, or something broke.
Yup. All my posts in hot are now more than a day old
I think “Hot” is broken for large instances. I am using a small instance and “Hot” seems to be working fine. I see frequent posts that were posted within the last hour.
Yeah works fine for me too
Same here, all posts older than 24hrs. Found this one by sorting by top/day
Hopefully it gets fixed soon
I’m sorting by hot right now… and this post is currently 4 hours old
Sort by top of the day, this isn’t reddit.
It was literally broken though. Check the GitHub links shared elsewhere in this thread. All fixed now though thankfully.
Oh, didn’t know that
I’m just using the New view right now. Won’t be sustainable once the amount of content on Lemmy grows, but it’s working for now…
