If this supported daylio (and the mood tracking that daylio uses), I would immediately switch.

just been cycling through them over and over again, if someone wanted to block them for curation, they should not have had a problem to do so by now. And I do have plenty that I don’t post from for comm making.

It’s good that you’ve narrowed it down, but cycling through them will continue to cause people to think you’re somehow a spam network.

You’d be surprised, Ive definitely had people ask me about instances that I’ve posted from. Especially funnier named ones like toast.ooo

I’m not asking for hard data, to be clear, but I would still argue that for the amount of people that see your posts (a lot, since you post a lot), the amount of people asking you questions about your instances is tiny. Most users don’t even comment, so the math there doesn’t really add up.

A big reason a crosspost won’t show, is if the other post is on a comm that isn’t federated with your instance or hasn’t pulled that specific post yet

But leaving a link to the original post would always show. Just like boost automatically does. You can see an example in this post: https://infosec.pub/post/40397999

basically by interconnecting instances I mean I’m encountering comms that the instance hasn’t federated with yet because nobody has subscribed from their instance to it. And nobody on that instance can see content from that comm until someone subscribes to it

I mean, that’s fine, but you don’t need to post from the account do to that. It doesn’t even need to be named with your username since you’d never post with it to begin with. It’s already an invisible action. So again, it’s not necessary to make your username seemingly associated with negative views such as spam networks or ban evasion to help instances with this. The cons still outweigh the pros.

Yea, but a big difference is, none of my accounts are actually banned from anywhere

It’s a low bar, to be honest.

I agree with you regarding Lund, however you aren’t floating these instances around in a positive way. A positive way would be much more organic and ideally you’d only post from one to really give it the positive energy it might deserve.

To be very clear here, I did not call you a spam network or spammer nor did I intend to do so. I said that it’s what your accounts look like at first glance to users that don’t know who you are. Lividweasel is saying this very thing, that they thought you were a spammer of some kind at first. This, and your unintended side effect of making Lemmy more challenging to curate, is really the main thing I’ve mentioned time and time again. I’m glad you’re at least willing to acknowledge that it’s making it more difficult for users to curate their feeds.

I do not agree that you’re boosting other instances simply by posting from them, and I don’t think the side effect you’re creating is worth the price. Further, I would argue that most users typically do not pay attention to the instance a user is from, especially when simply upvoting a post.

I also still don’t understand why you have to use the accounts you create communities with. Why not pick a primary and only post with that account? It would eliminate the “side effect” if you did that one simple thing.

The cross posts do not show properly in my case, only sometimes do I see them on your posts. Luckily, clients like Boost add a link to their original post when I cross post. It makes the cross post always show. You can see how buggy Lemmy is regarding baked in cross post links, since almost everyone above is saying that they can’t see that in their app. Why not add your own baked in link so that everyone can see that it’s a cross post?

What do you mean “better interconnecting smaller instances”? If it’s through cross posting, I doubt it, seeing as you don’t include the cross post link for maximum effect.

I also agree with lividweasel in that I grew to have a negative view on your army of accounts. It’s not necessarily your posts, but rather the way you post with dozens of accounts. Not saying that’s deserved, but if it happened to two of us, how many others get the same views? That can easily be fixed by simply posting from one account, instead of seeming like a spam network or ban evader. The only other user that I’ve seen do this type of thing is Monk, and I know your views of him.

mgtowlemmy

Why use so many accounts? Don’t give me the “I’m supporting smaller instances” take. It’s not supporting smaller instances when you make them look like they’re part of your spam network. If it’s to create communities on them, why not just post to them specifically? Why post to one of the larger instances with a million accounts?

It only serves to make it look like you’re a spam network while also making it next to impossible to block your posts. Users will try to block you, think they’ve successfully curated their feeds, only to have you turn up again. It’s not a great Lemmy experience.

It also is not a good look to strip any reference to the OP, cross posts exist for a reason. It just makes it look like you’re stealing people’s posts and trying to make them your own.

Do you have backups? You mentioned family photos, so I hope so. If yes, have you tested them? Remember, RAID (or RAID-adjacent) is not a backup.

What filesystem are you using at the moment?

Questions aside, since you have precious photos and are using RAID, I would absolutely get a UPS. This will save you a lot of pain in the future, and you can continue to use it while you wait to upgrade. You can find them for relatively cheap on ebay, just make sure whatever you get has a new battery (frequently listed as “NEW BATT” or similar). Bonus points for a USB connection to gracefully shut down your raid array, protecting it from getting corrupted.

For the drives themselves, even if you aren’t shucking them yet (shucking meaning taking external drives out of their cases to put into a server), I would use https://shucks.top/ to find the best deals per TB. This comes with the upside of allowing you to shuck them in the future if you get a proper enclosure or chassis, and you don’t have to buy an extra case. Interestingly, external drives (like those listed on the website above) are generally cheaper than naked drives, especially when priced per TB. If you want to avoid shucking entirely, you can pick up DC rated drives for relatively good prices on https://serverpartdeals.com/

The three main concerns with this setup, in my opinion, are power, heat, and speed. With raid, you’ll want the UPS as discussed, which covers the power issue. Since they’ll be in cases, it’s definitely possible they’ll heat up quickly, especially if you ever have to do a data rebuild or otherwise hammer them with lots of writes. As long as you’re able to keep them below 55-60C during those operations, you should be fine, but it’s something you’ll want to keep an eye on. Speed, meanwhile, won’t impact too much but you’ll probably notice some slow writes compared to having a drive over SATA. Rebuilds will be pretty slow.

Apologies if that was kind of rambling. I’ve been a data hoarder archivist for over a decade. I’ve gone through several iterations of NAS and learned some hard lessons along the way. I encourage you to keep thinking about how to best secure your data from loss; it’s good to ask questions like this.

I’m aware, but it should have been part of their build system and they should have, at the very least, had alarms for this.

That’s what alarming is for.

Well, that certainly would confuse users, yes.

🤮

I suppose, it just seemed like putting the blame on the consumers rather than greedy, short-sighted executives.

Confuses them?

I had a leg break which required hardware to be installed. I told the doctors that I smoked weed and they still gave me the “good stuff”. This was even at a Catholic hospital (gross), but I’m in the PNW so maybe that’s why.

Mayo tastes better too, in my opinion. It’s not healthy, but God damn, it’s fucking delicious.

To address your first edit, yes, it’s a script, and yes, it did delete the site and the backups, as confirmed by the site creator. You can browse the data extracted on https://okstupid.lol/

This wasn’t “just a fun script”. The site, backups, and infrastructure were actually deleted.

Did you read the article, like at all? It would have told you the same thing:

As of this writing, WhiteDate, which Hoffmann described as a “Tinder for Nazis”; WhiteChild, a site that claimed to match white supremacists’ sperm and egg donors; and WhiteDeal, a sort-of Taskrabbit-esque labor marketplace for racists, are all offline.

The administrator of the three websites confirmed the hack on their social media accounts.

“They publicly delete all my websites while the audience rejoices. This is cyberterrorism,” the administrator wrote on X on Sunday, vowing repercussions.

The administrator also claimed that Root deleted their X account before it was restored.

I say this lie every day these days.

1.7/10, nice

Like dgdft said, if you’re using certbot, it should typically be running on the machine that your endpoints are hosted on. Enterprise solutions don’t require this, but they have other means of deploying certificates automatically and alarming if they are unable to, before they expire. My organization has dashboards showing which certs expire and when, and it triggers alarms at least a month before anything goes wrong.

High stakes automation should always have alarms on error, and since certs have set expiration dates baked into them, you can alarm far before anything goes wrong. Apparently, Riot didn’t have that.

Also, more frequent renewals make it so that people are less likely to forget it exists. Because of that, along with the possible security ramifications, 2 to 10 year certs should never be used, in my opinion. A 10 year cert will always get kicked on to the next team and it’s very possible for things to fall through the cracks.

What makes you think I don’t do this on embedded devices? I’m not about to dox my self with specifics, but I do this exclusively for embedded hardware as my job. We even do it for devices not directly attached to our network. It’s really not difficult so long as you have control of your enterprise hardware (which, you should, unless your management is terrible at their jobs). Hell, even the routers we use have this functionality built in, failure alarms and all.

If this is a problem for you, it’s probably at an organizational level, and not a technical issue.