I mean, can you elaborate, or at least link something?
I think this is a little different as (Greek) Cyprus joined after the island had already been divided, the conflict already frozen. Versus if an EU member is attacked anew, the collective defence article would be triggered. Still, it’s unfortunate that Cyprus still remains divided.
I dunno. It may have been on the table at one point had they continued to work towards improving infrastructure and combating corruption. But once Erdogan turned autocrat, that door was closed.
Peter Magyar is an incredible name for a Hungarian politician, it would basically be like having the name John America lol
Wait what? So you can’t ever take a full day or days off?
The problem is that the only way to train an AI model is on real images, so the model can’t exist without crimes and suffering having been committed.
What the fuck
Okay, if it makes you feel better, we can call it premeditated mass-murder instead.
This is good news, but if I understand the article correctly, it sounds like the EU is not actually passing along the seized assets, but the interest generated on it - so e.g. a few billion per year in dividends and whatnot, as opposed to the underlying hundreds of billions they seized from Russia.
I’m a iOS developer just lurking here but, are paid features in custom ROMs common? Since they’re all downstream of AOSP, wouldn’t it be possible to bypass anything like that fairly easily by just commenting out the paywalls and building the ROM yourself?
🎶 Yo ho, yo ho, a pirate’s life for me. We pillage, we plunder, we rifle and loot. Drink up me ‘earties, yo ho. We kidnap and ravage and don’t give a hoot. Drink up me ‘earties, yo ho. 🎶
Haha fair point. “M&Ms Macaroni? Ain’t he the pursident of England?”
Why would anyone have thought otherwise? What are the odds that a world leader of a global power would meet with a regional official from one of the smallest and least politically relevant states in America?
The timing combined with her weird sociopathic nature make it all but a certainty that her decision to have kids was entirely driven by the possibility of a reduced sentence.
Referring to Apartheid, or what?
Isn’t it obvious, Joe?
“While I condemn Hamas, and supported Israel’s right to defend itself in the aftermath of the attacks, the use of force in reprisal has become excessive - beyond what is justified or acceptable. So effective immediately, I’m halting all arms shipments to Israel, and calling on President Netanyahu to withdraw IDF troops from Gaza and the West Bank.”
Problem solved.
R&D is cheap when you steal it from western companies!
It’s actually Argentina and Chile, which tips that calculus in our favour given they’re friendly western developed nations.
https://worldpopulationreview.com/country-rankings/lithium-reserves-by-country
Definitely wise to pick an EU member state to escape the law. This guy has probably never heard of extradition.
lol yea, even in Russia the headlines are always “person falls mysteriously out of window” and not “Putin stabs opponent in face with knife, lets out evil laugh”
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!
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. 🌎