Nice! I am glad I'm not the only person trying this strategy. I do need to admit I am completely unfamiliar with the wold of gemstones. Do you just go out and look for the initial stones?
(Btw I think you have a typo in your link? https://lemmy.world/c/faceting )
It's the kind of thing where it's not fun or just scary at the time. But it makes for a great story so it's worth it in the long run.
I think it would be good to have a separate summer vs winter community.
Possibly, I don't really know. My other thought is that the back country skiing subreddit was always kinda small and with the smaller number of people on Lemmy, its probably even smaller.
Its hard to get communities going initially so if broadening the topic helps, I'm for it.
Which sub were you thinking about specifically out of curiosity?
I created it to replace the /r/backcountry subreddit which was also skiing and snowborading. Perhaps it makes sense to broaden the scope a bit since the lemmy community is small. I could reasonably moderate hiking and camping stuff as well.
I will make a post over there asking people what they are interested in.
edit:https://lemmy.world/post/135425
Interesting, this one looked a lot more bald in person. Its a pretty zoomed in cell phone photo so I think the low contrast hides the feather/no feather line. Still, I was impressed my phone could capture it at all given the distance and lighting.
Its somewhat related, yes. Each time you do something in the web browser like upvote, that gets sent to your instance (e.g. lemmy.world). Then, the instance needs to update the other instances with that action (this is called publishing the action). Meanwhile, it needs to accept actions from other instances (these are actions that the server is subscribed to). All of these actions take server time and network so there is a queue of actions (think of this as each action standing in line waiting for its turn with the network/cpu).
You can optimize this a lot because each time you open a network connection and send something, there is some cpu and network cost above and beyond the action itself. So there are smart ways to group things together. But, the challenge is that such grouping adds delays (e.g. it may take longer for a moderator's removal of an offending comment to propagate to your server).
I created a community based on one of my hobbies to end my lurking habit: https://lemmy.world/c/backcountry
For now, I am just posting about one photo a day from my collection with some text that tries to drive interaction. There are 15 people in the community so I am hoping things start expanding at some point. All it costs me is a few minutes a day to choose and post a photo.
They are actively working on improving the performance. Large distributed systems aren't the easiest thing to build and scale. E.g. here is where they are working on improving the compute time required to handle upvoting:
Back in my day, our comments deleted themselves when the IRC or email server failed...
Come to think of it, what happens if an instance fails with Lemmy and there isn't a backup?
It was taken with a Sony alpha mirrorless camera. 1/1600 shutter speed, f11, iso5000. I have taken some cell phone photos too, but they don't seem to do quite as well with fast stuff like bird wings.
Ah that would make sense that they need to be mined. Still, that is a cool hobby I have never heard of before! You should make a post explaining the full process. Perhaps I will make a post explaining back country skiing as well for those who have never heard of it.
(edit: subscribed! You got me interested)