This really isn't the place for general Lemmy feature requests. The admin team here is very small and doesn't really have the time to do custom development. A better home for that sort of thing would be the lemmy-ui Issues tracker. If you post there, though, I would urge you to make sure any given issue only has a single feature request. The way you have shown it here, it would be very hard for a developer to decide what you were asking for.
Also please note that Beehaw is explicitly not trying to be reddit, despite some confused press coverage.
I suspect that Beehaw currently is skewed, as with many online early adopter communities, to those more interested in technology and computers. I think this is more a function of the early audience, not the target audience - the target audience is anyone who wants to participate in a nice friendly online community. Personally, I'd be happy to see more content from people who do sports, whether archery or anything else.
This is why I use DuckDuckGo instead of Google, and Firefox with a few selected extensions that ensure I almost never see an ad. I would be shocked if Google enabled any long-term ad-free experience.
I've seen this "sub affects logitech stock" story a few times now, and I don't find it very credible. If you look at the 1-month or longer price of the stock, it's pretty evident that (a) a 5% intraday variation in price is totally normal and (b) the recent news that has actually hurt the stock price substantially is that their CEO resigned.
I'm skeptical that Amazon review trolls are buying enough stock to move the market.
In addition to making it easier to find authentic perspectives, we're also improving how we rank results in Search overall, with a greater focus on content with unique expertise and experience. Last year, we launched the helpful content system to show more content made for people, and less content made to attract clicks. In the coming months, we’ll roll out an update to this system that more deeply understands content created from a personal or expert point of view, allowing us to rank more of this useful information on Search.
That seems like just a step in the inevitable AI arms race.
There's always a chance, though as you probably already know, the Beehaw admins are being cautious about community creation to avoid undue fragmentation. The current community survey has a camping/hiking community on the proposal list to vote on. If that community gets approved, it will probably launch as a more general "outdoor recreation" community, which might go some ways towards the sports pursuits community you're looking for - at least for some sports.
Looking at the public user numbers on the current Sports community, though, I think low engagement may just be that we don't have a lot of people around here who are interested in sports yet.
This exactly. The more developers working on different parts of an application, the more chance of an apparently-easy merge having unforeseen side effects. git bisect is the easiest way to narrow down the problem so real debugging can begin.
Well, most of my work was programming books, so honestly a 5 year copyright term would have been plenty. But the internet put most of those publishers out of business anyhow.
Outside of my own special case, I don't have really strong opinions on the term.
As a published author, I'm glad copyright existed. Without it, none of my publishers would have been in business and I would have had to find some other income source. But I think the default should be "public domain" rather than "copyright", and I'm skeptical of allowing corporations to own the copyright to individuals' works.
I re-read books frequently. But then, I am a fast and voracious reader. I've recently been trimming down my library from around 7000 books due to an upcoming move, and there's a hardcore of about 2000 I'm unwilling to get rid of because they're either reference materials or old friends I expect to re-read before I die. There are some things (LOTR, much Heinlein, Oz books, Alice in Wonderland...) that I've read a dozen times or more.
I do re-read some non-fiction, mainly history. But most of my well-worn books are fiction.
Keep your eyes open in the future...this is almost certainly not going to be the last round of community creation. The admins are being very deliberate about the process though.
Horrifying. And a splinter of the movement apparently led by men. It's easy to promote consequences that you're protected from by your lack of a uterus.
Assuming innovation, it seems like there would still be a need for some way for producers to inform potential consumers. I'd love to see advertising move from "create demand" to "provide information". Not at all sure how that might come about though.
Meanwhile, I personally get by just fine with blocking as many ads as possible, which is almost all of them, and going out and searching when I need information. But that probably doesn't scale to busier people.
Depended on the size of the team in my experience. With a project of ~50 devs split into 10 teams, I was having to resolve conflicts perhaps every other PR. But training and standards for workflow can certainly help.
Help make Beehaw the place you'd like to live in. Post interesting content in the communities that interest you. Add thoughtful comments. Be(e) nice. Don't feed the trolls.
I'm not an official spokescritter, but I can assure you the Beehaw admins aren't ignoring the issues. But ultimately it's going to come down to someone getting PRs in to the code. I hope someone gets some performance-focused PRs in soon.
Yes, Beehaw is struggling with uptime. From talking with the admins, this really isn't an nginx issue. It's more that the Lemmy code itself is immature, with memory leaks and SQL performance issues, and those issues are becoming more disruptive as the usage explodes.
If you've got development skills, helping out the Lemmy project on Github is probably the best way to help. If not, then just press F5 with the rest of us when the site goes down for a bit.
This really isn't the place for general Lemmy feature requests. The admin team here is very small and doesn't really have the time to do custom development. A better home for that sort of thing would be the lemmy-ui Issues tracker. If you post there, though, I would urge you to make sure any given issue only has a single feature request. The way you have shown it here, it would be very hard for a developer to decide what you were asking for.
Also please note that Beehaw is explicitly not trying to be reddit, despite some confused press coverage.