

reports currently go to community instance and the instance of the user that was reported, other than that there is no federation on the lemmy side currently.
other accounts:
reports currently go to community instance and the instance of the user that was reported, other than that there is no federation on the lemmy side currently.
that’s because SJW is still on 0.19.11. 0.19.12 fixes this by forcing new posts in NSFW communities to be NSFW. see #5649. the UI change made it in 0.19.11 already but the backend change was broken and not backported.
we’re currently looking into some performance issues, we’re looking into updating to the latest version this weekend, which fixes a few potential deadlocks. lately we’ve been getting DB deadlocks rather frequently, which results in significantly worse performance until we restart one of the services.
it’s in the main settings area:
check if your piefed account has pms from other instances enabled. afaik piefed.social had this disabled by default for some time during the nicole spamwave.
fyi also @Bonus@lemmy.world
the communities !rollerblading@lemmy.world and !monsterhunter@lemmy.world have both been deleted by their creators indeed.
here’s your rollerblading post:
Hello! I’m going to make a short review of the USD Aeon 80 Team inline skates, aimed at those who are considering buying them but are indecisive, like I was. To give some background, I’ve set foot in an inline skate one year ago, after last skating 15 year prior as a kid, when I only skated around the streets.
So last year I was searching for a skate which would allow me to cruise around the streets, use them for commuting, and occasionally learning some tricks at the skatepark. The skate that naturally presented itself was this skate, as it has large wheels (80 mm), and a soulplate and H-block for grinding. My biggest concern was about the unibody construction where the frame and the boot are one piece of plastic, i.e. no replaceable frame. Finally I decided to buy them, and here are my thoughts:
They are perfect! And I say that from a standpoint where I rarely go on the streets, but instead I go in the skatepark on average once a week throughout the year, and have been doing that for the last year (I very quickly switched the preferred way of usage). Anyway, for a level of skating where you don’t grind 24/7 on everything, the plastic will not wear down, so there is very little concern regarding the unreplaceable frame - it will not wear down as quickly as you may think. I’ve been practicing grinds in the park for the last year, and very little wear occurred. Granted, the grinds were on metal pipes and not on concrete, but still. If you’re not a hardcore grinder, the frame will not need replacement anytime soon
One other concern was if the grinds were even possible for a complete beginner like me, given the small H-block. Absolutely! I’ve learned the soul, acid, mizue and pornstar which require the H-block, and am in the process of learning the frontside (on which I’m not getting wheelbite in practice). The only problem I’ve encountered so far regarding grinds is the royale, but the reason for that is the height of the soulplate (and also the fact that I’m a beginner), which makes it hard to bend the foot so much to the required angle such that is touches the rail. Having said all that, for a beginner like me the “small” H-block did not present any issue.
Even though I now ride mostly in parks, I still commute with them and occasionally cruise around the city, and they are absolutely good for that too. No complaints here. You can normally do all the curves and power stops without touching the ground with the soulplate.
Now some additional comments. The main buckle… it is a good buckle which you need need to cut at the proper length so that it does not get in the way. However, when you skate with you legs too close together, one buckle can attach on the buckle of the other skate, and so one skate gets loose. Luckily, even though I experienced this multiple times during my sessions, I never fell because of that, the skates only get loose so you need to rebuckle. This is the only “complaint” I have for these skates.
The 45° buckle also needs to be shortened to the appropriate length to not get in the way (can also be seen from the above picture how long it is).
Lastly, regarding sizing. My feet are 266 and 268 mm long, and cca. 10 cm wide, and as per official recommendation I got the 41-42 and they fit PER-FECT-LY! Also, I recommend watching this video about new skates, includes fitting and other things.
To recap, the main concerns that I see people have about these skates are:
Both of these in my situation did not present any problems, even though I too had big concerns about them, but decided to just go for it, and now I’m happily writing this review.
Hope this helps someone clear their doubts and make their decision :)
For the last year I’ve been logging my sessions with all the tricks I’ve been learning, so I can share that too if you’re interested, and to further strengthen the argument that they are a perfectly good skate for the park!
All in all, I’ve been using them at least once a week throughout the last year, and these were all the observations I made.
P.S. I’ve been planning to post this on reddit, but given the circumstances I’m writing it here, in hopes to give a little boost to this community regarding content and visibility.
you can also click on the page icon below this comment if you want to get it in a format that can be copied to a new post.
My idea was to serve it in a way that would allow ActivityPub clients to resolve content still, while having a light static render for other clients for local content.
For content on other instances it would probably require some kind of lightweight redirection service towards the original item to be set up to prevent breaking those URLs.
This could probably be built just from scraping, without requiring database access.
I’ve considered setting up a static read-only copy of lemm.ee, but without being able to host this on the original domain i don’t think it’ll be of much use. i already reached out to @sunaurus@lemm.ee to see if he would be interested in something like this, doesn’t seem like anything was planned from his end so far.
can you think of any solution that is not a variation of “keep finding fresh volunteers to work until they burn out”?
how would paying admins prevent burnout? the only difference i see here is that it is probably easier to find people willing to do it as a paid job than volunteers, but they can both burn out. this would just change it from “keep finding fresh volunteers” to “keep finding fresh job applicants”.
Ruud and Stux are not the only people involved.
I’m personally only involved in Ruud’s side of things (mostly .world instances). Stux’ platforms are managed separately, I can’t say too much about those. Afaik finances between Ruud’s instances and Stux’ instances are also separate.
On the .world side, we currently have 6 active members for infra. For moderation, LW currently has 4 active instance admins plus some community team members with elevated privileges. Other .world platforms have moderation separate from LW. We certainly don’t have resources to hire professional admins, but I’m sure that we would find a viable solution if Ruud ever wanted to leave things behind. Not all solutions require paying someone a salary for it, which seems to be your implication here.
I don’t think “too big to fail” is as much of a factor here as the fact that LW is not the only FHF platform. Fedihosting Foundation, the non-profit behind Lemmy.World and our other platforms, existed before Lemmy.World already. While the Lemmy moderation team is working mostly independently from the rest of FHF, if the LW admin team disappeared there would still be FHF in a position to search for new admins and probably also at least temporarily step in without requiring to shut down the instance.
essentially start by identifying the accounts posting links to the domain in question, then analyze the voting behavior of the accounts upvoting these posts. you can start by sorting out accounts that have legitimate activity and then narrow it down further and find common patterns that only apply to these accounts.
most of them were also created in similar time frames.
edit:
to extend on this, once you have something to go on with it’s fairly easy. the hard part is finding something that applies in a more generic way to identify this happening before someone else discovers unusual voting patterns and reports them.
thanks for flagging this, i just banned 346 accounts involved in this scheme from lemmy.world :|
(unbanned at the time of creating the report) accounts posting links to the same domain:
accounts i’m highly confident were involved in vote manipulation here:
i’ve banned all the accounts i could identify as part of this scheme from lemmy.world now.
i originally sent them a warning before i was aware of the scale of this involving a bunch of alts with different usernames. if i had known that when i sent the warning it would’ve been a ban straight away.
they replied to my warning pretending they didn’t know about any recent vote manipulation, so they’re clearly not interested in acting in good faith going forward.
yes, we have a matrix room for coordinated efforts against spam and other types of abuse, which admins are welcome to join.
once lemmy allows reporting user profiles directly this will probably become more likely to reach the instances admins of instances that are less actively maintained as well.
I’ve sent out warnings to 10 other users in the past few days about similar behavior already and also banned two users for this type of behavior. one of them appealed and is unbanned again.
I also had this account in my list of such accounts, but I hadn’t followed up on it yet, as I figured I’d just deal with the top n users and then review it again at a later point in time.
i’ve sent them a warning about this as well now that they’ll get banned from our instance if they continue engaging in this behavior.
we currently have our own solution to send emails with a custom text explaining why people were rejected and what they can do next. we’ll have to review whether the built-in solution would be capable of replacing this functionality adequately if we add rejection reasons to lemmy when rejecting the applications.
our current solution rejects applications and then deletes the user from the database to ensure that they can sign up again if they want, as denied applications only get deleted after a week or so and an appeal process would require support tickets and a lot more time to be spent by us on addressing those.
our application process is fully automatic and just depends on certain words to be provided and the email not being disposable.
The link is up there in the post for you to use.
the implementation that piefed used to use made it trivial to link them to the original users, yes. this was an implementation flaw that could easily be addressed, which would make it less trivial to do so, mostly turning it into a probability assessment when correlating with other activity, provided that the pseudonymous identity is permanently tied to the real user.