[email protected] @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. 🌎
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?
In Best Korea, it is whatever day Dear Supreme Leader says it is. Reality is for westerners.
That’s because these anti immigrant views aren’t supported by data, or logic, or common sense. It’s not like Americans are lining up to do the jobs immigrants are taking. The US can’t function as a society today without those immigrants. But the right just wants to coddle its racist base with “brown man bad”.
I feel like the decentralization brings some downsides in the quantity of bad actors, extremist views, and the like.
The open platform certainly has an overwhelming advantage over Reddit in other ways, but there seems to be a higher number of trolls, shitheads, wackos, etc and in some cases entire instances dedicated to them.
While these people get banned on Reddit, Lemmy hasn’t yet solved this moderation issue; user accounts are basically disposable and moderation is super distributed, so it’s easy to abuse.
For the longest time I thought I hallucinated this movie in a fever dream or something. I must have seen it as a kid back in the nineties. But it makes so little sense that I guess I thought I imagined it lol. Watched it like a month back and uh, it might as well have been a fever dream hallucination lmfao
Okay, but I mean, 60 million versus 30 thousand. The former is effectively “infinite”, I mean how many hours would it take you to walk that far?
That’s better than I was thinking. But still, nothing beats “infinite”.
You should consider writing a long form post about your experience doing this. I’m sure I am not the only one interested in an account of living off the grid in this way.
Did they ever fix the game having a maximum map size of like 10.000 by 10.000? That limitation always seemed to put it at a disadvantage compared to Minecraft, for larger communities
The comparison certainly makes sense. Awesome, that means we’re just a few years shy of a world war.
It could well be as bad.
Yes you can run windows games fairly easily on Mac and Linux these days but it’s never quite as good as a native build.
There’s CrossOver on Mac which works pretty well for most titles too. Not as good as proton but let’s say 75% there. But you might be right that the success of proton is disincentivizing developers from targeting either. Still disappointing though as a game like this is an ideal candidate for Mac and Linux, compared to some AAA title.
Makes me sad to see it’s Windows only given it’s so graphically simple and low tech. Should be a shoe-in for a Mac and Linux version.
Edit: yes I know proton exists, my point is that as an indie game it is likely built with something like Unity or Godot, and thus exporting a native Mac and Linux build is just a matter of turning on a couple check boxes.
This community is moving to feddit.org/c/europa. This sub on Lemmyworld will be sunset in the coming weeks. Please update your subscriptions.
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.
...and we're back!
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!
How do you mention a user on Lemmy?
Is there an equivalent to doing /u/user in The Bad Place, to notify and summon someone?
Federation not currently working with non-Lemmy instances (kbin, mastodon, …)
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
My personal favourite: Port Old Fashioned
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
Welcome to /c/mixology, a community to share and discuss your favourite cocktail recipes. Unique and home-brewed cocktail recipes are especially welcome!
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.
Looking for a mobile experience for Lemmy? Try WefWef, a near-exact clone of Apollo for iOS
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!
Looking for forums on other Lemmies?
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]
E-mail now available
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.
Pro-tip: Self-hosting Lemmy? You can use object storage to back pict-rs (image hosting) to save a lot of money
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!
Pro-tip: Self-hosting Lemmy? You can use object storage to back pict-rs (image hosting) to save a lot of money
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!
Pro-tip: Self-hosting Lemmy? You can use object storage to back pict-rs (image hosting) to save a lot of money
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!
What does it mean when all your subscriptions on a single server (lemmy.world in this case) are stuck at “subscribe pending”?
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. 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.
Just wanted to say, awesome work and progress so far!
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!!
Jóias escondidas na província de Setúbal
Quais são seus lugares menos conhecidos favoritos em nossa província? Quaisquer cidades bonitas, praias isoladas, restaurantes familiares, etc, que você realmente goste?
Welcome to Lemmy @ Federate.cc!
Federate.cc is live with our first Fediverse service, Lemmy! While I'm the sole user on this instance for the moment, I hope to eventually attract a small community to join me here.
Copy/pasting from the main website:
> federate.cc is a collection of fediverse services operated on behalf of its members with limited commercial interest
> we are funded entirely through membership dues
> there is no advertising, data selling, or any such corporate baloney here
> we host instances of popular distributed, federated software platforms, providing a carefully-tended "home instance" / "homeserver" across several major platforms
> we intend for our services to be a home for upstanding netizens, interested in participating respectfully and in good faith across the fediverse
> in general, everyone is welcome, though we reserve the right to refuse membership to anyone suspected of prior misbehaviour across the fediverse
> we want to encourage quality over quantity and prefer a small, tight-knit community of active contributors; there is no aspiration to become a large public instance