sparky
Now
•
72%
My dude, you’re posting on a social comments platform. If you don’t want other people to comment, then why post here?
sparky
Now
•
100%
That’s not accurate at all! The real Gina would be eating spiders with her lizard tongue.
sparky
Now
•
61%
Not that I in any way support Israel’s campaign of violence, but I’m not sure these kinds of posts from and questionable news sources are doing anyone any favors. For those of us who already oppose the Israeli campaign, there’s nothing new here. For those who do, these kinds of sensationalist posts just push them farther back into their views.
The best case scenario is to open peoples’ eyes to the harm Israel is doing and convince them to change their opinion, which a more neutral has a better chance of doing.
sparky
Now
•
100%
It does go on sale from time to time. I picked it up on Xbox last year for 60% off if I recall correctly.
sparky
Now
•
66%
Pretty sure this is the same as every other messaging app - metadata is never protected information. The contents of the messages may be encrypted to some extent (which on Telegram they are, not end-to-end as with iMessage, but they’re not plain text), however your IP address, username, etc are subject to subpoena on any messaging platform.
sparky
Now
•
100%
Mozart actually was Austrian :-), this joke is usually told with Beethoven, who was born German but spent most of his life in Vienna.
sparky
Now
•
87%
Nope, you can buy an external one or something as an accessory but it’s another hundred bucks.
sparky
Now
•
100%
Thanks, Doc! Very useful context.
sparky
Now
•
100%
Surprising, however they announced existing owners can upgrade for $10, so perhaps the move is to raise the price for new buyers to make it equivalent to buying the full price remaster, while making it cheap to existing owners.
sparky
Now
•
100%
Came here to say the same thing, like WTF, why would you need a jar of 500
sparky
Now
•
100%
More of this please! We should be able to travel across the whole continent in electric high speed and/or night trains. I want to be able to get from Lisbon to Helsinki, from Athens to London, comfortably, without ever having to take a flight.
sparky
Now
•
94%
I love how on Lemmy you can be pretty sure this reference needs no explanation. We’re all nerds and I love it.
sparky
Now
•
100%
That was quite a trip. What a strange guy.
sparky
Now
•
100%
Yup. Piracy is bad so make sure to avoid that. Specifically, do not search for “Yuzu 1734” and combine it with “Firmware 18.1” and “Prod keys 18.1”, because if you did that you would be all set to pirate switch games. So to repeat, definitely don’t search for these things. Now you know what to avoid.
sparky
Now
•
100%
Why do all the Polynesian countries support Israel so strongly?
sparky
Now
•
100%
Huh, TIL. Are any of its competitors like the Legion Go or ROG Ally available?
sparky
Now
•
100%
The article uses the phrase “key outdoor areas” so I would assume this means you can’t smoke in a crowded plaza but you can still do so on your own balcony or whatever.
sparky
Now
•
100%
I think we really need some kind of automation tax, whether or not it’s specifically this take. But between robotics and AI, the only sustainable solution is taxing these kinds of things to fund UBI or some similar payments scheme for the displaced workers. Otherwise, we’ll end up with a few wealthy capitalists and mass unemployment. So it sure sounds to me like they need to choose between the tax option, and a significantly more dangerous option.
sparky
Now
•
100%
What is it with all these celebrities and powerful people committing sexual assault? It’s not that hard to find a consensual partner as a random ordinary guy, so how the fuck can you not find one as a rich and famous celebrity?
sparky
Now
•
80%
As a taxpayer I would be happy to contribute to getting him a one way ticket off the planet.
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?
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.
[/c/mixology@lemmy.federate.cc](/c/mixology@lemmy.federate.cc)
E porque é [a Manteigaria](https://maps.app.goo.gl/4EkfrouAhik6GRAc7?g_st=ic)?
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](https://github.com/LemmyNet/lemmy-ansible) 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+](https://git.asonix.dog/asonix/pict-rs/#user-content-filesystem-to-object-storage-migration): 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.](https://git.asonix.dog/asonix/pict-rs/#filesystem-to-object-storage-migration)** 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](https://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](https://github.com/LemmyNet/lemmy-ansible) 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+](https://git.asonix.dog/asonix/pict-rs/#user-content-filesystem-to-object-storage-migration): 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.](https://git.asonix.dog/asonix/pict-rs/#filesystem-to-object-storage-migration)** 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](https://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](https://github.com/LemmyNet/lemmy-ansible) 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+](https://git.asonix.dog/asonix/pict-rs/#user-content-filesystem-to-object-storage-migration): 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.](https://git.asonix.dog/asonix/pict-rs/#filesystem-to-object-storage-migration)** 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](https://federate.cc) and so far I can't see any ill effects. Happy Lemmy-ing!
Not sure if this is truly an issue with lemmy.world or just a general question about Lemmy, or maybe even my own instance, but this seems a fair place to start. [On my home instance, for some reason all subscriptions to @lemmy.world communities are perpetually stuck as “Subscribe Pending”, and I notice that not all of the posts and content have shown up.](https://lemmy.federate.cc/communities?listingType=All&page=1) Is this something that should “eventually” resolve itself, or is there some action I should take on my end as the instance administrator? Thanks/apologies in advance.
Absolutely loving the app so far, and I'm impressed by the rollout speed, seems like every time I launch it, there's a new build with more feature completion. Keep up the amazing work!!
Now
sparky@lemmy.federate.cc
sparky@ lemmy.federate.ccLead 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. 🌎