Beehaw Support
!support@beehaw.org
help-circle
rss
the July 2023 Beehaw financial update
pin
our [June 2023](https://beehaw.org/post/428209) financial update. --- obligatory preface: we're 100%-user funded and everything you donate to us specifically goes to the website, or any outside labor we pay to do something for us. because of the unique circumstances of this month i won't report an expected yearly expense like i did last time. that'll probably come next month, when our finances are closer to a useful baseline. --- #### overall expenses this month: $566.98 this is a mighty looking expense, but only **$371.98** of it is infrastructure (and even less of that is actually site hosting). **$312.54** for Digital Ocean hosting, which can be further subdivided into - $241.47 for hosting the site itself - $48.29 for backups - $11.87 for site snapshots - $10.91 for bandwidth overage (1091.10GB @ $0.01/GB) **$15.28** for Hive, an internal chat platform we're trying to set up (also being hosted on Digital Ocean, but distinct enough to break out from overall DO hosting) - $13.89 for hosting Hive - $1.39 for backups **~$39.16** for email functionality, which can be further subdivided into - $35/mo for Mailgun (handles outbound emails, so approval/denial/notifications emails; also lets us not get marked as spam) - ~$4.16/mo ($50/yr, already paid in full) for Fastmail (handles all inbound emails) **$5/mo** for 1TB of backup storage with BackBlaze (redundant backup system that's standalone from Digital Ocean) the remaining **$195** of this month's expenses have gone to paying [@UrLogicFails@beehaw.org](https://beehaw.org/u/UrLogicFails) for his community icons. we do so at a rate of $5 per icon and he's done 39 of them for us (36 of which are live so far). overall: we definitely think we're able to downsize infrastructure costs going forward. we're already investigating how best to do that (both in terms of host and overall cost)--there's no ETA for a few reasons, but this month should not be representative of many more subsequent months. #### overall contributions this month: $3,870.44 we also have an incredible amount of support, so that really helps things as far as "being able to take time to get everything right". according to OpenCollective, we currently have approximately: - 97 monthly contributions, totaling **$549.58** - 9 yearly contributions, totaling **$254.99** - 149 one-time donations, totaling **$3,065.87** between monthly and yearly contributions, this means we are still more-or-less breaking even and sustainable overall with this month's costs. obviously, we would like to be *substantially* moreso though, through either lower costs, more donations, or a combination of both. #### total end of month balance: $3,591.33 - yes yes, this is already out of date by a bunch. expect it to be like that, i use UTC for our reports lol. --- ##### expense runway, assuming no further donations - **assuming expenses like ours this month**: we have about 6 months and 10 days of runway - **assuming just expenses like our infrastructure this month**: we have 10 and a half months of runway if you'd like to make the runway longer (and reward us for even having this site up today after yesterday's complete fiasco), now is a good time to donate :)
fedilink

New Communities + Beehaw is once again looking for community moderators
pin
quick dual announcement ### New Communities we've tabulated the easiest part of the survey (other results coming [NOW](https://beehaw.org/post/849493?scrollToComments=true)) and we're pleased to announce that, in the future, we'll be creating six new communities. these six choices can be stratified as: most popular, community picks - World News - AskBeehaw hand picked, also popular with our community - Tabletop Gaming - Anime and Manga hand picked, base exists in our community for it and distinct enough to take a chance on - Vegan and Vegetarian[^1] - Parenting in the specific case of World News, the [!news@beehaw.org](https://beehaw.org/c/news) community will be converted into the "World News" section, and a separate !usnews community will be spun off for US-centric news. these communities will be created in batches of three. you'll see WN+US news conversion/AB/TG first, then A&M/V&V/P about a week after that. as for communities that didn't make it, these are best fits for now: - School & Education: [!humanities@beehaw.org](https://beehaw.org/c/humanities) - Camping & Hiking: [!greenspace@beehaw.org](https://beehaw.org/c/greenspace) or [!environment@beehaw.org](https://beehaw.org/c/environment) or [!chat@beehaw.org](https://beehaw.org/c/chat) - Fitness: [!chat@beehaw.org](https://beehaw.org/c/chat), occasionally [!betterment@beehaw.org](https://beehaw.org/c/betterment) - Photography: wherever it fits - TIL: [!chat@beehaw.org](https://beehaw.org/c/chat) - Travel: [!chat@beehaw.org](https://beehaw.org/c/chat) - Spirituality: [!chat@beehaw.org](https://beehaw.org/c/chat) and [!humanities@beehaw.org](https://beehaw.org/c/humanities) - Health: wherever it fits - Sustainability: can mostly go in [!environment@beehaw.org](https://beehaw.org/c/environment) - AntiWork/WorkReform: [!socialism@beehaw.org](https://beehaw.org/c/socialism) - Retro: wherever it fits ### Community Moderators this *also* means we're taking on new Community moderators. as with last time: this is not a full time job and we don't want it to be, but this is also not a completely *trivial* commitment either, so please only apply if you're comfortable with making that commitment. (if you think it's becoming overwhelming or too much for you at a later point, that's different and we can discuss that then.) our community mods haven't had many issues though, so i doubt you will either. --- ##### What is expected of community moderators? I'm sure you can surmise, but to be specific: - Encourage and promote respectful and constructive discussions, and address any behaviour that goes against our community's spirit to be(e) nice. - Assist people by answering their questions, offering guidance, and helping them navigate the platform effectively, ensuring they feel heard. - Where possible, give us and/or your fellow active mods concerns, improvements, or insights you have from your section of our community.  ##### What powers do community moderators have? You'd be expected to use these responsibly, obviously: - The ability to remove or hide posts, comments, or other content that violate our community guidelines. - The authority to issue warnings to users who breach our mantra, and in severe cases, temporarily suspend their accounts. We generally encourage a compassionate approach to moderating, though. Unless someone is clearly unproductive, we encourage you as a mod to engage in constructive dialogue before banning. And if you don't have the energy for this, you can flag a post to bring it to our (or another mod's) attention. Additionally: blatantly misusing these or using them maliciously will be instant grounds for demotion, and in the latter case likely permanent banning from the site. *Do not* do that, please and thank you. ##### If I'm selected, how can I report stuff to the admins? On site, you can flag it and leave it for us to deliberate. You can also reach one of us by DM on here. If you need to immediately contact us for mod stuff, our main hubs of operation are Discord (where we have a specific channel for community mod reports) and Matrix (which is pretty relaxed and easy to follow). You can also use a DM on Beehaw itself. ##### How will mods be selected? Hand selection. In the future we may supplement hand picking mods with another method—any mods selected by that method would most likely serve on a temporary basis (and that would be made clear to them on appointing). ### [Applications can be made here](https://forms.gle/Ae7qZBNKpMPWfQk17).[^2] [^1]: because i've already seen moderately concerning posts w/r/t to this: please do not make us regret this community. it is currently this grouping or nothing. [^2]: we are working on a non-Google platform here but our first alternative failed to materialize today and there are easily half a dozen other things we need to prioritize right now (including the big 0.18 update, which had its timing on here derailed by a crippling bug). we'll get to an alternative when we do. if you do not want to use the form, DM me and we can arrange something.
fedilink

Beehaw’s Demographics survey of June 2023!
pin
Compiling this data was not as hard as I expected, let's go through the data and the shiny graphs! ### Age of Beeple ![](https://beehaw.org/pictrs/image/fa1a8241-5fad-4e2a-ba95-2daed9359e87.png) Most are above 24! Seems we got an older average age compared to a lot of social media. It would be interesting to see how many came here with experiences from independent forums before Reddit. ### Where Beeple reside ![](https://beehaw.org/pictrs/image/d542e9d9-2916-43f2-9cca-3731e9877300.png) ![](https://beehaw.org/pictrs/image/924b2f3f-0495-414c-bc48-cc31438c396c.png) This one's a big graph. Though we can notice most people are from the US. Would be nice to see more countries represented though a big part of it likely has to do with language. (You will need to open the big graph in another tab, it's too big to show properly.) ### Gender identity of Beeple ![](https://beehaw.org/pictrs/image/44f9ed76-5d29-4c31-9ea0-0d52af706cf0.png) So, as expected, mostly men. However, less than expected which is nice to see. There should be outreach to at least equalize this. ### Sexual orientation of Beeple ![](https://beehaw.org/pictrs/image/45f29616-2031-477a-b1ff-addc0989aadb.png) This is kinda surprising. It seems we managed to get a lot more LGBTQ+ people than expected considering most of you all come from Reddit - so this is nice to see. This is most likely because of our focus on a safe space. ### Whiteness of Beeple ![](https://beehaw.org/pictrs/image/24c84413-6fd6-4e52-9aa7-24b8f711cd83.png) As expected, mostly white which is unfortunate. I think there's outreach to be done in that regard as well. ### Neurodivergence of Beeple ![](https://beehaw.org/pictrs/image/07d3efe0-835e-4bd1-8de6-810bfb2eb04e.png) We seem to have a really surprising amount of neurodivergent people! Definitely nice to see. ### Beeple with disabilities ![](https://beehaw.org/pictrs/image/31127d2e-e978-4307-8779-ab9fbd1b5c2a.png) I.. have no idea how to interpret this data so I'll just say, shiny graph. ### Beeple's awareness of the Fediverse ![](https://beehaw.org/pictrs/image/423df590-5ee5-4821-b886-84752c4369db.png) Most knew about the fediverse but still a good 20% had not heard about it so glad to see you all managed to find your way here! ### How Beeple have been dealing with Beehaw ![](https://beehaw.org/pictrs/image/cbd79799-28e9-49f4-9310-78f113af0401.png) ![](https://beehaw.org/pictrs/image/d2f8354d-4c5b-4eb7-b337-fad1e61368a3.png) It seems most people feel relatively confident in their ability to use Beehaw and most people seem to enjoy it. That makes me really happy to see. Feels rewarding, feels good. ### Conclusion I wanna thank everyone for the feedback about the survey and its questions - we'll do better next time! I'm glad we did this survey because it shows the areas to work on in terms of outreach! Thank you all for your participation!
fedilink

A few quick notes
pin
A few quick notes on discussions the administrator team has had, since we've fielded a lot of questions in these particular fields. We're posting this both for transparency and to help us limit the load of having to respond to each of you individually. * We would like to become an official nonprofit at some point, but there is a cost associated with this, we are not lawyers, and we might need to change where/how we collect donations to do so. * We've upgraded the server approximately 7 times now. We're trying to balance fiscal responsibility with server costs. We are aware that digital ocean isn't the cheapest server and we are trying to be conservative with estimates and give ourselves extra runtime at whatever tier we are on. We're also hoping that the upcoming lemmy version will solve a lot of our CPU-bound issues. We are aware of the following bugs: * the "report created" indicator flashes in the bottom left corner for some users randomly, even non-moderator users * sometimes, briefly or without a refresh, the username in the top corner will not be your own; as far as we can tell this is purely cosmetic and is not a security issue * sometimes the post you're in changes to another post for no clear reason
fedilink

Removed threads should still be reachable and interactive
I posted an apparently off-topic post to [!foss@beehaw.org](https://beehaw.org/c/foss). The moderator removed it from the timeline because discussion about software that ***should be*** FOSS was considered irrelevant to FOSS. Perhaps fair enough, but it’s an injustice that people in a discussion were cut off. The thread should continue even if it’s not linked in the community timeline. I received a reply that I could not reply to. What’s the point in blocking a discussion that’s no longer visible from the timeline? It’s more than just an unwanted behavior because the UI is broken enough to render a dysfunctional reply mechanism. That is, I can click the reply button to a comment in an orphaned thread (via notifications) and the UI serves me with a blank form where I can then waste human time writing a msg, only to find that clicking submit causes it to go to lunch in an endless spinner loop. So time is wasted on the composition then time is wasted wondering what’s wrong with the network. When in fact the reply should simply go through. (edit) this is similar to [this issue](https://beehaw.org/post/7638652). Slight difference though: [@jarfil@beehaw.org](https://beehaw.org/u/jarfil) merely expects to be able to reply to lingering notifications after a mod action. That’s good but I would go further and propose that the thread should still be reachable and functional (just not linked in the timeline where it was problematic).
fedilink

Votes fail to rank comment visibility
This series of single word spam has 1 vote each: https://beehaw.org/comment/2351412 Yet there are responses to the same comment with many more upvotes. Why don’t the higher valued comments rise above the comments with a score of 1?
fedilink

Minor UI/Quality of life issue
I've noticed that interacting with your feed on the Beehaw instance creates a bit of an odd issue: When you click on a link from the feed, or enter into a post/comment section, when you back out to the feed it sets you back to the *previous* page of the feed. The workaround I've found is that every time you move to a new page, you refresh the browser and that makes it "stick" while you go in and out of posts on that page. Not sure if anyone else has experienced this. It is a very minor issue, but I have an account with another instance where this doesn't happen. If it doesn't represent a lot of work to investigate/fix it would be a nice quality of life improvement. Or maybe you guys are already aware. This is on the Firefox mobile browser.
fedilink

the February 2024 Beehaw Financial Update
#### obligatory preface: we're 100%-user funded and everything you donate to us specifically goes to the website, or any outside labor we pay to do something for us. you can [donate here](https://opencollective.com/beehaw/donate). --- ### overall expenses for January: $212.04 **$139.16** for Digital Ocean hosting, which can be further subdivided into - $112.00 for hosting the site itself - $22.40 for backups - $4.76 for site snapshots **$28.80** for Hive, an internal chat platform we've set up (also being hosted on Digital Ocean) - $24.00 for hosting Hive - $4.80 for backups - $0.00 for snapshots **~$39.16** for email functionality, which can be further subdivided into - $35/mo for Mailgun (handles outbound emails, so approval/denial/notifications emails; also lets us not get marked as spam) - ~$4.16/mo ($50/yr, already paid in full) for Fastmail (handles all inbound emails) **$4.92** for BackBlaze, (redundant backup system that's standalone from Digital Ocean) - we internally flagged this because we don't have an explanation for why this is so low this month--but, as far as we can tell it lines up with what it "should" be, so... ### overall contributions in the past month: $696.59 - we received a single $193.32 one-time donation, while the remaining $503.27 was monthly ### total end of year balance: $6,781.73 #### expense runway, assuming no further donations - **assuming expenses like ours this month**: we have about two years and seven months of runway ### finance history | | [October](https://beehaw.org/post/8379926) | [November](https://beehaw.org/post/9231160) | [December](https://beehaw.org/post/10736040) | [January](https://beehaw.org/post/10736040) | February | |---------------|---------|-----------|-----------|-----------|---------| | Contributions | $691.85 | $596.28 | $660.43 | $562.79 | $696.59 | | Expenses | $230.81 | $231.54 | $229.09 | $230.68 | $212.04 | | Difference | +$461.04 | +$364.74 | +$431.34 | +$332.11 | +$484.55 | | Balance | $5,198.47 | $5,470.13 | $5,926.29 | $6,290.06 | $6,781.73 |
fedilink

Community Popularity
Dude(ettes), This community has dropped off _fast_ in the `now trending` list on the sidebar. That is **awesome**. When I first started supporting Beehaw, it was a matter of _minutes_ before the site crashed due to processing and load. Gone are the days of 3,4 or 10 posts in [Beehaw Support](https://beehaw.org/c/support) about content issues, server instability and server errors. Here are the days of _no_ support requested. We have improved the [uptime and responsiveness](https://status.beehaw.org) of Beehaw for all users, in a short time. Extenstive work and efforts have been placed into not only keeping Beehaw running; but _improving_ Beehaw. Those efforts and support have paid off I think. I say this as a primary systems admin of Beeehaw: --- # Thank you --- To all monetary supports and lurkers, your contributions are immensely appreciated. We hope you continue to find value in our presence on the internet and in the Fediverse.
fedilink

Beehaw still running Lemmy v0.18.4; current is v0.19.2. Any reason why?
I'm thinking this might be a good thing, since Lemmy v0.19.2 has introduced a new round of bugs and brought back some old ones. Is this why Beehaw is still running the older version? I'm just curious.
fedilink

the December 2023/January 2024 Beehaw Financial Update
#### obligatory preface: we're 100%-user funded and everything you donate to us specifically goes to the website, or any outside labor we pay to do something for us. you can [donate here](https://opencollective.com/beehaw/donate). this month is a double feature because i got sick last month and decided to just roll the December update into January's. ### overall expenses for November and December: $229.09 (Nov) + $230.68 (Dec) #### $459.77 between both months both months had the same breakdown for everything besides BackBlaze, which was: **$134.40** for Digital Ocean hosting, which can be further subdivided into - $112.00 for hosting the site itself - $22.40 for backups - $0.00 for site snapshots **$28.80** for Hive, an internal chat platform we've set up (also being hosted on Digital Ocean) - $24.00 for hosting Hive - $4.80 for backups - $0.00 for snapshots **~$39.16** for email functionality, which can be further subdivided into - $35/mo for Mailgun (handles outbound emails, so approval/denial/notifications emails; also lets us not get marked as spam) - ~$4.16/mo ($50/yr, already paid in full) for Fastmail (handles all inbound emails) for BackBlaze, (redundant backup system that's standalone from Digital Ocean), the difference in months was as follows: - November: **$26.73** - December: **$28.32** ### overall contributions in the past two months: $1,223.22 - November: $660.43 - $75.89 of this was in one-time donations, while the remaining $584.54 was monthly - December: $562.79 - $23.45 of this was in one-time donations, while the remaining $539.34 was monthly ### total end of year balance: $6,290.06 #### expense runway, assuming no further donations - **assuming expenses like ours this month**: we have about two years and three months of runway ### finance history | | [September](https://beehaw.org/post/7563806) | [October](https://beehaw.org/post/8379926) | [November](https://beehaw.org/post/9231160) | December | January |---------------|---------|-----------|-----------|-----------|---------| | Contributions | $1,033.82 | $691.85 | $596.28 | $660.43 | $562.79 | Expenses | $264.50 | $230.81 | $231.54 | $229.09 | $230.68 | Difference | +$769.32 | +$461.04 | +$364.74 | +$431.34 | +$332.11 | Balance | $4,701.66 | $5,198.47 | $5,470.13 | $5,926.29 | $6,290.06
fedilink

On the behavior of moderators
A couple days ago, a thing transpired between two users, namely Axolotling and DroneRights on this website. They were having a thing over intentions and empathy, but the important thing is that DroneRights expressed the fact not everyone should speculate on someone’s intentions, which I’d say is a fair thing to say. The mods, seeing that DroneRights laid out all of their intentions and what Axolotling could do to hopefully understand its POV, decided to call it “pompous”. That, I think, breaks the whole principles that Beehaw stands for, mainly those of acknowledging good faith when it happens and not randomly banning a user because an admin felt the way they word themselves is “pompous”, which I don’t think it was to begin with. Now, I actually do believe in the principles of this federation and I’m not here to start a shitstorm or to stoke the fire more; I’m here to understand how was it possible for a moderation team to see someone who was willing to help someone else understand their point of view and be met with moderators jumping in out of nowhere without truly understanding what had happened.
fedilink

2FA link not working
I'm trying to enable 2FA, the link generated does not work.
fedilink

Is Beehaw federating with Threads?
I'm out of the loop. Are we federating with Threads or not? EDIT: The answer is no, we are not federating with Threads. Thank you. That's the answer I was hoping for.
fedilink

[resolved] Finance community unreachable
When trying to access https://beehaw.org/c/finance it gives a 502 bad gateway -- “Worker Bees are busy updating the website”.
fedilink

What happened to beehaw potentially moving to a new platform?
Hey folks! Sorry if this has been covered elsewhere but I did a search around the site and I just couldn't find the information I was looking for. I remember reading a while back that the folks at beehaw were considering moving to a new platform and I was just curious if anything came of that? Thanks for all you do!
fedilink

the November 2023 Beehaw Financial Update
#### obligatory preface: we're 100%-user funded and everything you donate to us specifically goes to the website, or any outside labor we pay to do something for us. you can [donate here](https://opencollective.com/beehaw/donate). ### overall expenses this month: $230.81 **$134.40** for Digital Ocean hosting, which can be further subdivided into - $112.00 for hosting the site itself - $22.40 for backups - $0.00 for site snapshots **$28.80** for Hive, an internal chat platform we've set up (also being hosted on Digital Ocean) - $24.00 for hosting Hive - $4.80 for backups - $0.00 for snapshots **~$39.16** for email functionality, which can be further subdivided into - $35/mo for Mailgun (handles outbound emails, so approval/denial/notifications emails; also lets us not get marked as spam) - ~$4.16/mo ($50/yr, already paid in full) for Fastmail (handles all inbound emails) **$29.18** for BackBlaze (redundant backup system that's standalone from Digital Ocean) ### overall contributions this month: $596.28 - all contributions this month were monthly donations. ### total end of month balance: $5,470.13 #### expense runway, assuming no further donations - **assuming expenses like ours this month**: we have about two years of runway ### finance history | | [July](https://beehaw.org/post/920683) | [August](https://beehaw.org/post/6921483) | [September](https://beehaw.org/post/7563806) | [October](https://beehaw.org/post/8379926) | November |---------------|---------|-----------|-----------|-----------|---------| | Contributions | $3,870.44 | $1,310.90 | $1,033.82 | $691.85 | $596.28 | Expenses | $566.98 | $523.79 | $264.50 | $230.81 | $231.54 | Difference | +$3,303.46 | +$787.11 | +$769.32 | +$461.04 | +$364.74 | Balance | $3,591.33 | $4,347.79 | $4,701.66 | $5,198.47 | $5,470.13
fedilink

Is there an appropriate place to advertise a community sharing full length college lectures?
The community can be found at !opencourselectures@slrpnk.net. Are there any appropriate places under the beehaw umbrella?
fedilink

2FA Help
I just tried to enable 2FA on my account, it said to save and refresh to get the setup code etc but it just logged me out. Now I can’t login without a 2FA code that I don’t have. Any chance I can get a bit of help resetting it so I can log back in again? I’m still logged in on this device (via the voyager app) so hopefully this post works!
fedilink

Hide Post Feature
Is there anything in the works that will allow us to hide posts? Report isn't necessary in a lot of cases which just leaves the block option. It works but it's also overkill.
fedilink

Unable To Load Extra Replies
Hi beeautiful people. On certain posts, reply chains seem to be hidden by a "x more replies" button. When I try to click to expand these replies, however, I'm met with an eternally-spinning wheel. I've tried this in both Chrome and Firefox, with extensions enabled and disabled, all to the same effect. Any help is appreciated. Browser: Chrome 118.0.5993.88 (Also reproduced on the latest Firefox) Platform: Fedora 38 Thanks. :) Sloppy video recording of the behavior in question: https://youtu.be/rWbZc3wdVC4 The thread I used as an example: https://beehaw.org/comment/1433678 Update: I finally figured out that this happens on threads where I have one of the participants blocked. Everyone can look away now.
fedilink

Creating a new community
Is creating a new community at will not an option on Beehaw?
fedilink

the October 2023 Beehaw Financial Update
#### obligatory preface: we're 100%-user funded and everything you donate to us specifically goes to the website, or any outside labor we pay to do something for us. you can [donate here](https://opencollective.com/beehaw/donate). ### overall expenses this month: $230.81 **$134.66** for Digital Ocean hosting, which can be further subdivided into - $108.00 for hosting the site itself - $21.60 for backups - $5.06 for site snapshots **$27.81** for Hive, an internal chat platform we've set up (also being hosted on Digital Ocean) - $23.14 for hosting Hive - $4.63 for backups - $0.04 for snapshots **~$39.16** for email functionality, which can be further subdivided into - $35/mo for Mailgun (handles outbound emails, so approval/denial/notifications emails; also lets us not get marked as spam) - ~$4.16/mo ($50/yr, already paid in full) for Fastmail (handles all inbound emails) **$29.18** for BackBlaze (redundant backup system that's standalone from Digital Ocean) ### overall contributions this month: $691.85 support still more than covers our expenses; interestingly, our donation composition is now almost exclusively monthly donations. - 108 monthly contributions, totaling **$668.33** - 2 one-time donations, totaling **$23.52** ### total end of month balance: $5,198.47 #### expense runway, assuming no further donations - **assuming expenses like ours this month**: we have about one year and seven months of runway. ### finance history | | [June](https://beehaw.org/post/428209) | [July](https://beehaw.org/post/920683) | [August](https://beehaw.org/post/6921483) | [September](https://beehaw.org/post/7563806) | October | |---------------|---------|-----------|-----------|-----------|---------| | Contributions | $705.00 | $3,870.44 | $1,310.90 | $1,033.82 | $691.85 | | Expenses | $54.00 | $566.98 | $523.79 | $264.50 | $230.81 | | Difference | +$651.00 | +$3,303.46 | +$787.11 | +$769.32 | +$461.04 | | Balance | $726.51 | $3,591.33 | $4,347.79 | $4,701.66 | $5,198.47 |
fedilink

On Beehaw there are a few [tldr](https://beehaw.org/u/autotldr@lemmings.world) [bots](https://beehaw.org/u/autotldr@programming.dev) from other instances. I present Beehaws own [summarizing bot](https://beehaw.org/u/AbstractifyBot) developed by yours truly. Based on feedback from moderators and community leaders, I don't just want to let this loose on the entire site. Might cause confusion and spam for a community instead of being useful. If you do like what that bot does, and are a moderator of a community on Beehaw that wants to use it; send a private messaged to `AbstractifyBot` stating `Summarize articles on c/[communityname]`. That's just one aspect, but I have a few more questions while I have your attention. * What type of bots _if any_ do you want to see on Beehaw to help things/your community? * Which functions of the 'nice to have' should be **built in** and not reliant on a bot to do? * What do you **need** for your communities to thrive here?
fedilink
1

Permanently deleted
*Permanently deleted*
fedilink

[db0 from dbzer0.com] I just developed and deployed the first real-time protection for lemmy against CSAM!
cross-posted from: https://lemmy.dbzer0.com/post/4500964 > cross-posted from: https://lemmy.dbzer0.com/post/4500908 > > > In the past months, there's a been a issue in various instances where accounts would start uploading blatant CSAM to popular communities. First of all this traumatizes anyone who gets to see it before the admins get to it, including the admins who have to review to take it down. Second of all, even if the content is a link to an external site, lemmy sill caches the thumbnail and stores it in the local pict-rs, causing headaches for the admins who have to somehow clear that out. Finally, both image posts and problematic thumbnails are federated to other lemmy instances, and then likewise stored in their pict-rs, causing such content to be stored in their image storage. > > > > This has caused multiple instances to take radical measures, from defederating liberaly, to stopping image uploads to even shutting down. > > > > Today I'm happy to announce that I've spend multiple days developing a tool you can plug into your instance to stop this at the source: [pictrs-safety](https://github.com/db0/pictrs-safety) > > > > Using a new feature from pictr-rs 0.4.3 we can now cause pictrs to call an arbitary endpoint to validate the content of an image before uploading it. pictrs-safety builds that endpoint which uses an asynchronous approach to validate such images. > > > > I had already developed [fedi-safety](https://github.com/db0/fedi-safety) which could be used to regularly go through your image storage and delete all potential CSAM. I have now extended fedi-safety to plug into pict-rs safety and scan images sent by pict-rs. > > > > The end effect is that any images uploaded or federated into your instance will be scanned in advance and if fedi-safety thinks they're potential CSAM, **they will not be uploaded to your image storage at all!** > > > > This covers three important vectors for abuse: > > > > * Malicious users cannot upload CSAM to for trolling communities. Even novel GenerativeAI CSAM. > > * Users cannot upload CSAM images and never submit a post or comment (making them invisible to admins). The images will be automatically rejected during upload > > * Deferated images and thumbnails of CSAM will be rejected by your pict-rs. > > > > Now, that said, this tool is AI-driven and thus, not perfect. There will be false positives, especially around lewd images and images which contain children or child-topics (even if not lewd). This is the bargain we have to take to prevent the bigger problem above. > > > > By my napkin calculations, false positive rates are below 1%, but certainly someone's innocent meme will eventually be affected. If this happen, I request to just move on as currently we don't have a way to whitelist specific images. Don't try to resize or modify the images to pass the filter. It won't help you. > > > > ### For lemmy admins: > > > > * pictrs-safety contains [a docker-compose sample](https://github.com/db0/pictrs-safety/blob/main/docker-compose.yml) you can add to your lemmy's docker-compose. You will need to your put the .env in the same folder, or adjust the provided variables. (All kudos to [@Penguincoder@beehaw.org](https://beehaw.org/u/Penguincoder) for the docker support). > > * You need to adjust your pict-rs ENVIRONMENT as well. Check the readme. > > * fedi-safety **must** run on a system with GPU. The reason for this is that lemmy provides just a 10-seconds grace period for each upload before it times out the upload regardless of the results. A CPU scan will not be fast enough. However my architecture allows the fedi-safety to run on a different place than pictrs-safety. I am currently running it from my desktop. In fact, if you have a lot of images to scan, you can connect **multiple** scanning workers to pictrs-safety! > > * For those who don't have access to a GPU, I am working on a NSFW-scanner which will use the [AI-Horde](https://aihorde.net) directly instead and won't require using fedi-safety at all. Stay tuned. > > > > ### For other fediverse software admins > > > > fedi-safety can already be used to scan your image storage for CSAM, so you can also protect yourself and your users, even on mastodon or firefish or whatever. > > > > I will try to provide real-time scanning in the future for each software as well and PRs are welcome. > > > > ### Divisions by zero > > This tool is already active now on divisions by zero. It's usage should be transparent to you, but do let me know if you notice anything wrong. > > > > ### Support > > > > If you appreciate the priority work that I've put in this tool, please consider supporting this and future development work on liberapay: > > > > https://liberapay.com/db0/ > > > > All my work is and will always be FOSS and available for all who need it most. > >
fedilink
1
[db0 from dbzer0.com] I just developed and deployed the first real-time protection for lemmy against CSAM!

@support Yesterday I saw this post https://beehaw.org/post/7776438 where it used the non-propagation of deleted posts as an example o
[@support](https://beehaw.org/c/support) Yesterday I saw this post [https://beehaw.org/post/7776438](https://beehaw.org/post/7776438) where it used the non-propagation of deleted posts as an example of one of the problems of the Lemmy platform. Today, this post [https://lemmy.world/post/5289864](https://lemmy.world/post/5289864) says there's "a bug in kbin where moderation tasks are not federated to other instances".. i'm confused, isn't that a problem coming from the underlying software, Lemmy? Are they shifting blame?
fedilink
1
@support Yesterday I saw this post https://beehaw.org/post/7776438 where it used the non-propagation of deleted posts as an example o

I'm on Firefox on android on pixel 7. Just started seeing this today. It's not a big deal. But it's weird it started suddenly.
fedilink

Anybody else having this issue (attached screenshot). Landscape mode is fine. I'm guessing this is an upstream issue. Text alignment is all over the place. Eta: this is in Firefox on Android
fedilink

Permanently deleted
*Permanently deleted*
fedilink

Problem with 2FA
Hello, I have been accesing beehaw through Jerboa and Wefwef, recently due to the timezone issue I had to use the website. When I try to log in I'm asked to enter a 2FA token but I don't think I ever activated that. I'm able to access my account through wefwef now because my credentials were stored here and the issue has been fixed, but I can't access beehaw settings from here to disable 2fa. Would you be able to disable 2FA for my account? Thanks in advance!
fedilink

A brief note on lost posts
you might have noticed we lost a bunch of posts... in short: we tried to fix [a Lemmy issue](https://github.com/LemmyNet/lemmy/pull/3496) that [started on 9/13](https://beehaw.org/post/7854854) and is causing or has caused problems with apps for the software. we're aware of basically all of them besides Sync exhibiting some sort of problematic behavior since this issue arose. however: attempting to fix this issue on our side of things did not go well. i am not qualified to make a formal write-up of the exact mechanism of what went wrong here--and in this case the mechanism isn't really important for your informational purposes, although [@Penguincoder@beehaw.org](https://beehaw.org/u/Penguincoder) can elaborate as needed--but basically we made a fix that seemed fine in testing and was *not* fine when actually applied. when it became obvious something was wrong, we tried restoring literally everything but the database. that, unfortunately, did not work, so eventually we just pulled the trigger on restoring from a backup. this has lost at least some posts, but probably no more than 8 hours of them by our estimation. *hopefully* this will not happen again, either upstream or on our side of things.
fedilink

Lost posts/comments
Has something happened? I made 3 posts and a few comments late yesterday and they're all gone today (but still appear on the federated instances I posted them to)
fedilink

Can’t load Beehaw on Jerboa or Connect
Starting this morning Jerboa crashes and Connect for Lemmy shows a spinner when trying to access Beehaw. My accounts on other Lemmy instances are working fine. Is anyone else having similar issues?
fedilink

  • liv
  • English
  • edit-2
    5M
Is there any way to turn off automatically loading embedded images in comments?
I find they make it harder to read and as I'm under data restrictions it would be nice to not load them. Sorry if this has been asked before. I know the lemmy software has a lot of limitations too so maybe this is one of them.
fedilink

Beehaw on Lemmy: The long-term conundrum of staying here
Yesterday, you probably saw [this informal post](https://beehaw.org/post/7754304) by one of our head admins (Chris Remington). This post lamented some of the difficulties we’re running into with the site at this point, and what the future might hold for us. This is a more formal post about those difficulties and the way we currently see things. Up front: *we aren't confident in the continued use of Lemmy*. We are working through how best to make the website live up to the vision of our documents—and simply put, the vast majority of the limitations we're running into are Lemmy's at this point. An increasing amount of our time is spent trying to work around or against the software to achieve what we want rather than productively building this community. That leaves us with serious questions about our long-term ability to stay on this platform, especially with the lingering prospect of not having the people needed to navigate backend stuff. Long-time users will no doubt be aware of our advocacy for moderator tools that we think the platform needs (and particularly that *we* need). Our belief in the importance and necessity of those tools has only hardened with time. Progress of those tools, however—and even organizing work on them—has been pretty much nonexistent outside of our efforts from what we can see.[^1] In the three months since we started seriously pushing the ideas we'd like to see, we’re not aware of *any* of them being seriously considered—much less taken up or on the way to being incorporated into Lemmy. In fact: even within the framework of Lemmy's almost nonexistent roadmap and entirely nonexistent timetable on which to expect features it has been made clear to us that improving federation or moderation on the platform are not big priorities.[^2] We have implicitly been told that if this part of the software is to improve we will need to organize that from scratch. And we *have* tried that to be clear. Our proposal is (and has been) paying people bounties for their labor toward implementing these features, in line with paying all labor done on our behalf—but we've received mixed messages from the top on whether this would be acceptable. (Unclear guidance and general lack of communication is symptomatic of a *lot* of our relation with the Lemmy devs in the past few months.) Things aren't much better on the non-moderator side of things. The problems with databases are almost too numerous to talk about and even Lemmy's most ardent supporters recognize this as the biggest issue with the software currently. A complete rewrite is likely the only solution. Technical issues with the codebase are also extensive; we've made numerous changes on our side because of that. Many of the things we're running into have been reported up the chain of command but continue to languish *entirely unacknowledged*. In some cases bugs, feature requests, and other requests to Lemmy devs have explicitly been blown off—and this is behavior that others have also run into with respect to the project. Only very recently have we seen any overtures at regular communication—and this communication has not hinted at any change in priorities. All of what was just described has been difficult to get a handle on—and having fewer users, less activity, and more moderators has not done a whole lot to ease that. We honestly find that the more we dig and the more we work to straighten out issues that pop up, the more pop out and the more it feels like Lemmy is structurally unsound for our purposes. (One such example of what we’re working with is provided in the next section.) In summary: we believe we can either continue to fight the software in basically every way possible, or we can prioritize building the community our documents preach. It is our shared belief that we cannot, in the long-term, do both; in any case, we're not interested in constantly having to fight for basic priorities—ones we consider extremely beneficial to the health of the overall Lemmy network—or having to unilaterally organize and recruit for their addition to the software. We are hobbyists trying to make a cool space first and foremost, and it's already a job enough to run the site. We *cannot* also be surrogates for fixing the software we use. ### PenguinCoder: A brief sketch of the technical perspective I've said a few words about this topic already, [here](https://beehaw.org/post/980868) and [here](https://beehaw.org/comment/1134544). Other Beehaw admins have also [brought](https://beehaw.org/comment/1018508) some [concerns](https://discuss.online/post/12787) to the Lemmy devs. Those issues still exist. To be clear: this is a volunteer operation and Lemmy is **their** software; they have a right to pick and choose what goes into it and what to put a priority on. But we have an obligation to keep users safe and secure, and their priorities increasingly stifle our own. In the case of this happening for open source projects, the consensus is to make your own fork. But: > The problem with forking Lemmy is in starting from all the bad that is inherently there, and trying to make it better. That is _way more work_ than starting fresh with _more developers_. IE, not using Rust for a web app and UI, better database queries from the start, better logging/functions _from the start_; not adding on bandaids. A fork of Lemmy will have all of Lemmy's problems but now _you're_ responsible for them instead. **We don't need a fork, we need a solution.** To give just *one* painful example of where an upstream solution is sorely needed: the federation, blocking, and/or removal of [problem images](https://beehaw.org/post/7426279). 1) You post an image to Beehaw. 2) Beehaw sends your content out to every other server it's federated with 3) Federated server accepts it (beehaw.org is on their allowlist), or rejects it (beehaw.org is on their denylist) 4) If the server accepts it, a copy of _your post or comment including the images_ are now on that receiving server as well as on the server you posted it to. Federation at work. 5) Mod on beehaw.org sees your post doesn't follow the rules. Removes it from beehaw.org. The other instances Beehaw pushed this content to, **do not get that notice to remove it**. The copy of your content on Beehaw was removed. The copy of your content _on other servers was not removed_. 6) The receiving federated instance needs to manually remove/delete the content from their own server 7) For a text post or comment that's removed, this can be done via the admin/mod tools on that instance 8) For a post or comment including a thumbnail, uploaded images, etc; **that media content is not removed**. It's not tracked where in Lemmy that content was used at. Admin removal of media commences. This requires backend command line and database access, and takes about a *dozen* steps per image; sometimes more. There are *dozens* of issues—some bigger, some smaller—like this that we have encountered and have either needed to patch ourselves or have reported up the chain without success. ### Alternatives and the way forward If possible the best solution here is to stay on Lemmy—but this is going to require the status quo changing, and we’re unsure of how realistic that is. If we stay on Lemmy, it is probable that we will have to do so by making use of a whitelist. For the unfamiliar, we currently use a *blacklist*—by default, we federate with all current and newly-created nodes of the Fediverse unless we explicitly exclude them from interacting with our site. A switch to a *whitelist* would invert this dynamic: we would *not* federate with anybody unless we explicitly choose to do so. This has some benefits—maintaining federation in some form; staying on Lemmy; generally causing less entropy than other alternatives, etc. But the drawbacks are also obvious: nearly everything described in this post *will* continue, blacklist or whitelist, because a huge part of the problem is Lemmy. Because of that we have discussed *almost every* conceivable alternative there is to Lemmy. We are interested in the thoughts of this community on platforms you have all used and what our eventual choice is going to be, but we are planning on having more surveys in the future to collect this feedback. We ask that you do not suggest anything to us at this time, and comments with suggestions in this thread will be removed. As for alternatives we’re seriously considering right now: they’re basically all FOSS; would preserve most aspects of the current experience while giving us less to worry about on the backside of things (and/or lowering the bar for code participation); are pretty much all more mature and feature-rich than Lemmy; and *generally* seem to avoid the issues we’re talking about at length here. Downsides are varied but the main commonality is lack of federation; entropy in moving; questions of how sustainable they are with our current mod team; and more cosmetic things like customization and modification. We’re currently investigating the most promising of them in greater depth—but we don’t want to list something and then have to strike it, hence the vagueness. If we make a jump, that will be an informed jump. In any case logistics mean that the timetable here is on the order of months. Don’t expect immediate changes. As things develop, we’ll engage the community on what the path forward is and how to make it as smooth as possible. [^1]: Other administrators have probably vocally pushed for these things, but we’re not aware of any public examples we can point to of this taking place. Their advocacy has not produced results that we're aware of in any case, which is what matters. [^2]: Perhaps best illustrated by the recent [Lemmy dev AMA](https://beehaw.org/post/7007045?scrollToComments=true). We’ll also emphasize that Beehaw’s admin team is not alone in the belief that Lemmy devs do not take mod tools or federation issues particularly seriously.
fedilink

problem creating a community
I filled out the form and clicked “create”. It turned into a spinner for a few seconds then just went back to the form. No error, but no action either. When I search for the new community, there are no results.
fedilink

Deleted posts
It's unnerving to find an interesting post, with an interesting conversation, only to see it deleted (not even mod removed) with hanging replies in the inbox and no way to reply back. Is there any feature that would allow continuing those conversations? Other than direct messages, which get "black holed" (no way to see own replies). Could these conversations be somehow continued, either recovered in Lemmy, or maybe via Mastodon?
fedilink

[CLOSED] a Beehaw survey on some policy and the site’s vibes
lock
good morning, Beehaw this morning we have a survey for you, which will run for approximately three days. it contains three questions on site policy (plus an optional explanation field), and two questions about the site's current vibe (plus another optional explanation field). ### [you can find the survey here](https://forms.beehaw.org/form/z10D4PZnWN-5VFPeu6FW11gAW9Gkkb5Bxt8wV1pOIPc). ---- ### some caveats to this survey you likely have some priors for how this "should" work, and i would like you to leave those at the door. to be up front: - **this is not a referendum**—it is more like a Wikipedia vote if anything. we're looking for a consensus or a synthesis of the community's opinions with the practical limitations we're working with, not a first-past-the-post winner. - **this is not (currently) a democracy, and you should not expect public results from this.** we talked this part over as an admin team and we don't see much value in publicly releasing the results of a survey like this. if we *do* release the results publicly, we'll be announcing that before it happens. - **the same caveats just mentioned will apply to any surveys like this into the foreseeable future.** i'm sure everyone understands that in online spaces it is very easy to manipulate surveys like this; accordingly, it is not a great idea to take them at complete face value until you can audit votes. since we don't have a foolproof, private system for doing that yet, these caveats are necessary to make any kind of vote involving site policy work. (we do eventually want to create a foolproof enough private system, but this is way on the backburner and i'm guessing most of you prefer having an imperfect way to chime in on the site's direction than none at all until this system is created)
fedilink

The September 2023 Beehaw Financial Update
obligatory preface: we’re 100%-user funded and everything you [donate](https://opencollective.com/beehaw/donate) to us specifically goes to the website, or any outside labor we pay to do something for us. ### overall expenses this month: $264.50 We downsized this month which has significantly brought down our costs, but it involved quite a few steps so it's a bit complicated to roll everything up. For simplicity purposes I rolled all the snapshots, backups, and hosting together for old/new droplets by service. **$177.46** for Digital Ocean hosting, which can be further subdivided into * $157.50 for hosting the site itself * $2.28 for backups * $17.68 for site snapshots **$29.60** for Hive, an internal chat platform we’ve set up (also being hosted on Digital Ocean) * $24.00 for hosting Hive * $4.80 for backups * $0.80 for snapshots **~$39.16** for email functionality, which can be further subdivided into * $35/mo for Mailgun (handles outbound emails, so approval/denial/notifications emails; also lets us not get marked as spam) * ~$4.16/mo ($50/yr, already paid in full) for Fastmail (handles all inbound emails) **$18.28** for BackBlaze (redundant backup system that’s standalone from Digital Ocean) ### overall contributions this month: $1,033.82 support still more than covers our expenses, thank you everyone! breakdown is: * 114 monthly contributions, totaling **$793.82** * 12 one-time donations, totaling **$240.00** It seems like the majority of our flow has shifted to monthly contributions and we are still sustainable overall ### total end of month balance: $4,701.66 #### expense runway, assuming no further donations * **assuming expenses like ours this month:** we have about 17 months and three weeks of runway
fedilink

Beehaw Support
!support@beehaw.org
    Create a post

    Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.

    A brief FAQ for lurkers and new users can be found here.

    Our November 2023 financial update is here.

    For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community


    This community’s icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.


    if you can see this, it's up  

    • 0 users online
    • 2 users / day
    • 7 users / week
    • 26 users / month
    • 49 users / 6 months
    • 1 subscriber
    • 348 Posts
    • 4.57K Comments
    • Modlog
    Beehaw
    Aspiring to be(e) a safe, friendly and diverse place.

    We’re a collective of individuals upset with the way social media has been traditionally governed. A severe lack of moderation has led to major platforms like Facebook to turn into political machinery focused on disinformation campaigns as a way to make profit off of users. Websites with ineffective moderation allow hate speech to proliferate and contribute to the erosion of minority rights and safe spaces. Our goal with Beehaw is to demonstrate and promote a healthier environment.

    Our philosophy:

    Downvotes are disabled on this instance.

    Be(e) nice.


    As a news aggregator and a social media outlet, with a focus on being a safe and accepting space, we strive to create a positive social impact. We will, also, help to connect underprivileged and minority individuals with education and civic participation by promoting a healthier online experience.


    We currently have a Mastodon account you can follow for major updates: @beehaw at hachyderm.io. You can also join our community Discord or Matrix servers. You can also view our status page.


    Our instance is 100% user-funded - help us keep it running by donating.

    If you donate, you should know that 100% of the costs will go towards server time, licensing costs, and artwork. In the future if we need to hire developers or other labor, it would be sourced through the Open Collective Foundation, and it would be transparent to the community before any changes were made.

    Donate on Opencollective


    Our community icons were made by Aaron Schneider under the CC-BY-NC-SA-4.0 license.

    Our most up to date FAQ can be found here.


    if you can see this, it's up