At least 1% of the money being poured into “AI research” nowadays seems to be spent on spewing these breathless puff pieces everywhere. The other 99% is spent on datacenter costs, probably. I am so excited for the day this bubble will finally pop. Just imagine the firesales on GPUs and rack space. It’ll be glorious.

If we’re actually trying to achieve sustainability, we have to stop being consumers. “consume” means to use up and destroy leaving nothing useful behind. This is what consumers do. Think about this the next time someone says the “additional price is passed on to the consumer” and phrases like that. Want to stop paying those prices? Stop consuming!

Instead of sending your money to some evil dictatorship on the other side of the world to “consume” something else, we should be building a system and a society where we can give that money, probably a little more more money even, to somebody in your local community to do actual productive work that doesn’t destroy the environment.

Right to repair is a huge project that we need to force down the throats of the large corporations who want to keep us being consumers forever no matter how much it destroys the planet. But India can still do things like this even without having the “right” to repair, they just figure out a solution and do it anyway, and we can too if we learn from them. We throw away so much perfectly useful stuff. Not just electronics but everything in our modern world from clothes to cars, because economics has told us that it’s expensive to repair or repurpose or salvage, and cheaper to buy a new one, buy more, buy in bulk, buy and dispose. And it often is, but that’s false economics. It’s the economics of throwing more shit in landfill and digging up more tons of rock and burning coal to turn it into something new. It’s the economics with all the costs externalized onto the environment and onto the future. It’s the economics of us destroying ourselves.

Ugh, don’t give him any more reasons to attack Canada please.

Nextcloud Notes or Joplin (nevermind all the other features Nextcloud provides) tick most of your boxes. They’re more productivity focused than privacy focused, it doesn’t do “zero knowledge” encryption the way you’re describing, but I don’t really understand the point of that when you’re self-hosting and the server host belongs to you anyway. The federation may leave you wanting more and the collaboration might not be “real time” enough for you either, though. If you can build something better by all means go for it.

When it comes to TikTok it is less clear to me what a good decision would be

the fact a foreign and potentially hostile state can influence the people is a serious threat.

That seems pretty clear to me.

fail2ban is mandatory equipment for any ssh server accessible to the public especially on its default port. It’s highly configurable, but the default settings will do fine at making it statistically impossible for any user or password to be brute forced.

Well, in my hypothetical scenario, “gamipedia” is not going to have an article about “the sky is”, that’s not really its purpose. Ideally you’d only have one encyclopedia wiki, or multiple that are willing to work together and not duplicate each other’s content. If another competing supposed-encyclopedia instance called “assholepedia” does have an article about “the sky is: a liberal delusion”, then you block and defederate that asshole instance. No big deal.

Maybe I’m misunderstanding how it’s designed but I don’t think I am, and I don’t think that’s how this works.

A topic definition on the wiki includes the instance it’s hosted on. All links to that topic will go to that same instance and all the content for that topic will be served by the one instance as the authoritative source for “That-topic@that-instance” which is the link everyone will use. The federated part is specifically that you can link to topics on other instances and view them through your local instance.

For example, hypothetically, if you are a “fedipedia” author and you are writing a “fedipedia” article about a video game, and you mention a particular feature of the video game, you can include in your “fedipedia” article a link to a topic about that particular feature on “wikia-gamipedia” or even “the-games-own-wiki.site” and interact with and maybe even edit that content without needing to make accounts on all these other wikis. It’s like it’s all hosted on one centralized wiki, but it’s hosted on different servers that are all talking to each other.

Of course, it’s possible both our hypothetical “wikia-gamipedia” AND “the-games-own-wiki.site” will have their OWN, completely SEPARATE topics about the video game feature in question. The topics might even have exactly the same name. That’s allowed. In that case, you’ll have to decide for yourself which one is more credible and useful, and which one you want to link to and interact with, because yes, two different federated wikis can have different topics with totally different content.

Just like on Lemmy you can have two different communities with the same name but totally different people and content because they’re on different instances. That’s not really the general intention of how communities are supposed to work though. The intention is that you can pick the one community that is the “right” one for you, or the largest, and use that and hopefully other people will do the same. You can all pick that same instance/community, no matter which account you live on, even if it’s not hosted on your local instance. You don’t have to use the one from your local instance, or from any particular instance. That’s what the federation does.

Yeah when I first started there was one guy whose code reviews I dreaded, he would nitpick every detail and he would stand by it, he would tell me to do it a completely different way that was 10x more work. It felt like I would never get my stories done because I had drawn “that asshole” in the code review lottery.

Years later, I came to realize that he was actually the best, he taught me so much about the way I should be thinking of things and structuring things, that have saved so much time and trouble later on, I now specifically reach out to him for a review when I am trying to do something complex because I know he’s going to give me an honest, thorough and useful review. Nobody’s doing anyone any favours in the long run by rubber stamping things, it may help you keep your sprint velocity up, but it’s not going to result in high quality code, and the bad quality code will inevitably bite you.

I actually dare them to try. I’m really looking forward to the massive paychecks I’m going to get when companies are panicking to try to untangle all the absolute nonsense bullshit these AI companies are about to unleash into corporate codebases. The AI-slop bugfest will make the Y2K issue seem trivial. I’m so excited, the future looks very bright for human software developers.

My advice: Practice going over other people’s code with a fine-tooth comb looking for bad architecture, flaws and inefficiencies. You won’t always be right, you won’t find them all, but you’ll learn lots of skills you’ll need in the future. Whatever you do, don’t undersell yourselves, remember that your experience is valuable, and AI has no experience, it just has a huge library it can shotgun “solutions” out of. Half the time they don’t even compile, nevermind work properly, or efficiently.

I feel like 99% of the time that’s just a lazy or misleading excuse. I’ve worked in proprietary software development for 25 years and I’ve never worked for a company that didn’t avoid restricted third-party code like the plague at all times. In the few, rare cases when we did have to use some proprietary third-party licensed library, it was usually kept very compartmentalized and easy to drop out of the code specifically because we were always afraid the other proprietary code vendor could fuck us and jack up their prices or find some nasty way to make our lives difficult.

The excuse that there is some secret but legitimate third-party code they’re not allowed to share simply doesn’t hold water in the vast majority of cases.

More likely answers are that some beancounter somewhere still imagines that the proprietary source code could possibly be valuable in some hypothetical future acquisition (nonsense of course) even though it has no real commercial value, or fears that it could expose the company to liability if some security flaw or licensing violation is found (more plausible).

Ironically, perhaps the most likely reality for this resistance is that the software actually includes code that dictates they were actually always obligated to publish the source but never did. ie, GPL-based code. GPL violations are all too common in proprietary software and very few organizations have codebase governance effective enough to keep the situation under control with developers copy-pasting from anything they can find on Google. Releasing their plagiarized GPL source code would reveal to the world that they were not in compliance all along. Let it quietly die, and nobody ever finds out and they get away with it. It’s not simply that they’re embarrassed by bad code, it’s that their bad code will potentially incriminate them. Not worth the risk, and sometimes it’s not just a risk it’s a certainty.

The proprietary software industry relies on open source so much and rarely gives much of anything back. I’m fortunate that the company I’m working for now actually takes licensing seriously and does contribute to open source projects to some degree, although I keep insisting they need to do better.

They may seem like nerf when they first come out of the AI, but they turn into real bullets once they start filling people’s heads with convincing enough lies and falsehoods, and those people start wielding their own weapons against minorities, democracy, and the government. If the election of Trump 2.0 has not convinced you of the immense danger of disinformation and misinformation, I have literally no idea how anything could ever possibly get through to you.

That was unconfirmed but Louis Rossmann blew it up into a big thing. Don’t get me wrong, I love the guy, he’ll be the first one to admit he’s not perfect, but that was not his finest work and nothing about it was convincing. Brother isn’t perfect either, but as far as printer manufacturers go, they’re pretty okay.

I think context is what’s going to kill LLMs. They keep throwing hacks on top of it to try to make it understand context, but it never really “understands” it just makes it look like it is following the context by simulating a few pertinent cues. Every interaction is essentially a fresh slate with a few prompts hiding underneath to seed it with what looks like context, but trying to actually preserve the context of the model to the level that we would consider actual “intelligence” never mind long term planning and actual “thinking” would explode towards infinity so fast there are probably not enough resources in the universe to even do it once.

Back in the old days, a lot of people went through the “Linux From Scratch” process to literally build up the OS from absolute scratch. No distro, no packages, no precompiled kernel, nothing but the raw ingredients. It is a good way to really understand the fundamentals not just of Linux but of the whole computing paradigm our systems are built on. It is not as hard as it probably sounds, but it’s an investment. It takes some time and you need to put your brain in gear to actually learn.

Yeah, that’s all it is. Calibre Portable. In a folder on Nextcloud.

Kobo has a great balance of good hardware, good price, and good openness. It’s not perfect on any of those categories, it just strikes a nice middle ground balance to make it an extremely popular ereader for people who require the kind of openness people like us do. There’s really nothing locked down about them, they don’t do anything in particular to make it easy, but they don’t do anything to make it hard either. “koreader” installs very nicely on Kobo devices, and then you just load your books from Calibre (or right through USB if you’re hardcore for some reason) and you’re basically off to the races.

All the choices for “ebook stores” and ereader ecosystems are proprietary vendor-locked services with no self-hosting options. While Calibre is primarily a “local” tool it is a true alternative to all these proprietary services and I think it’s at least in the spirit of self hosting, if not strictly the letter.

For what it’s worth, I self-host a Calibre Portable library on Nextcloud, which enables me to access all my ebooks anywhere, and to upload new ones to my ereader from anywhere, as long as I have access to my Nextcloud. And I also share the same library through Calibre Web for when I don’t. I retain control of all my books, I remove all the DRM and convert them to epub. Calibre isn’t a hosted service on its own, but it fits nicely into the self-hosting ecosystem, and for that I am grateful.

Nextcloud AIO via docker is super simple and has clear instructions.

Install docker through whatever tools Fedora has to install packages/rpms/whatever. Then follow steps 2, 3 and 4 at least. 5 if you need it.

Discord is a completely proprietary walled-garden that bans third-party clients to maintain full control AND (soon) has Wall-Street-ownership.

Jitsi is open-source built with multiple open protocols BUT has Wall-Street-ownership.

Neither is great, but these are two distinctly different situations.