Western utah after driving through a storm two weeks ago.
A couple years ago, my buddy and I had just finished enough of his SAS project on the hundie that we needed a test drive. This trail is relatively close and has some great views. We managed to rope our other friend (who owns the orange FJC) into it as well.
Nothing failed and all the welds stayed welded, so that was nice.
This was shot with a full moon behind me. I was happy to get the unique moonlit landscape with some faint milky way at the same time.
The clutch basically gave up yesterday. Gonna miss driving this for a few days while it gets repaired.
Long term, I agree -- the whole point of the fediverse is to distribute the user base, moderation capacity, etc. Initially though, we're just trying to make it as easy as possible to for folks to discover lemmy and use it.
Sending them on a wild goose chase to find an instance and sign up complicates that. Getting them to come back the next day is also way harder when that experience sucks.
If folks can sign up on your instance and use it as their gateway to the lemmy fediverse, its tremendously helpful for distributing load.
The challenge is, letting people know your instance exists, and when they finally do and you get 30 signups per hour, scaling your instance to keep up.
Long term, you also have to deal with all the sysadmin crap (scaling up/down based on load, security and updates, backups, assholes that DDOS your instance because they don't like your moderation decisions, copyright take downs, legal requests, etc).
Hard to say -- so far on lemmy.ml, when the backend is overload, I can get pages to load (presumably from cache) but actions I take to change things (sign in, post comments or content, etc) result in an eternal "spinny wheel".
Yeah - its tricky. What I'm seeing though is instead of communicating that need at all, lemmy.ml and potentially other instance owners are just trying to push new users to smaller instances.
I am running my own mastodon instance in my basement - I've got other personal projects running in AWS, and work professionally in Azure. It sounds like you've got some great cloud experience as well. There seem to be lots of other similarly skilled folks here that can assist with deployment and scale automation (if that's what they need), or others that could assist by just signing up for $5/month on patreon to cover server costs. That call to action needs to happen though or else people wont do anything.
I’ve been uploading jpegs at 2048x1365. Lemmy.ml has been up and down throughout the night so you might just get a spinny circle sometimes when you post.
Imgur works too but lemmy can’t seem to deal with imgur thumbnails.
Me and a buddy are trying to find some good photography locations for the Oct. eclipse in the United States. Was able to get some decent shots out in western Utah.
I created this community as a landing zone for reddit offroad refugees. I've only got so many trip reports and Jeep/Land Cruiser photos though. If you're new, please help us flood this new community with photos of your rig and trips.
Taken from Tibble Fork Reservoir.
A pinned post like "Welcome to Lemmy!" on Lemmy.ml and other instances with that link would help I think. Also, I think it would be a more streamlined experience (and less disorienting) if the "Join" links on that page went directly to the instance's signup page instead of the local instance feed.
I agree -- the FOMO thing is real.
However having a clear path to follow would really help capture/retain those users. In other words "Wow, Lemmy is so popular it can't handle the traffic -- here's an up-to-date list of instances to try anyway", or some other option.
Possibly a pinned post where instance owners can comment info on their own instances without having to wait for someone to update a master list?
Mastodon during the twitter migration had a problem where folks were standing up instances, but new users were having trouble finding them, or overwhelmed with lots of "interest-based" instances. Most users don't care about a "furry" specific instance, or an instance focused on San Francisco Donut enthusiasts. They just want an instance.
Another problem is as time went on, some of those instances shut down abruptly and wiped out accounts for folks. Having a few centralized and supported instances at first will help solve that problem as well.
I have the technical know how, given a "GettingStarted.md" file to read to stand up an instance, but I'd rather put my time/energy into supporting an existing one. Dealing with the horde of people currently joining and about to join will require some coordination.
Haha wow. What an effective way to describe it.