GeekyLink

Aww yeah

There was a fan and the fan decided it wanted to make loud noises and become unbearable and thus gekinzuku was moved again.

If you're having problems connecting to Discord on Desktop today, try your phone and/or phone data. If that doesn't work, connecting over VPN seems to solve the issue for now:

https://news.ycombinator.com/item?id=37701476

You also may be able to use the website version for today.

EDIT: Changing your DNS may also resolve the issue.

You are not actually blocked; it seems to be affecting a lot of people at the moment.

"empty/corrupt snapshot file" is a solvable issue. Look into pict-rs's storage in the sled directories. there should be some files that have .snap at the end. if any of these are zero-sized, delete them. if none of them are zero-sized, delete the most recently created one. then restart pict-rs

https://github.com/LemmyNet/lemmy/issues/2653

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.

It's been done, memes from this time forth shall take less space.

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/#/

Sorry for any lost memes

Now you can self-host a minecraft server in a docker container wherever. Just set the forge URL in settings.json build the docker and run:

https://github.com/geekylink/minecraft-forge-docker

All the communities now have banners.