Welcome and I hope you enjoy interacting in this space!
One thing to note is that communities across the instances (lemmy.ml being an instance) will have varying content and vibe, and may differ from what you might expect of an instance. So if you’re selective with the communities you subscribe to and typically only scroll through your Subscribed front page, filtering out lemmy.ml might not be necessary.
Huh, never thought about it this way but it makes sense. Ultimately the URL will be identical across the different posts, and I believe a Post object has a URL field.
I would suggest looking into subscribing to and engaging with communities from the programming.dev instance. While they continue to exist, and Beehaw is federated with them and vice versa, Beehaw users like you and me can do so!
Sorry, 1984 references!
It was said during the Two Minutes of Hate. The Brotherhood shall be sending a visitor to pay you a visit soon.
Assuming you’re viewing on mobile, at the top of the page, there should be a Sidebar button. Click that and it will expand the sidebar. There should now be a Subscribe button for you to subscribe to the community.
Note that the URL should look something like <local instance url>/c/<remote channel>@<remote instance hostname>. For example, my local instance is Beehaw too and I’m trying to view AskLemmy on lemmy.ml, so it should be something like beehaw.org/c/asklemmy.ml
Sweet, that’s awesome! What are you studying at Uni?
When I was learning to code, I always wished that I could learn while applying it to solve “real world” problems!
This probably needs verification, so run at your own risk!
The SQL statement to delete would be: DELETE from person where name = '...'
person is the table of users.
name = '...' is the condition for the row that is to be deleted.
You can also modify the condition to, for example, delete a user using the id instead of their name (username).
Here’s a link to the “schema” of the person table as generated by the backend code.
What do you mean by collapsing threads? Currently if you clicked on a comment, it should collapse said comment and any children of the comment.
With regards to navigating to the next/previous top level comment, worth putting that as an “issue” on Jerboa’s GitHub as a feature request if one doesn’t exist for this feature already.
If you don’t mind sharing, what’s the name of this place?
I had a one day transit through Japan not too long ago. We made our way to the Golden Gai area and had some absolutely delicious niboshi ramen too! The place we went to is named Ramen Nagi.
And of course, it uses a ticketing machine just like this picture! =D
At least according to this article, it seems like Wayland enabled by default will be for the next release!