You: literally splatters shitty posts into a thread
”Why am I being downvoted”
I vaguely remember that one of the articles talking about the physics forum mentioned it happening elsewhere, but I haven’t dug into it myself. it might just be one or two shitty admins doing this, but I suspect (without evidence, I just can’t think of another reason to do it) there’s some party offering a financial incentive for them to go back and fuck up their old forums
I think you’re absolutely correct, and this feels to me like the only reason why we’re seeing some of the bizarre shit we’ve been keeping an eye on:
- several old forums, all of which are unique high-quality data sources, are being polluted by their own admins with backdated LLM-generated answers. this destroys that forum as a trustworthy data source and removes it as competition for the LLM that already scraped the forum — and, as a bonus, it also makes training a future LLM on that data source utterly impractical without risking model collapse.
- Wikipedia refuses to compromise on quality in general, so it’s under increasing political pressure to change. the game here is to shut down or pollute the original data source by any means necessary, so that the only way to access that data becomes an LLM. the people behind the AI startups are experts at creating monopolies, and shutting down a world-class data source like Wikipedia or making it otherwise unusable would guarantee a monopoly position for them.
I keep stopping myself from doing this exact project, with the fediverse as the curation source, several times. I’ve talked about this before, but interestingly Postgres’ full-text search is effectively the complete core of a search engine, minus what you’d need for crawling and ranking (which is where curation and a bit of scripting would come in)
other than resources and time, one big open question is how to do this kind of thing as a positive part of the fediverse — to not make the same mistake that a bunch of techbros already have and index the fediverse without consent. how does one make the curation process simultaneously consensual and also automated enough that it can be reasonably ruggedized against abuse?
The philosophy is: your content is what matters, everything else is a bonus. Put in effort, not money. We’re making punk rock here. I did fanzines in the ’80s and books in the 2010s on the same principles.
this is brilliant, and it’s worth keeping in mind for anything independently produced or self-hosted. for our instance’s infrastructure, I do as much as I can with what we’ve got before I increase our monthly bill, and with proper planning you can make the compute you’ve got stretch to handle a lot more requests and users than you might think from modern cloud doctrine, which is built around throwing money at your problems.
to return to the subject of media production, it’s very easy to spend money and damn yourself into spending more later: an expensive microphone might need an XLR soundboard or newer audio computer to work well, the expensive video editor likely comes with a subscription fee or paid upgrades, and so on. it’s unwise to start out by splurging, because working on the style and content of what you’re producing will get you better results for much cheaper, and you won’t trap yourself into paying more than anticipated.
Export at 720p as “MP4 (H.264 va).” I could go to 1080p, but this is a talking head show and you don’t need my nose hairs that sharp.
this is an excellent point too, and it’s something that’s easy to forget just viewing videos. as a viewer, I usually want 4k if it’s available but will go down to 1080p or 720p if bandwidth’s a concern. for production: chances are 720p’s more than enough to start with, especially for YouTube, and it needs a whole lot less in terms of resources and attention to detail to look good than 1080p or especially 4k.
also, I forgot to point this out earlier, but it’s worth saying: the only reason why I’m considering GrapheneOS as a viable path forward is because as an AOSP fork, it isn’t all-or-nothing. I can create a private space or profile for Google Play Services and all my spyware shit and keep it isolated, and ending the session kills all the processes those apps might have been running.
that’s fantastic! I finally don’t have to switch fully to open source apps and do without working non-janky notifications to have a modicum of privacy on Android! the graphene devs assume I’m not gonna be perfect and they ruggedized their fork against that and put a ton of effort into making even stuff that’s deeply reliant on Google safer! why in fuck aren’t they like that for everything?
To be clear, this is not a rant against security… I treat security of my devices seriously.
exactly! and taking this shit seriously is why this overbearing shit sucks, especially when it’s theater or enforced for threats that aren’t realistic for your threat model. unlike some of these fuckers, we both actually intend to daily the devices we’re locking down.
because apparently having non-smooth scrolling can be fingerprinted (that being possible is IMO reason alone to burn down the modern web altogether)
oh I fucking hate this. it’s the same shit as forcing dark mode off/on as part of fingerprinting protection. not only is this the absolute wrong way to fix that shit, it’s pretty monstrous for anyone who needs dark mode or light mode to use their device in anything resembling comfort — your user may have a visual impairment or severe light sensitivity, and now they’re fucked cause the developers couldn’t accept a minor fingerprinting risk (and light/dark mode and smooth scrolling are both utterly minor, to be real)
Possibly controversial, but I’ll say it: web browsers being so annoying about self-signed certificates.
motherfucker yes! the CA infrastructure is nowhere near usable for all cases and we all know it, but locking down the web and making development and self-hosting fucking annoying is the game for the browser vendors and Google in particular. to add to this: why the fuck is my browser acting like me not having a cert for localhost is a tragedy? why does the browser sandbox not allow certain shit unless I’m using https of all things to access localhost? where precisely is the fucking threat here? (I’m sure some well-paid security asshole at one of the browser vendors could snark a list of unlikely shit as reasons why local host needs to be treated as insecure with no toggle or dev tools option to treat it otherwise… and I just don’t give a fuck)
The entire reality of secure boot on most platforms
I’d love good secure boot! the one on PCs ain’t it at all, and unfortunately the secure ones tend to be used to lock out device owners from modifying what they own and implement shit like attestation that’s just there to violate your rights and make sure you’re not blocking ads, so unfortunately good secure boot might be incompatible with capitalism. for now though at least graphene seems to benefit from a secure secure boot chain that hasn’t been locked down yet?
the GrapheneOS developers would like you to know that switching to Ironfox, the only Android Firefox fork (to my knowledge) that implements process sandboxing (and also ships ublock origin for convenience) (also also, the Firefox situation on Android looks so much like intentional Mozilla sabotage, cause they have a perfectly good sandbox sitting there disabled) is utterly unsafe because it doesn’t work with a lesser Android sandbox named isolatedProcess or have the V8 sandbox (because it isn’t V8) and its usage will result in your immediate death
so anyway I’m currently switching from vanadium to ironfox and it’s a lot better so far
speaking of privacy, if you got unlucky during secret santa and got an echo device and set it up out of shame as a kitchen timer or the speaker that plays while you poop: get rid of it right the fuck now, this is not a joke, they’re going mask-off on turning the awful things into always-on microphones and previous incidents have made it clear that the resulting data will not be kept private and can be used against you in legal proceedings (via mastodon)
oh I meant the rant that started this thread, but fuck it, let’s go, welcome to the awful.systems privacy guide
grapheneOS review!
pros:
- provably highly Cellebrite-resistant due to obsessive amounts of dev attention given to low-level security and practices enforced around phone login
- almost barebones AOSP! for better or worse
- sandboxed Google Play Services so you can use the damn phone practically without feeding all your data into Google’s maw
- buggy but usable support for Android user profiles and private spaces so you can isolate spyware apps to a fairly high degree
- there’s support coming for some very cool virtualization features for securely using your phone as one of them convertible desktops or for maybe virtualizing graphene under graphene
- it’s probably the only relatively serious choice for a secure mobile OS? and that’s depressing as fuck actually, how did we get here
cons:
- the devs seem toxic
- the community is toxic
- almost barebones AOSP! so good fucking luck when the AOSP implementation of something is broken or buggy or missing cause the graphene devs will tell you to fuck off
- the project has weird priorities and seems to just forget to do parts of their roadmap when their devs lose interest
- their browser vanadium seems like a good chromium fork and a fine webview implementation but lacks an effective ad blocker, which makes it unsafe to use if your threat model includes, you know, the fucking obvious. the graphene devs will shame you for using anything but it or brave though, and officially recommend using either a VPN with ad blocking or a service like NextDNS since they don’t seem to acknowledge that network-level blocking isn’t sufficient
- there’s just a lot of userland low hanging fruit it doesn’t have. like, you’re not supposed to root a grapheneOS phone cause that breaks Android’s security model wide open. cool! do they ship any apps to do even the basic shit you’d want root for? of course not.
- you’ll have 4 different app stores (per profile) and not know which one to use for anything. if you choose wrong the project devs will shame you.
- the docs are wildly out of date, of course, why wouldn’t they be. presumably I’m supposed to be on Matrix or Discord but I’m not going to do that
and now the NextDNS rant:
this is just spyware as a service. why in fuck do privacyguides and the graphene community both recommend a service that uniquely correlates your DNS traffic with your account (even the “try without an account” button on their site generates a 7 day trial account and a DNS instance so your usage can be tracked) and recommend configuring it in such a way that said traffic can be correlated with VPN traffic? this is incredibly valuable data especially when tagged with an individual’s identity, and the only guarantee you have that they don’t do this is a promise from a US-based corporation that will be broken the instant they receive a court order. privacyguides should be ashamed for recommending this unserious clown shit.
new generational trauma just unlocked: your parents let spicy autocomplete make all their parenting decisions for them and think they’re too logical and rational to go to any of your art exhibitions
yep, your second attempt’s still a fashy dad quip about art and it’s still as funny as the grave. you haven’t produced anything with the subjective value of even terrible art, and I think it’s about time you stop trying