Thanks friend!
Thanks friend!
Reminds me of the Fish Peppers I’ve grown the past 3 years! But definitely less hot/more versatile!
Give us some more info.
Pond size, depth, bottom composition, any weeds, typical size of bass, other fish present, forage base, etc.
“Pond” typically means small and shallow, and a foot of visibility, to me, means you’ll want something that makes some noise but is small.
Ned rig is quiet but good if the bottom is rocky and not much weeds and wood. If there’s submerged wood, try a small spinnerbait, small squarebills are a good bet as well.
When I just need a bite, I’ve also had good luck with the Berkley gulp minnows in like 2 inch size on a drop shot.
Of course there’s always live nightcrawlers and minnows under a float as well.
I feel like this one is one where they took an existing shirt and ran the instructions through an OCR program.
Like the goblins of Moria.
I guess that makes spez the balrog…or maybe the cave troll.
I would definitely consider that a serious potential issue, if for no other reason than so many communities will likely find a use for tags based on the nature of the community structure.
For example, I could see a ton of communities having tags for things like modposts, new member intros, meta topics, memes, questions, reviews, how-to’s/tutorials, guides, etc. and that’s just for broad post types that would apply to thousands of communities.
I think letting users manually make their own multi-lems, perhaps with the ability for communities to sort of team up to make uber-lems of closely related communities to help users discover more of them…but sub, unsub, multi, and un-multi as they see fit…is likely the best approach.
Maybe don’t take disagreement so personally?
I too would like to do this myself and not have AI or anyone else decide for me what content gets lumped together.
I predict that this is also an issue that will slowly resolve itself over time, as critical masses of users gradually coalesce around one community, or more…but only if the extras are distinct in some way…which would very specifically be made more difficult by the sort of programming you’re proposing.
I’m not saying there’s no merit in your suggestion, only that it may not be the one-size-fits-all solution that you seem to think it is
Exactly.
It’s analogous to the way that Reddit knowingly allowing some subs to exist repelled some users.
Most were able to get past it and simply not subscribe to subs they found objectionable, but I’m sure many people just stayed away once they learned that certain subs existed and were very much known about by Reddit admins.
One key difference here is the way that your instance is able to enforce rules and to some extent influence and filter your user experience, and that’s worth consideration too.
I’m also curious if and how an instance like lemmy.ml can, for example, delete comments, ban users, take down content in cases of cross-instance interaction. Could the admins of lemmy.ml, for example, ban a user from another instance from Lemmy completely? From their local communities? Could they remove that person’s comments? Can they prevent their own users from seeing content they don’t like on other instances? Can they moderate content from their users that is posted to communities on other instances?
Well said.
In that case, I think the reddit administration did a good job of excising the people it didn’t want, letting them take root elsewhere before the main mass went to check that place out, and letting that main mass come right back.
At the time, I thought it was a calculated and intelligent move on their part, fully intentional.
After what we’re seeing now, I think maybe they lucked out.
I guess it’s some sort of Hanlon’s Inverse Corollary: Never attribute to intelligence what can be adequately explained by dumb luck.
Ewwww! Gravid!
Someone posted this on Reddit?