sparky

joined 2 years ago
MODERATOR OF
[–] sparky@lemmy.federate.cc 1 points 1 day ago

Lol. Yes, but also, even with the typo it wasn’t that wrong

[–] sparky@lemmy.federate.cc 38 points 2 days ago* (last edited 2 days ago)

Hi, I’d like to buy a plane ticket to San Fr-

PENIS OR VAGINA?

[–] sparky@lemmy.federate.cc 6 points 2 days ago* (last edited 1 day ago) (2 children)

The more I see .ml users’ comments, the more I understand why they keep getting ~~degenerated~~ defederated.

[–] sparky@lemmy.federate.cc 6 points 2 days ago (1 children)

Also worked in SV from 2011-2023. The shift is absolutely crazy. For basically my whole career there, you could waltz your way into an interview and offer anywhere you felt like - complete employee’s market. It’s hard to wrap your head around there being no jobs anymore. LLMs are cancer.

[–] sparky@lemmy.federate.cc 6 points 3 days ago

Seconding Kagi, it’s worth every penny.

[–] sparky@lemmy.federate.cc 10 points 3 days ago (1 children)

It’s a currency swap. Basically, we give them dollars and they give us pesos. Eventually, they could theoretically be swapped back.

Holding dollars is good for them because it shows foreign investors’ confidence in their economy, and allows them to shore up the peso if necessary by using dollars to prop it up through central bank buybacks.

Holding pesos is a high risk for us because the inflation rate has historically been extremely high. $1 US was like 300 pesos five years ago, and it’s more like 1500 today. So if we swap them back down the road, we will probably lose money, since we swapped dollars at $1 = 1500 pesos, but may swap back later at $1 = 2000+ pesos.

In a way it’s like we gave them an interest free loan. Or actually: more like we gave them a loan with a negative interest rate. Because we likely lose money the longer they hold it.

Why would we do this? Because Milei says lots of nice things about the orange man on TV.

[–] sparky@lemmy.federate.cc 4 points 4 days ago

Yes, on the one hand, this is a chilling precedent that can only lead to long term despair and national ruination. But on the other hand, line go up next quarter. I think we all know which one Tim Apple will choose.

[–] sparky@lemmy.federate.cc 5 points 4 days ago

Because Milei is also an embattled right wing nut job who frequently says nice things about orange man on TV.

[–] sparky@lemmy.federate.cc 1 points 1 week ago* (last edited 1 week ago)

Hi friend! I’m an American living in Portugal. Sorry about our bastard of a president. The wines here Portugal are fantastic, I can’t recommend them enough!

Since I’m a wine enthusiast from the states, here are some similar appellations that might satisfy your cravings, due to similar production styles and palates!

Napa and Sonoma Valley, CA … Alentejo

Willamette Valley, OR … Douro

Columbia Valley, WA … Dão, Tras-os-Montes

[–] sparky@lemmy.federate.cc 9 points 2 weeks ago (3 children)

How much time have you got?

[–] sparky@lemmy.federate.cc 13 points 2 weeks ago (3 children)

The roll of paper is an interesting idea but where would one actually buy those? Are they a standard thing?

[–] sparky@lemmy.federate.cc 15 points 2 weeks ago

It’s unclear if MS is even winning considering they’re trying to hike the price 50%, and considering that Xbox sales are flat.

232
ich_iel (lemmy.federate.cc)
 
 
 
 
 
 

Apparently this is the name of a construction/engineering firm here in Lisbon Portugal. Amusing coincidence

 

The main Fediverse community for Europe is located at !europe@feddit.org - please don’t submit many new posts to this sub on Lemmyworld. We are considering the board to be sunset and in a transition period for the next few weeks, after which it will be locked for new posts. Thanks.

 

Is there an equivalent to doing /u/user in The Bad Place, to notify and summon someone?

 

Just thought I'd share this since it's working for me at my home instance of federate.cc, even though it's not documented in the Lemmy hosting guide.

The image server used by Lemmy, pict-rs, recently added support for object storage like Amazon S3, instead of serving images directly off the disk. This is potentially interesting to you because object storage is orders of magnitude cheaper than disk storage with a VM.

By way of example, I'm hosting my setup on Vultr, but this applies to say Digital Ocean or AWS as well. Going from a 50GB to a 100GB VM instance on Vultr will take you from $12 to $24/month. Up to 180GB, $48/month. Of course these include CPU and RAM step-ups too, but I'm focusing only on disk space for now.

Vultr's object storage by comparison is $5/month for 1TB of storage and includes a separate 1TB of bandwidth that doesn't count against your main VM, plus this content is served off of Vultr's CDN instead of your instance, meaning even less CPU load for you.

This is pretty easy to do. What we'll be doing is diverging slightly from the official Lemmy ansible setup to add some different environment variables to pict-rs.

After step 5, before running the ansible playbook, we're going to modify the ansible template slightly:

cd templates/

cp docker-compose.yml docker-compose.yml.original

Now we're going to edit the docker-compose.yml with your favourite text editor, personally I like micro but vim, emacs, nano or whatever will do..

favourite-editor docker-compose.yml

Down around line 67 begins the section for pictrs, you'll notice under the environment section there are a bunch of things that the Lemmy guys predefined. We're going to add some here to take advantage of the new support for object storage in pict-rs 0.4+:

At the bottom of the environment section we'll add these new vars:

  - PICTRS__STORE__TYPE=object_storage
  - PICTRS__STORE__ENDPOINT=Your Object Store Endpoint
  - PICTRS__STORE__BUCKET_NAME=Your Bucket Name
  - PICTRS__STORE__REGION=Your Bucket Region
  - PICTRS__STORE__USE_PATH_STYLE=false
  - PICTRS__STORE__ACCESS_KEY=Your Access Key
  - PICTRS__STORE__SECRET_KEY=Your Secret Key

So your whole pictrs section looks something like this: https://pastebin.com/X1dP1jew

The actual bucket name, region, access key and secret key will come from your provider. If you're using Vultr like me then they are under the details after you've created your object store, under Overview -> S3 Credentials. On Vultr your endpoint will be something like sjc1.vultrobjects.com, and your region is the domain prefix, so in this case sjc1.

Now you can install as usual. If you have an existing instance already deployed, there is an additional migration command you have to run to move your on-disk images into the object storage.

You're now good to go and things should pretty much behave like before, except pict-rs will be saving images to your designated cloud/object store, and when serving images it will instead redirect clients to pull directly from the object store, saving you a lot of storage, cpu use and bandwidth, and therefore money.

Hope this helps someone, I am not an expert in either Lemmy administration nor Linux sysadmin stuff, but I can say I've done this on my own instance at federate.cc and so far I can't see any ill effects.

Happy Lemmy-ing!

 

Just thought I'd share this since it's working for me at my home instance of federate.cc, even though it's not documented in the Lemmy hosting guide.

The image server used by Lemmy, pict-rs, recently added support for object storage like Amazon S3, instead of serving images directly off the disk. This is potentially interesting to you because object storage is orders of magnitude cheaper than disk storage with a VM.

By way of example, I'm hosting my setup on Vultr, but this applies to say Digital Ocean or AWS as well. Going from a 50GB to a 100GB VM instance on Vultr will take you from $12 to $24/month. Up to 180GB, $48/month. Of course these include CPU and RAM step-ups too, but I'm focusing only on disk space for now.

Vultr's object storage by comparison is $5/month for 1TB of storage and includes a separate 1TB of bandwidth that doesn't count against your main VM, plus this content is served off of Vultr's CDN instead of your instance, meaning even less CPU load for you.

This is pretty easy to do. What we'll be doing is diverging slightly from the official Lemmy ansible setup to add some different environment variables to pict-rs.

After step 5, before running the ansible playbook, we're going to modify the ansible template slightly:

cd templates/

cp docker-compose.yml docker-compose.yml.original

Now we're going to edit the docker-compose.yml with your favourite text editor, personally I like micro but vim, emacs, nano or whatever will do..

favourite-editor docker-compose.yml

Down around line 67 begins the section for pictrs, you'll notice under the environment section there are a bunch of things that the Lemmy guys predefined. We're going to add some here to take advantage of the new support for object storage in pict-rs 0.4+:

At the bottom of the environment section we'll add these new vars:

  - PICTRS__STORE__TYPE=object_storage
  - PICTRS__STORE__ENDPOINT=Your Object Store Endpoint
  - PICTRS__STORE__BUCKET_NAME=Your Bucket Name
  - PICTRS__STORE__REGION=Your Bucket Region
  - PICTRS__STORE__USE_PATH_STYLE=false
  - PICTRS__STORE__ACCESS_KEY=Your Access Key
  - PICTRS__STORE__SECRET_KEY=Your Secret Key

So your whole pictrs section looks something like this: https://pastebin.com/X1dP1jew

The actual bucket name, region, access key and secret key will come from your provider. If you're using Vultr like me then they are under the details after you've created your object store, under Overview -> S3 Credentials. On Vultr your endpoint will be something like sjc1.vultrobjects.com, and your region is the domain prefix, so in this case sjc1.

Now you can install as usual. If you have an existing instance already deployed, there is an additional migration command you have to run to move your on-disk images into the object storage.

You're now good to go and things should pretty much behave like before, except pict-rs will be saving images to your designated cloud/object store, and when serving images it will instead redirect clients to pull directly from the object store, saving you a lot of storage, cpu use and bandwidth, and therefore money.

Hope this helps someone, I am not an expert in either Lemmy administration nor Linux sysadmin stuff, but I can say I've done this on my own instance at federate.cc and so far I can't see any ill effects.

Happy Lemmy-ing!

view more: next ›