GeekyLink

cross-posted from: https://yiffit.net/post/868741

This new version introduced a system so that your instance stops sending out content to other instances that are supposedly dead / offline.

Unfortunately for some reason there's false positives. When I checked comparing the results from a curl request vs the information in our Lemmy database I found over 350+ false positives.

In the DB there is a table called "instance" which has a column called "updated". If the date on that column is older than 3 days, your server will stop sending any content to those instances.

For some reason I had entries that were dated as last being alive in July, while actually they were always up. If an entry is incorrect, you can fix it by manually using an update statement and adding today's date. If your instance is not too large you can safely update all entries to today's date and check if everything works as expected from then on any new content created on your instances.

The dead instances won't have an impact unless your instance is larger and generates more content, thus it might be easier to simply update all entries and have Lemmy believe they're all alive if you start noticing wonky behavior and don't want to check one by one.

If you don't know how to access the database run this command where domaincom is your instance domain without the dot.

1. docker exec -it domaincom_postgres_1 busybox /bin/sh

2. psql -U

(The default user is 'lemmy') You could technically do this is one single step, but it's good to know the command to get shell access to the container itself if you didn't know how to.

This should give you access to a postgres CLI interface. Use \c to connect, \dt to list tables and \d+ tablename to list table definition. You can also run SQL queries from there.

Try with this query: SELECT * from instance to list all instances and their updated date.

You can use other SQL queries to get better results or correct false positives. Just be careful with what you execute since there's no undo.

Some helpful links regarding training your own LLM since I've been playing with:

https://github.com/geekylink/PicoGPT

Hacker News post: https://news.ycombinator.com/item?id=36832572

LLAMA: https://github.com/ggerganov/llama.cpp

Dead simple LLAMA: https://cocktailpeanut.github.io/dalai/#/

Rclone is a cool little CLI tool for Linux/WSL that allows you to backup, sync, and even mount various cloud server provider options on your desktop/server and protect your data.

For additional security, you can encrypt the files before they are uploaded to the cloud so even the folder & file names, and file types are encrypted. By doing this client-side encryption you can pretty safely assume your files are free for snooping.

Your password can be two passwords so you can access it from machine as well and recover your archive in case of your device failing.

Once you have a crypt volume setup you can then copy your files manually, sync a directory to the cloud, or even mount your cloud drive as a local directory for easy exploration.

sudo apt install rclone

Then run:

rclone config

Optional: You don't have to use your own API keys but you'll be sharing it with everyone else who uses rclone with the default API keys and they throttle the connections with usage. So it's best to setup your own oauth consent screen and credentials here:

https://console.cloud.google.com/apis/

If you want a detailed guide on configuring rclone for Google Drive check this guide:

https://www.maketecheasier.com/rclone-sync-multiple-cloud-storage-providers-linux/

After you have a cloud account connected and named, you can create a crypt volume on top of it:

https://www.maketecheasier.com/use-rclone-crypt-encrypt-files/

rclone github:

https://github.com/rclone/rclone

cross-posted from: https://programming.dev/post/266503

Yes, who haven't had a glass of red wine, relaxing music and some inline assembly....

So I set up a self-hosted lemmy instance to play around with but I'm a bit confused by how the federation system is supposed to work.

I followed these instructions to get setup:

https://join-lemmy.org/docs/administration/install_docker.html

I then found that I was having issues deploying the lemmy proxy as it could not find the nginx config. I was able to resolve that issue by adding the nginx internal config from the git to my instance like so:

wget https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/nginx_internal.conf

I noticed that I couldn't search for any instances from my personal instance, so in the "Allowed Instances" in the server settings on the web UI I added: lemmy.ml lemmy.world programming.dev and sopuli.xyz

I figured that adding some of the major instances should kick-start the federation process and allow it to find other things, but it seems it does not.

Now I've been able to subscribe to a couple communities from my instance, [email protected] and [email protected] and of course this Selfhosted community. However, I still cannot seem to add others, for example it still fails to find anything when I try to add [email protected]

Additionally, I can't seem to see comments from most other users on most of the posts that I do see for some reason. Even if those users are from one of those instances I've allowed, I still don't see them.

Does anybody have any idea why this might be? For example, I'm quite sure I'm not going to see any of the comments on this post even though I posted it, I'll probably have to come back and check on another account to reply and I really don't understand why and would like to find a fix.

Thanks.

"It's real, I was the gorilla." - AI

Install docs for docker:

https://join-lemmy.org/docs/administration/install_docker.html

Gits:

https://github.com/LemmyNet/lemmy

https://github.com/LemmyNet/lemmy-ui

Docs: https://join-lemmy.org/docs/introduction.html