frozen

joined 2 years ago
MODERATOR OF
[–] [email protected] 5 points 3 days ago (1 children)

Wait, I'm a millennial and also drank from a garden hose and came home when the streetlights turned on... What does that mean for me?

[–] [email protected] 11 points 2 weeks ago

As a T1 diabetic, artificial sweeteners don't affect my blood sugar either. Caffeine does, though, unfortunately.

[–] [email protected] 2 points 2 weeks ago

Use a steamer instead of a blow-dryer or heat gun, next time. I just had to defrost my Samsung freezer to fix a leak, no warping with the steamer.

[–] [email protected] 2 points 3 weeks ago (1 children)

I have a similar docker/podman alias, except I pull first. This greatly reduces downtime between down and up, which is nice for critical services.

[–] [email protected] 2 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

Right you are, I messed up the external host. Thanks!

[–] [email protected] 1 points 4 weeks ago (3 children)

Below is my current dockerfile, which is using 0.19.11 right now to fix the issue. The issue happens when I switch to 0.19.12.

networks:
  # communication to web and clients
  lemmyexternalproxy:
  lemmybridge:
  # communication between lemmy services
  lemmyinternal:
    driver: bridge
    internal: true

services:
  photon:
    image: ghcr.io/xyphyn/photon:latest
    networks:
      - lemmyexternalproxy
      - lemmyinternal
    ports:
      - 8080:3000
    environment:
      - PUBLIC_INSTANCE_URL=lemmy.frozeninferno.xyz
      - PUBLIC_LOCK_TO_INSTANCE=true
      - PUBLIC_DEFAULT_COMMENT_SORT=Top
      - PUBLIC_FULL_WIDTH_LAYOUT=true
      - PUBLIC_DEFAULT_FEED=Subscribed
    restart: unless-stopped
    depends_on:
      - lemmy
      - lemmy-ui

  proxy:
    image: nginx:1-alpine
    networks:
      - lemmyinternal
      - lemmyexternalproxy
    ports:
      # only ports facing any connection from outside
      - 8880:80
      - 8843:443
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf:ro
      # setup your certbot and letsencrypt config
      - ./certbot:/var/www/certbot
      - ./letsencrypt:/etc/letsencrypt/live
    restart: unless-stopped
    depends_on:
      - pictrs
      - lemmy-ui

  lemmy:
    image: dessalines/lemmy:0.19.11
    hostname: lemmy
    networks:
      - lemmyinternal``
      - lemmybridge
    ports:
      - 8536:8536
    restart: unless-stopped
    environment:
      - RUST_LOG="warn,lemmy_server=info,lemmy_api=info,lemmy_api_common=info,lemmy_api_crud=info,lemmy_apub=info,lemmy_db_schema=info,lemmy_db_views=info,lemmy_db_views_actor=info,lemmy_db_views_moderator=info,lemmy_routes=info,lemmy_utils=info,lemmy_websocket=info"
    volumes:
      - ./lemmy.hjson:/config/config.hjson
    depends_on:
      - postgres
      - pictrs

  lemmy-ui:
    image: dessalines/lemmy-ui:0.19.11
    networks:
      - lemmyinternal
      - lemmybridge
    ports:
      - 1234:1234
    environment:
      # this needs to match the hostname defined in the lemmy service
      - LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536
      # set the outside hostname here
      - LEMMY_UI_LEMMY_EXTERNAL_HOST=192.168.0.10:1236
      - LEMMY_UI_HOST=lemmy-ui:1234
      - LEMMY_HTTPS=true
    depends_on:
      - lemmy
    restart: unless-stopped

  pictrs:
    image: asonix/pictrs:0.5
    # this needs to match the pictrs url in lemmy.hjson
    hostname: pictrs
    # we can set options to pictrs like this, here we set max. image size and forced format for conversion
    # entrypoint: /sbin/tini -- /usr/local/bin/pict-rs -p /mnt -m 4 --image-format webp
    networks:
      - lemmyinternal
      - lemmybridge
    environment:
      - PICTRS__API_KEY=API_KEY
      - RUST_BACKTRACE=full
      - PICTRS__UPGRADE__CONCURRENCY=256
      - PICTRS__OLD_REPO__PATH=/mnt/sled-repo
      - PICTRS__REPO__TYPE=postgres
      - PICTRS__REPO__URL=postgres://lemmy:<censored>@postgres:5432/pictrs
    user: 991:991
    volumes:
      - ./pictrs:/mnt
    restart: unless-stopped

  postgres:
    image: postgres:16-alpine
    # this needs to match the database host in lemmy.hson
    hostname: postgres
    networks:
      - lemmyinternal
    environment:
      - POSTGRES_USER=lemmy
      - POSTGRES_PASSWORD=<censored>
      - POSTGRES_DB=lemmy
    volumes:
      - ./postgres:/var/lib/postgresql/data
    restart: unless-stopped
    shm_size: 12gb

  adminer:
    image: adminer
    restart: always
    networks:
      - lemmyinternal
      - lemmyexternalproxy
    ports:
      - 10000:8080
[–] [email protected] 1 points 1 month ago (5 children)

I'm using the regular Docker file, and I'm getting the same thing.

Lots of the following in the UI logs.

{ name: 'couldnt_find_person', message: '' }
{ name: 'couldnt_find_post', message: '' }
{
  name: 'unknown',
  message: 'Query deserialize error: invalid digit found in string'
}
{
  name: 'unknown',
  message: 'Query deserialize error: invalid digit found in string'
}
{ name: 'couldnt_find_post', message: '' }
{ name: 'couldnt_find_post', message: '' }

However, Photon's alternative UI works fine.

[–] [email protected] 3 points 1 month ago (1 children)

I think where you're messing up is making the assumption that the person will stick with "they" even after learning pronouns. Defaulting to they when a person doesn't know is just the smart, respectful play. As long as the person makes an honest effort to use the correct pronoun when corrected, that's all that can be asked.

[–] [email protected] 2 points 1 month ago

The only problem with Telegram = IRC angle is that I can't scroll up in IRC to see what I missed throughout the day. I legitimately would love to switch my friend group to a self-hosted IRC server, but chat history is important.

[–] [email protected] 8 points 1 month ago (3 children)

Unironically, yes. LLM generated text is chock-full of em-dashes for some reason. I still use regular dashes to separate clauses occasionally - like this - but not full em-dashes.

[–] [email protected] 4 points 1 month ago

This is an effort to kill anyone who isn't young and fit.

Or also chronically ill. I'm (relatively) young and very fit, but I'm also type 1 and require insulin to live. It's eugenics, plain and simple.

[–] [email protected] 1 points 2 months ago

The third and fourth books actually start to introduce some really wild lore and world-building. Shame it was wasted on such a terrible main plot.

 

My instance (frozeninferno.xyz) seems not to be federating properly with mander.xyz.

Looking at https://lemmy.frozeninferno.xyz/c/[email protected] it appears that the newest posts are from 4 months ago, however, looking at https://mander.xyz/c/herpetology there have been some more recent than that.

What can I do to fix this? And how can I check if federation is working properly with other instances?

Thanks.

 

I'm planning on building a workstation with the 7955WX, but I can't find it for sale anywhere except sketchy CPU resellers and eBay.

But I can buy a Lenovo ThinkStation P8 with one, and that honestly seems like the better deal after pricing out a custom build. I'd be bringing an AMD 6800 XT and an Nvidia 3070 Ti over, so no GPU required.

Thoughts or advice?

1
Maintenance complete! (lemmy.frozeninferno.xyz)
 

All of the primary Lemmy services have been updated as part of this maintenance.

PosgreSQL database: 15 -> 16
pict-rs image repository: 0.4 -> 0.5
Lemmy: 0.19.3 -> 0.19.5

Also, as part of the migration, the pict-rs image repository's backend has been migrated from its internal sled-repo database to the shared PostgreSQL database, which will simplify backup and recovery in the future.

Please report any issues on this post or a new post in [email protected].

Thanks for your patience as we work to improve your Lemmy experience.

 

We'll be taking the instance down for maintenance at 4PM UTC on Saturday 9 August. Use this to convert to your local time.

The instance will be upgraded to Lemmy 0.19.5, which requires upgrading several other services Lemmy relies on.

The maintenance window will be 5 hours

 

We ran into some unexpected issues upgrading the instance to the latest Lemmy version, and troubleshooting was starting to take too long and extend past the previously given maintenance window. As such, we decided to restore from backup and attempt the upgrade again another day, next time with a larger maintenance window.

Everything should be back as it was before the downtime. The next maintenance will be announced soon.

Thanks for your patience!

1
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

We'll be taking the instance down for maintenance at 2PM UTC on Saturday 29 June. Use this to convert to your local time.

The instance will be upgraded to Lemmy 0.19.5, which requires upgrading several other services Lemmy relies on.

The maintenance window will be 3 hours

 

I found MoonDeck while perusing the Decky plugin store and it's absolutely awesome. I've had Moonlight and Sunshine set up for a while because Steam streaming is very inconsistent between Deck and Linux, but I didn't use it often because it's a pain setting up launchers in Sunshine for each individual game. MoonDeck takes the hassle out of that completely, and I find myself streaming GPU-intensive games to my living room much more often nowadays.

I highly recommend it!

 

I was looking through various RCON tools and found this. Someone does not like commit messages.

 

Also, the location on the LinkedIn job listing was a city nearby, even though I'm over 300 miles from SF. Fuckin' dumb.

1
GBA core with RTC? (lemmy.frozeninferno.xyz)
 

I've searched around, but the only GBA core that seems to exist is spiritualized's, which doesn't have RTC support and hasn't had a release in over a year. I was actually under the impression that RTC support in cores wasn't possible, but then budude2 just released his GB/GBC core that does have RTC support. So now I'm wondering if it's possible for GBA.

I ask because I play a ton of Pokemon ROM hacks that take advantage of time changes, and it would be nice to have some of the core features of the Pocket. For example, sleep/wake doesn't work for Everdrives, and save states / memories are iffy.

1
Maintenance complete! (lemmy.frozeninferno.xyz)
 

The storage backend for the instance has been upgraded, which means the instance should be faster by quite a bit. It also enables a few new data resiliency features, which is pretty cool. Hopefully we don't need them, but better safe than sorry!

Please report any issues on this post or a new post in [email protected].

Thanks for your patience as we work to improve your Lemmy experience.

 

We'll be taking the instance down for maintenance at 6PM UTC on Friday, 22 Dec. Use this to convert to your local time.

This maintenance is due to a much-needed storage upgrade, which will hopefully speed up the instance quite a bit. The maintenance window will be 3 hours to account for full system backup and restore, but I'm hoping we'll be done quicker than that.

view more: next ›