This made me laugh so hard, I spit my drink all over my desk. Well played, sir.
They didn’t even name the country in the headline? What is this? Does NY Times think its readers have never heard of Moldova?
The economic situation is so complicated there that you probably need to sit through a 60 minute documentary to get an answer to this question, or really understand much about their crisis at all.
It’s very difficult to say whether or not the cure is worse then the disease; they were fucked to start, and the austerity measures weren’t the origin of the unemployment and poverty, but they did exacerbate them. But, they also lower the inflation rate, which itself was the largest cause of hardship, especially poverty.
Is the increase in suffering due to austerity worth the decrease in suffering due to cooling inflation? That’s the real question but I’m not sure anyone knows objectively, yet.
Anecdotally, as someone who spends 3-4 months a year in Buenos Aires: things seem to be getting worse; but they’ve been worsening for a decade, and the rate at which they are getting worse seems to be decreasing. So I guess a sort of Pyrrhic victory..?
It’s not that easy to “just move” for most people, particularly if they’re not working in a professional field where they can get relocation with a new job, or save up enough funds to move. I say this as an American who moved to Europe, by the way.
I looked out of curiosity, they’re actually not doing well, revenue shrinking quarterly. Seems like other players are eating their lunch. Makes sense really, 10-15 years ago Dropbox was innovative but now? There’s like 25 other cloud drive providers. Dropbox isn’t really offering anything unique now, they’re just a commodity, and they can’t meet the package deal pricing of competitors (like Google drive being included with Google Apps, or iCloud Drive being included with Apple One).
That’s cool, any details or link to share?
Not arguing with you, but I think Gaza is even worse.
What’s happening in Ukraine is terrible - but it’s a war between two countries, that each have an army.
What’s happening in Gaza is something else. It’s a country sending an army on a civilian population. Palestine has no army to defend itself.
And if, for the sake of argument, you accept Israel’s claim that it owns the Palestinian Territories, then it means Israel is turning its army against its own land and its own citizens.
AI may be a useless meme but evidently it’s also a forcing function for reasonable RAM minimums.
To put that into perspective, the World Bank estimates global GDP as around $100 trillion, which is peanuts compared to the prospective fine. Google would therefore have to find more money than exists on Earth to pay Moscow.
Seems a bit suspect.
This is what I keep thinking. If we drew a Venn diagram of hardcore republicans and EV buyers, they would be two distant, non-intersecting circles.
Gravity is tired of humans saying it causes things to fall down.
More than that, they supposedly punish multiple generations of the family in labor camps. You can Google something like North Korea 3 generations to see the details.
Ich bin selber Mitglied dieser Gruppe, und hab den Eindruck, dass viele Millenials/GenZ‘ers diese Frage teilen.
Doesn’t trump fall under this tough? He swore to uphold the constitution in his oath of office at Inauguration day.
Console manufacturers will have to adapt and liberalize self-publishing to stay relevant. AAA gaming continues to enshittify, and indie games / smaller studios are the ones releasing the good titles.
Valve knows this, and the ease for developers to release on Steam means they’re well positioned to ride out the transition. By comparison, releasing on console means signing license agreements, getting access to proprietary SDKs, submitting your game through an approval process, getting each update reviewed, etc etc. The barriers make releasing on console very unappealing for smaller developers.
So IMO if the consoles want to ride out the decline of AAA games, they will need to reinvent their image and how they interact with smaller studios and indies.
Mr Netanyahu, please stop dropping bombs on Gaza, ok? Anyway, here are some more bombs. All the bombs you want in fact, at our expense!
The fall from grace was both spectacular and stunning. I’ve never seen someone trash so much goodwill and in such a short time.
This isn’t an actual accession to the EU though is it? Rather just Moldova altering its constitution to reflect an eventual desire to join?
Is there an equivalent to doing /u/user in The Bad Place, to notify and summon someone?
Do you like old fashioneds, and wine? This is the drink for you! I can't remember now where I got the idea, but I've been making them forever.
----
2-3 shots Bourbon whiskey (personal favourite: Jefferson's Reserve, the gentle alcohol notes but strong wood flavours blend gracefully into the wine notes!)
1 - 1.5 shots' worth of tawny port (don't need anything too good here but a basic 10 year Graham's or similar will do)
1 teaspoon simple syrup (take it easy on this since the Port itself will impart sweetness!)
1 big ass ice cube
1 maraschino cherry
I'm a fan of custom and unique twists on cocktails; and if you're reading this, hopefully you are too! Let's move beyond the typical basic stuff and discuss more interesting recipes that have a special place in your heart, particularly if you've concocted them yourself, or put a twist on them.
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!
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!
sparky@lemmy.federate.cc @lemmy.federate.cc Lead administrator of federate.cc and its services. Please don't DM me for support with federate.cc, make a post in /c/meta instead.
Originally from Fort Lauderdale 🇺🇸, lived many years in Vienna 🇦🇹, now living in Setúbal 🇵🇹. Software engineer specialized in Apple platforms. 🌎