you’re now hating the new DNC led by entirely different people who agree with you

no we’re saying the current DNC leadership is entirely uninterested in actually doing a fucking report, and the fact they wasted how many months and $$$$ on first commissioning and then trying to surpress this steaming pile of shit is damning enough on its own.

An 8th grader is held to higher standards than that drivel was. And there has been no evidence the DNC has improved under the new leadership in any dimension. they still suppress any criticism of gaza, there has been no change in rhetoric around middle class economic policy.

its pathetic. what a competent group of people should have done was immediately publish the piece of toilet paper that it is and said ‘we’re commissioning a real one’ and start the fuck over and ban the moron and anyone associated with that report from ever being involved w/ the DNC again.

drives ad revenue!

they literally just gutted voting protections for minority groups they are absolutely doing the things they were appointed to do.

or 99% of the people running instances will want those defaults and its not worth the effort to deal with people like you to bother making it brain dead to disable.

trust me adding friction to a codebase is the a easy way to not have to deal with you.

for example imagine having ti field nonsense feature requests from people who cant even be assed to do basic research on how to remove the blocking configuration. that’d be infuriating.

the average person isnt running their own software stack. your complaint was its hard coded. it isnt. your complaint was that it couldnt be changed. it can. you were simply wrong on all counts and are now moving the goal post to make yourself feel better.

PEBCAC. this is a skill issue not a statement of fact. you not knowing how to operate the software is different from the software mandating things. maybe you should go find the code and understand how it works before making wild claims that are a result of your incompetence.

Fun fact: since someone did provide receipts and I did look at the code. its trivial to remove both domain blocklist and the instance block list in about 40s of work.

1. open db terminal
2. truncate blocklist and domain list tables.

smile I assume most of the individuals crying foul here are just generally confused about many things.

laugh in other words you dont know wtf you’re talking about. no one is saying piefied’s codebase doesnt have block functionality or that its available by default. the problem is you shits are saying its mandatory, when in reality it almost CERTAINLY isnt and then you can’t even be half assed enough to ask an LLM to find the code to prove your position.

stop wasting everyone’s time with your childish nonsense. and be happy someone else did your homework for you and you were entirely incorrect.

so no proof got it. note other people in the thread mentioned DB records you need to clear out. fairly trivial work if your hosting systems.

citation needed. no one has provided evidence of that and i highly doubt it simply due to the multiple claims by individuals here crying foul claiming multiple versions of how that block list is stored. not to mention, you know, it’d need to be updated periodically.

and provided zero proof of this fact. feel free to provide that proof. I’m too lazy to go research the codebase but i highly doubt they hard coded it.

provide proof. highly doubt that.

who can’t opt out? just use a different instance if you dont like an instances setting. no one owes you anything. or run your own and just change the setting.

sounds like exactly what piefied did, they provide a default set of sites and you’re free to adjust them on your instance as you feel.

blocking trash sites on your own instance, and providing default settings is perfectly reasonable.

I imagine having 100% uptime is much harder the bigger a platform is, so did Github grow a lot in the same period?

its not there are scale points where once you hit a critical number you need to re-architect your backend. 1k,10k,1mil, etc. usually these vary based on your app. but they’re usually exponential so once you hit the higher levels it takes much longer to reach the next level.

on top of that you usually by the higher tiers have proper backpressure and signals being sent to the frontend systems to dynamically manage the load generated. so suddenly uptime is much easier.

when you see large repeated failures like this the cause is almost always corporate causing issues.

• reducing engineering budget.
• not listening to engineering department on product decisions. (see the recent product manager AI generated commit that got merged and caused a mild uproar of 'co authored by copilot)
• rushing nonsense out before its ready.

it this particular case i bet it cutting engineering head count and increase AI slop generated code without proper review by engineers. which ive been hearing a lot more from my engineering friends.

oh no! and none of that really matters to this person they just wanted an easy way to manage shit.

and I also develop software. lack of sandboxing is hardly a deal breaker. its just something you manage and if you care you ensure stuff is properly boxed.

appimage does have tools that are capable of sandboxing quite effectively and automatically.

what precisely about this do you consider insecure? do you understand how appimage works?

say it with me: ‘republicans have the edge in rural states because democrats ignore working class interests and do nothing to support them, republicans at least blame illegals for stealing muh job!’.

the fact is the largest voting group are working class indepedents, and neither party appeals to them.

they really dont have a numbers advantage. both partys are just terrible. the difference is republicans do what their base wants. while democrats shit on their base constantly.