Shadow

joined 2 years ago
MODERATOR OF
[–] Shadow@lemmy.ca 2 points 3 weeks ago (2 children)

Fish scales?

[–] Shadow@lemmy.ca 3 points 3 weeks ago (1 children)
[–] Shadow@lemmy.ca 3 points 4 weeks ago

Monthly. There were a couple yearly that I just normalized down to monthly.

[–] Shadow@lemmy.ca 6 points 4 weeks ago

Yes, shipped to a server at my house.

[–] Shadow@lemmy.ca 5 points 4 weeks ago

No we launched with stripe, but if you look at our site you'll see we don't push it heavily since we pay more fees there.

[–] Shadow@lemmy.ca 15 points 4 weeks ago

Good idea, they all do except interac since everything routes through stripe. It's absurd the amount of transaction data they get. Thanks!

[–] Shadow@lemmy.ca 19 points 4 weeks ago (6 children)

As requested, here's some additional info about donation methods / sizes / volume!

@GreyEyedGhost@lemmy.ca @pglpm@lemmy.ca

[–] Shadow@lemmy.ca 6 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

I like the idea of a specific fundraiser. ~~Our post 6 months ago is what drive the big spike visible on the graphs, so I was hoping for a similar boost this time.~~ If we don't get there naturally, I think that's a reasonable next step.

See below for your other question.

Edit: I was wrong, the big spike was Smorks transferring our old donations over. I forgot about that!

[–] Shadow@lemmy.ca 9 points 4 weeks ago

I have no problem sharing anonymized info for things like this, it's just difficult to pull.

We accept donations a few different ways, they can be one time or recurring, we don't know who people are , and we often get paid weeks after they happen once it gets reconciled by stripe.

Let me see what I can do.

Re: Lem.ee that's kinda a different problem. They weren't financial issues afaik, but admin burnout. I don't think that's a concern on our side at this time.

[–] Shadow@lemmy.ca 12 points 4 weeks ago (1 children)

Two hosts would cost more in colo fees and we don't need the resources. The redundancy would be nice, but this is enterprise grade hardware covered under Dell prosupport. I also have an identical box running my home systems, so I could steal parts temporarily if we had an issue.

Yeah the ram is just what the hosts came with. It's way more than we need and so everything is very over provisioned.

[–] Shadow@lemmy.ca 4 points 1 month ago (1 children)

Willing to email me your file so I can try? Shadow@lemmy.ca

 

Sorry for the downtime! Unfortunately our secondary firewall took over for some reason, and haproxy failed to properly come up.

I'll be scheduling a maintenance window in the next few days to do some further digging, so I can make sure this is fully resolved.

42
We Are Canadian (www.youtube.com)
 

With some hacking at the database and APIs, I've put together a python script that allows backfilling of posts. I've now pulled in the most recent 50 posts of anyone that one of our users is following.

You may now bask in cats. https://pixelfed.ca/i/web/profile/797991200484212751

Hopefully that'll help it feel a little less empty!

 

Sorry about the brief downtime there!

Wasn't related to the new users or high load, but was a combination of two problems:

  1. Our fw02 took over for some reason TBD
  2. Opnsense isn't keeping haproxy configs in sync and fw02 had a broken config

Still digging into the root cause, but shouldn't be any more issues =)

 

Just a heads up that we're now running on lemmy 0.19.9.

Change log here - https://lemmy.ca/post/38913840

 

Sorry about the ~20 minutes of downtime there!

I was working on migrating the lemmy.ca domain out of a personal cloudflare account, into a shared one for Fedecan. Missed one little setting that took me far too long to track down!

 

Unfortunately the pictrs database migration yesterday seems to have skipped migrating a ton of data.

Since cloudflare is caching our images, almost nobody noticed. We've now been running on the new instance for over a day, collecting new images into a new incomplete db. Fun.

I now have two copies of pictrs running, one with the postgres db and one with the legacy sled-db. Requests that fail against our updated one, will be retried against the legacy one. This should result in all images working properly again for now, while I figure out a better long term solution.

Please let me know if you still see any issues with images loading!

view more: ‹ prev next ›