It seems that something went wrong with our nameserver, thus no connections to the 'outside world' were working. As soon as I added a new nameserver, federation started working again (this also affected server updates).
This is my favorite version of this so far.
I'm not in the business of collecting user data and don't really want to be. In regards to logs, we restart our containers every 6 hours and the logs are wiped at that time, so the furthest back logs I can actually find in our system are from an hour ago.
And nah, I wouldn't give in. There's no real reason to request that information, as accessing a url means absolutely nothing. I did so just now to verify things and the same could be argued by any real user (oh, I clicked on the link and didn't know what it was going to). I very much doubt the past 6 hours of logs would be useful anyway, as by the time I got the request the logs wouldn't matter anymore.
But, I'm still going to see if I can turn off logging for requests. I do not think we need them at all, and if we do, we can simply turn it on for a few minutes to get the info we need.
Skewed priorities like trying to make sure that Firefox continues to exist even with the massive amount of competition in the browser space and everything being taken over by chromium. Yeah. Definitely skewed priorities.
Or it’s because Tesla is like 60% of the market and their quality is absolute shit. https://insideevs.com/news/686440/tesla-60-percent-ev-market-share-new-registrations-2024/
If that’s the first thing you see then maybe you have a problem. It took me a full 20 seconds to see it.
Just so you know, companies already use drones for roof surveys. I work for sunrun and we use them to analyze roofs for solar installations and whether roofs need to be fixed before hand.
Well it sure does sound like advertising won doesn’t it. I completely stopped using Google it is so bad now.
My first comment directly discusses the issue at hand. It wasn’t off topic. It’s clear you didn’t want any feedback on the issue because it makes you look bad. I explicitly talked about how client side scheduling is a bad idea that does not accomplish the goal of scheduling. And then I gave feedback directly concerning the exact issue I was commenting on of how your conduct was unfitting of lead devs of a major software project, where you squabbled in public in a really weird way, and you refused to even think about discussing the topic (closing the issue over and over again when your coworker had opened it and asked for discussion? Really dude?). Then you finally banned me without any warning or discussion of why.
And no, it’s not going to teach me any lesson, all it did was teach the entire community you have no clue how to run an open source software project. No warning, no explanation, just juvenile marking of comments as off topic (they weren’t), closing of the issue your main dev opened and then boom banned.
Hey @db0@lemmy.dbzer0.com, just so you know, this tool is most likely very illegal to use in the USA. Something that your users should be aware of. I don't really have the energy to go into it now, but I'll post what I told my users in the programming.dev discord:
that is almost definitely against the law in the USA. From what I've read, you have to follow very specific procedures to report CSAM as well as retain the evidence (yes, you actually have to keep the pictures), until the NCMEC tells you you should destroy the data. I've begun the process to sign up programming.dev (yes you actually have to register with the government as an ICS/ESP) and receive a login for reports.
If you operate a website, and knowingly destroy the evidence without reporting it, you can be jailed. It's quite strange, and it's quite a burden on websites. Funnily enough, if you completely ignore your website, so much so that you don't know that you're hosting CSAM then you are completely protected and have no obligation to report (in the USA at least)
Also, that script is likely to get you even more into trouble because you are knowingly transmitting CSAM to 'other systems', like dbzer0's aihorde cluster. that's pretty dang bad...
here are some sources:
- https://www.law.cornell.edu/uscode/text/18/2258A
- https://crsreports.congress.gov/product/pdf/LSB/LSB10713
- https://www.missingkids.org/theissues/csam
- https://www.cloudflare.com/service-specific-terms-application-services/#csam-scanning-tool-terms
- https://developers.cloudflare.com/cache/reference/csam-scanning/#what-happens-when-a-match-is-detected
- https://developers.cloudflare.com/cache/reference/csam-scanning/#what-action-should-i-take-when-a-match-is-detected
Hi, programming.dev owner here. From what I've been seeing it's a lot of memory issues. We were hitting swap which was causing massive disk io. You can see what happened with the disk io immediately after the upgrade to more memory.
I know at least one reason is being resolved in this PR
We were also having issues with the nginx config. There were some really weird settings that I don't think were necessary. Finally, the federation is quite busy. So if someone subscribes to events from 10 different servers, we pull in every single event, even upvotes. There's currently a lot of work being done around this stuff.
I don't think Rust is the problem. I think it's just a growth thing. Every platform has growth challenges, things grow in ways that you never expect. You might have thought that it was going to be IO constrained due to the federation, but in reality it's memory constrained because memory is actually the most expensive thing to have on a server. etc.
https://programming.dev/comment/10856293