The main Fediverse community for Europe is located at [email protected] - 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.

Sup lemmings!

As you probably noticed, this instance was dead for the majority of last week. Sorry about that. An update to the latest version using the official method was less than successful, and the documentation less than informative.

At any rate, the site is back up now, though I’d expect slowdowns over the next day or so as all that backlog from the fediverse filters in.

Sorry about that!

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

Currently 👀 an upstream issue that’s preventing non-Lemmy instances from federating with us; this is preventing interacting with Kbin among other things. Hoping this will get merged in soon, otherwise I’ll probably have to monkey-patch our instance to get this working. Kbin has a large user base and so the ability for us to subscribe and participate in their communities (“magazines” in their parlance) is important to me.

https://github.com/LemmyNet/lemmy/issues/3354

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/[email protected]

It’s a free progressive web app; visit https://wefwef.app in Safari, go to the action/share sheet and click Add To Home Screen. You’ll find it’s a near carbon copy of Apollo was on iOS. To use it with your account here, just go to Login and where it asks you which server, scroll down to select Other and use “lemmy.federate.cc” as the server. Voila!

E porque é a Manteigaria?

Don’t forget to browse by “Subscribed” or “All” instead of “Local”. If you want to search for or subscribe to a remote community, you can search either for the full URL of the remote community inside our search box, or search with the syntax [email protected]

I've set up email at the federate.cc domain today, backed by Migadu, a lightweight privacy-focused email service out of Switzerland.

If any members would like an e-mail at this domain, either send me an email (sparky@), or DM me here on Lemmy. They're not created automatically by default, as I have to manually go do something adminny to make them happen.

But upon request, an email @federate.cc is open to anyone who wants one.

Some caveats:

• This isn't Gmail, we're poor. Assume you have something like 500mb-1gb of storage in your account. Not a good place for large attachments, etc.
• You're subject to the same code of conduct as our instances, e.g., if you start sending spam or harassment, you'll get shut down.

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!