go-littr VS nix

If you're interested in Go, I develop such a project and the plumbing required for it.

The code is at https://github.com/mariusor/go-littr and you can check it out at https://brutalinks.tech

For people favouring to the old reddit interface more, I created another federated alternative: https://github.com/mariusor/go-littr (with an example instance at https://brutalinks.tech).

Sadly it received less publicity and mind share than lemmy, so not everything might be up to the expectations of the HN crowd.

The code is on github: https://github.com/mariusor/go-littr An example is at: https://littr.me Status: not done.

Considering it's received HN's kiss-of-death, perhaps a pointer to the code is useful: https://github.com/mariusor/go-littr

If you're interested in another option to lotide, I'm working on a very similar project to it, called brutalinks. You can check it out an example instance at https://brutalinks.tech. The code is on github and sourcehut.

I started a go project to create a link aggregator similar to HN and old reddit, but built on top of ActivityPub.

It's targeted at small to medium communities, but at the same time it can reach outward through the federation mechanism that ActivityPub provides. Outside of immediate support to intercommunicate with other instances of its own platform, it will handle interactions from the larger fediverse at large: Mastodon, Pleroma, Pixelfed, etc.

Currently this is a one man project, namely me, and I would welcome support in any area that people could help: development, design, documentation, graphics, copy, etc.

The project can be found at https://github.com/mariusor/go-littr, and if anyone is interested there is a mailing list where people can get in touch: https://lists.sr.ht/~mariusor/activitypub-go

Some details about the project can be found on its wiki: https://man.sr.ht/~mariusor/go-activitypub/brutalinks/index....

https://littr.me/ is another federated reddit-like project under development, a "link aggregator" as they call it. https://github.com/mariusor/go-littr

I see that people already recommended lemmy, but if you're looking for something closer to old reddit and hacker news I am working on https://github.com/mariusor/go-littr. An example instance is at https://littr.me

I'm building something that could help in this regard: https://github.com/mariusor/go-littr

It's a distillation of the early reddit into a discussion platform that speaks activitypub. This means that the goal is not to have "one site" to rule them all, but that communities can each create their own and then interact with others if they chose to.

An demo instance is at https://littr.me

> https://github.com/NixOS/nix/pull/9911#issuecomment-19252073...

As we covered in my last post, NixOS is a amazing Linux distribution for creating stable and declared environments. Now while this is amazing for a desktop setup, it is also perfect for a home-server or home-lab.

(Nix itself is slowly chugging along with Windows via MinGW - https://discourse.nixos.org/t/nix-on-windows/1113/108 and https://github.com/NixOS/nix/issues/1320 , for example.)

Nix is a cross-platform package manager. It uses the nix programming language. Nix and NixOs are often used in the same context, but while the first is a package manager, the latter is a linux distribution based on nix.

Today I want to talk to you about Nixos. What is it? Nixos is a declarative and reproducible OS, partly taking the words used on their own page. What does that mean?

Software developers often want to customize:

1. their home environments: for packages (some reach for brew on MacOS) and configurations (dotfiles, and some reach for stow).

2. their development shells: for build dependencies (compilers, SDKs, libraries), tools (LSP, linters, formatters, debuggers), and services (runtime, database). Some reach for devcontainers here.

3. or even their operating systems: for development, for CI, for deployment, or for personal use.

Nix provision all of the above in the same language, with Nixpkgs, NixOS, home-manager, and devShells such as https://devenv.sh/. What's more, Nix is (https://nixos.org/):

- reproducible: what works on your dev machine also works in CI in prod,

- declarative: you version control and review your configurations and infrastructure as code, at a reasonable level of abstraction,

- reliable: all changes are atomic with easy roll back.

Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.

- it reduces bloat, because you can generate an environment or OS image with only the software needed to run a specific program or service

My guess is that a big efficiency gain would come from the second point, because you don't waste CPU on code that you don't use.

Does this make sense? Has anyone explored this?

[0]: https://nixos.org

1) Setting up the development environment - I currently use devcontainers for most things, but may also dig into nix -> isolated, portable, repeatable development environment 2) Exploring Echo - understand routing, requests, response, etc. 3) Incorporate Templ - integration with Echo, template composition, etc. 4) Integrating TailwindCSS - config for use with Echo/Templ, development cycle, deployment, etc. 5) Add in HTMX - endpoints, template structure, concepts, etc. 6) hyperscript for interactivity - client side interactivity