Thanks, I didn't notice that before. Looking at the modlog, I'm guessing may have actually been for the use of a t*rd suffix ... I think? The log doesn't really get specific enough.
Yet, in the thread I presumed it was for, another user not only used a full-on r-word but also directed it at another user. They are still active and posting.
Hmm....
Where do you find this info?
Jesus christ. This is what's wrong with internet discussions. There is no room for nuance and everyone just assumes the worst of everyone.
I wasn't blaming anyone for anything. All I was saying is ... murder is, y'know, bad and you should maybe try not murdering. I can't believe this is controversial or ban-worthy.
Edit: downvoted for saying murder is bad. Cool beans.
Shadowbanned may have been the wrong term. I think it's actually just an account lockout.
By all objective measures, so did the person replying to me. They're still galavanting around lemmy advocating for murder.
So I'm pretty sure my lemmy.ca account just got shadowbanned for telling someone that murder is NOT acceptable
Meanwhile, another account is still out promoting murder as of less than an hour ago. Boy, lemmy sure is a great alternative to reddit.
Seriously, what the fuck?
Edit: not shadowbanned, but account lockout/suspension. Would be nice to receive some sort of notice.
Yeah, I gotta be honest, it works really poorly here, especially when viewing all/hot. It's just constantly loading new posts and pushing down and off-screen whatever you're trying to read or click. It's frankly unusable.
This type of thing should be a user setting, not a site wide setting, IMO.
Yep, this is exactly what I meant. Just the option to disable auto post loading so you see whatever posts where loaded at the time you initially opened the page. If I want to see new posts, I can hit reload myself.
Well, I'm here, aren't I?
Forearms. It's always forearms.
I mourn what it was, yes.
There was a recent comment I read about how it's become this incredible resource for the most obscure tech issues and they were reluctant to delete their posts and accounts because they'd receive random messages of thanks years after a tech resource post was made.
And it's true. Reddit has become an invaluable resource for these kinds of things. Not only that, but it's one of the few places that exists on the web where cohesive and coherent discussions even exist. It was always the community and discussion that made reddit great and they want to turn it into yet another swipebait infested serotonin sponge. I sincerely hope lemmy can take its place, but there are going to be some major growing pains if we get big influx of "redfugees."
It almost makes me think that when something becomes such an enormous and invaluable public resource, there should be a legal compulsion to archive it before doing anything that will compromise its accessibility.___
After hearing the call audio — and I am not defending spez here — I can actually understand how it might have been initially perceived as a "threat" given the context of the conversation. It was a mix of technical and financial negotiations (or really just spez saying "this is how it is, you can suck it") and Christian was speaking metaphorically about Apollo's API calls being "noisy" and (at least how I understood it) was suggesting perhaps "quiet" it down by optimizing the software.
I am not trying to victim blame here and it absolutely does not excuse spez turning around and publicly shit talking Christian, especially after spez immediately apologized on the call after admitting to misinterpreting what he heard ... anyway, the point I'm trying to make is that it's important to communicate clearly, directly, and unambiguously.
The headline is still that spez is a greedy sack of shit.
Particularly in the way that lemmy isn't finance bro bullshit
Reddit following in their footsteps shortly after
Right, good point. Scroll down, it disappears. Scroll up, it reappears regardless of scroll position.
It's a banana, Michael, what can it cost, $10?
It'll be like a trainwreck in slow motion
I'm feeling rather smug and justified telling my clients to keep files on a local server that they control rather than "the cloud" someone else's computer.
Good question. Not sure what the best procedure might be here. Could be as simple promoting them in order of initial mirror deployment dates and the others become mirrors for the newly activated instance.
Triggering the activation could be a part of an instance decommissioning procedure where the operator selects the mirror to become the successor. Maybe there could be some basic system specs and network performance reporting so they could choose the optimal instance. Users would receive a message that their account is being moved to another instance and domain.
In the event of an unexpected outage, there could be a deadman switch style timeout where the fastest mirror activates automatically after the original instance is out for long enough, but also a process for the operator of the downed instance to delay the takeover by signaling, "I'm working on it." In the event of automatic takeover, since users wouldn't be able to receive messages, there would have to be some sort of global lemmy notice system so users of the downed instance know where to go, like a sticky post on the front page or maybe just a separate "notices" page.
This is definitely my main concern with this federated infrastructure. It's a neat way of keeping things decentralized, but when an instance goes down, everything's just gone.
There needs some sort of backup system, maybe something mirror instances, where anyone could spin up an instance with the sole purpose of mirroring another instance in case the original goes down. Anyone could mirror any number of instances. I think that would be a huge plus for lemmy.
Some UX & UI issues I've come across and some suggestions to address them
issue: menus are not always immediately apparent
suggestion: style menus like sidebars (outlines and backgrounds)
------------
issue: user menu elements on mobile are jammed against left edge
suggestion: add left padding
------------
issue: content and comments are too narrow on large/wide displays
suggestion: add option to set min and max widths relative to viewport (CSS VW)
------------
issue: main menu (from hamburger button) elements on mobile/narrow displayed as block is unsightly
suggestion: elements should be inline-block until they cannot fit on one line
------------
issue: comment action icons are unnecessarily hidden
suggestion: show all comment icons persistently (could be grouped as [up/down/reply] on left, [message/flag/block/fav/source] on right; could be a user profile option to show/hide additional comment options persistently)
------------
issue: message notification (bell icon) often indicates unread count when all messages are read
suggestion: fix
------------
issue: auto-refresh on posts causes elements to move down as reading when scrolled
suggestion: implement option to disable auto-refresh OR move scroll position down correspondingly to total height of dynamically loaded post elements
------------
issue: (if above feature implemented) must refresh page if auto-refresh disabled
suggestion: add soft-reload button (reloads posts)
------------
issue: [subscribed|local|all] default from user profile doesn't work (always selects local)
suggestion: fix
------------
issue: no function to block a specific community from your feed
suggestion: add function
------------
issue: notifications view has no stateful awareness of viewing mode [unread|all] or [all|replies|mentions|messages]
suggestion: add stateful awareness to enable browser <|> navigation
------------
issue: replying to inbox comment/message does not display after submitting reply
suggestion: display reply to comment after submitting reply
------------
issue: [show context] from inbox comment does not display immediate parent comment
suggestion: [show context] from inbox comment should display immediate parent comment
------------
issue: when viewing context from comment on a non-local instance, you are not authenticated and cannot reply from context
suggestion: implement cross-instance authentication OR link to context in the currently-authenticated instance
------------
issue: [next] buttons have no stateful awareness (displays an empty page when clicked from the last page in a set)
suggestion: [next] should be statefully aware of page and be disabled when viewing last available page
------------
issue: when inbox messages appear as a notification, there should be a button to mark them as read
suggestion: add function
------------
issue: inbox messages are only marked read when explicitly clicking [read] checkmark button
suggestion: messages should be marked read when replying or navigating to context
------------
Hope this helps make some improvements to the UX! :)
------------
EDIT another one while I'm thinking of it: it would be nice for the top toolbar to be fixed at the top so you don't need to scroll back up to use it.