Just this guy, you know?
What?
Compiling quality datasets is enormously challenging and labour intensive. OpenAI absolutely knows the provenance of the data they train on as it’s part of their secret sauce. And there’s no damn way their CTO won’t have a broad strokes understanding of the origins of those datasets.
Or burned out because they get pulled into every project that’s gone off the rails.
Take it to an electronics recycling center. Seriously.
If you already have a homelab, you plan to replace it, you don’t want to repair it, and you don’t have an obvious use case for another machine (it’s just another computer; you either have the need for another computer or you don’t), then holding onto it is just hoarding.
If somebody wanted to draw animated kiddie porn they could still do that. How far would you go until you ban crayons
It’s genuinely impressive how completely you missed my point.
How about another analogy: US federal law allows people to own individual firearms, but not grenades.
But they’re both things that kill people, right? Why would they be treated differently?
Hint: it’s about scale.
The same is true of pipe bombs. But anyone can make a pipe bomb. Genie is out of the bottle, right? So why are there laws regulating manufacture and ownership of them? Hmm…
And how many times have you made this comment, only to have it pointed out that there is a big fucking difference between a human manually creating fake images via Photoshop at human speed using human skills, versus automating the process so it can be done en masse at the push of a button?
Because that’s a really big fucking difference.
Think: musket versus gatling gun. Yeah, they both shoot bullets, but that’s about where the similarity ends.
Is the genie out of the bottle at this point? Probably.
But to claim this doesn’t represent a massive shift because Photoshop? Sorry but that’s at best naive, and it’s starting to get exhausting seeing this “argument” trotted out repeatedly by AI apologists.
Oh, no worries, just figured I’d add that extra little bit of detail as it’s a useful hook into a lot of other git concepts.
For folks unaware, the technical git term, here, is a ‘ref’. Everything that points to a commit is a ref, whether it’s HEAD, the tip of a branch, or a tag. If the git manpage mentions a ‘ref’ that’s what it’s talking about.
deleted by creator
If you have an Android phone I can’t recommend Genius Scan enough. Fast, accurate, lots of features. I use it with syncthing by exporting the files to a folder that’s configured to sync the paperless input folder.
Just want to say thank you! Paperless is one of the first things I recommend to anyone considering self hosting their infra. Amazing piece of work!
deleted by creator
Amazing how Google and Apple differ on so much, but in this respect they are in total agreement…
“Huh weird, I tried to use and it’s not working. Welp, guess I better fix it…”
That’s a goal, but it’s hardly the only goal.
My goal is to get a synthesis of search results across multiple engines while eliminating tracking URLs and other garbage. In short it’s a better UX for me first and foremost, and self-hosting allows me to customize that experience and also own uptime/availability. Privacy (through elimination of cookies and browser fingerprinting) is just a convenient side effect.
That said, on the topic of privacy, it’s absolutely false to say that by self-hosting you get the same effect as using the engines directly. Intermediating my access to those search engines means things like cookies and fingerprinting cannot be used to link my search history to my browsing activity.
Furthermore, in my case I host SearX on a VPS that’s independent of my broadband connection which means even IP can’t be used to correlate my activity.
As a former product manager where the CEO led the sales team, I feel seen.
Honestly the issue here may be a lack of familiarity with how bare repos work? If that’s right, it could be worth experimenting with them if only to learn something new and fun, even if you never plan to use them. If anything it’s a good way to learn about git internals!
Anyway, apologies for the pissy coda at the end, I’ve deleted it as it was unnecessary. Keep on having fun!
No. It’s strictly more complexity.
Right now I have a NAS. I have to upgrade and maintain my NAS. That’s table stakes already. But that alone is sufficient to use bare git repos.
If I add Gitea or whatever, I have to maintain my NAS, and a container running some additional software, and some sort of web proxy to access it. And in a disaster recovery scenario I’m now no longer just restoring some files on disk, I have to rebuild an entire service, restore it’s config and whatever backing store it uses, etc.
Even if you don’t already have a NAS, setting up a server with some storage running SSH is already necessary before you layer in an additional service like Gitea, whereas it’s all you need to store and interact with bare git repos. Put the other way, Gitea (for example) requires me to deploy all the things I need to host bare repos plus a bunch of addition complexity. It’s a strict (and non-trivial) superset.
Absolutely. Every service you run, whether containerized or not, is software you have to upgrade, maintain, and back up. Containers don’t magically alleviate the need for basic software/service maintenance.
Agreed, which is why you’ll find in a subsequent comment I allow for the fact that in a multi-user scenario, a support service on top of Git makes real sense.
Given this post is joking about being ashamed of their code, I can only surmise that, like I’m betting most self-hosters, they’re not dealing with a multi-user use case.
Well, that or they want to limit their shame to their close friends and/or colleagues…
My Momentum 4s have 60 hours of battery life…