I took a look through the twitter, which someone mentioned in another thread.

Given the 4chan like aestetic of your twitter post, I decided to take a look through the boards and it only took me less than a minute to find the n word being used.

Oh, and all the accounts are truly anonymous, rather than pseudoanonymous, which must make moderation a nightmare. Moderation being technically possible doesn’t make it easy or practical to do.

I don’t want an unmoderated experience by default, either.

No, I’m good. I think I’ll stay far away from plebbit.

To be pedantic, lemmy is federated, rather than decentralized (e.g. a direct p2p architecture).

With decentralization, moderation is much harder than federation, so many people aren’t a fan.

I’m not spotting it. “AI” is only mentioned once.

The key and secret in the docker compose don’t seem to be API keys, but keys for directus itself (which upon a careful reread of the article, I realize is not FOSS, which might be anpther reason people don’t like it").

Directus does seem to have some integration with openai, but it requires at least an api key and this blog post doesn’t mention any of that.

The current setup they are using doesn’t seem to actually connect to openai at all.

There’s only one project that provides truly static/relocatable python that work on both glibc/musl: https://github.com/leleliu008/python-distribution

There is the python provided by APE/cosmo. They also have two other distributions containing various goodies, pypack1, and pypack2. https://cosmo.zip/pub/cosmos/bin/

But this came at the cost of discontinuing support for Android & Windows

I don’t care about android support, but for the competition, and I don’t really know about Windows support. Right now, RDP is used to authenticate and managed the machines, but maybe a portable VNC we can quickly spin up, so more than one person can be on the same machine, would be useful.

My original thought was to replace in place, insecure services with secure one’s via something like docker containers or nix. But I think many of the machines have too little ram bundled libraries for the services to be viable. I actually tested replacing apache, but it simply wouldn’t launch (I think the machine only had 2 GB of ram?).

There are a few reasons why I really like it being public, even though it means I have to be careful not to share sensitive stuff.

• It creates a portfolio for me (I’m an undergrad) because I document my projects on there
• When asking for help with certain complex things, it’s really easy to simply link to my blog, since I document almost everything I’ve tried and why it did or didn’t work. Here’s a recent example
• I can share cool stuff I have saved, like my lists of learning resources or lists of software, with others easily.

This isn’t exactly what you want. But I use a static site generator, with a fulltext search engine (that operates entirely locally!), called quarto. (although there are other options).

Although I call it a “blog”, it really is more of a personal data dump for me, where I put all my notes down and also record all my processes as I work through projects. Whenever I am redoing something I know I did in an old project, or something I saved here (but disguised as a blogpost), I can just search for it.

Here is my site: https://moonpiedumplings.github.io/ . You can try search at the top right (requires javascript).

Are you using rpmfusion?

Lol I misread it too.

There is literally no way to do performant e2ee at large scale. e2ee works by encrypting every message for every recipient, on the users device.

At 1000 users, that’s basically a public room.

I have been using your stuff since they were called toolpacks.

https://moonpiedumplings.github.io/playground/ape-experiments/

Welcome to Lemmy, Azathothas. It’s nice to see more and more usernames I recognize show up here.

There a source port of at least portal 1.

https://github.com/AruMoon/source-engine

Here’s the active fork of the original project. Going through the issues of the original project, it seems to have support for building for 64 bit platforms.

No portal 2 support though. Although mentioned in the issues of nileusr’s repo is this: https://github.com/EpicSentry/P2ASW , which is interesting

I think the mistake is they titled it “The last note taking app you’ll ever need” instead of “The last note taking app I’lll ever need”

Yes, seriously. The article seems to talk mostly about their personal usecases, which is fine. This app is great and it works for them. But it won’t work for everybody and the title should probably respect that instead of having a grating title that evokes a knee jerk reaction.

Databases are annoying it is legitimately more difficult to export data from a database to another, than it is to copy markdown notes from one folder to another. In addition to that, there are also tools that process markdown and do cool stuff with, like pandoc, beamer, revealjs, etc, which can’t really be done with the more opaque database format.

Also this notetaking service only appears to work while online. Again, fine for them — but a dealbreaker for many people.

Alright, this is gonna be long.

Firstly, yes, different static site generators have different templating langauges. But just like normal programming languages, it is easy to transition from one templating langauge to another. If you take a look at the syntax:

• Pelian: https://pypi.org/project/Jinja2/
• Hugo: https://pkg.go.dev/text/template, https://pkg.go.dev/html/template

Not drastically different, but reading the docs, they are all similar enough, and easy to learn.

I wouldn’t call go’s templating language “esoteric”, but it should be noted that jinja2 is has other uses, most notably it is the templating engine that Ansible uses.

As for the docs… This could probably be a blog post by itself.

Firstly, take a look at this website: https://killedbygoogle.com/ . Google has created and then killed 296 projects, many of which were actively used and working. Why?

This is because, internally at Google, you get promoted if you either A: write software, or B: add more features to software. So what happens is people write software, get promoted, and then realize they don’t get paid more if they actually maintain that software, so they just kill it. Also, they forget to write documentation (because it doesn’t pay more or get you promoted).

Hugo, is by a Google Engineer, and it shows (or at least, it used to). Software by Google has two distinct characteristics (actually 3 if we count being written in Go).

• It has every feature you could ever want, even stuff you haven’t heard of
• And it’s poorly documented. Or not at all lmao.

But, “being poorly documented” is not a permanent fixture of this software, but instead something that mostly persists for as long as it’s Google software. Often, these projects get “adopted” by the wider community, who fixes up their documentation. Looking at hugo’s docs, it doesn’t seem be nightmarishly bad, especially for the core, main set of features. Like the setup docs appear to be clear (although a more complex process than alternatives).

But like, for search options: https://gohugo.io/tools/search/ . That google software pattern continues. There are like 10 options on the page, and no docs from hugo on their usage/installation lol.

Anyway, I would recommend eithier Pelican or Jekyll, given your requirements. Because everything you write is in markdown, it will be fairly easy to move from one static site generator to another, even if you are dissatisfied.

Also, kinda sorta relevant:

(source)

But the point I’m trying to make is the same. Don’t agonize over selecting the perfect static site generator.