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 :)

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.

Compiling this data was not as hard as I expected, let's go through the data and the shiny graphs! ### Age of Beeple  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   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  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  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  As expected, mostly white which is unfortunate. I think there's outreach to be done in that regard as well. ### Neurodivergence of Beeple  We seem to have a really surprising amount of neurodivergent people! Definitely nice to see. ### Beeple with disabilities  I.. have no idea how to interpret this data so I'll just say, shiny graph. ### Beeple's awareness of the Fediverse  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   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!

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

There are a lot of tanky posts coming from lemmy.ml. Their whole purpose seems to be to troll and spread their bullshit far and wide. They are nearly as bad as the alt-right. They argue in bad faith and celebrate authoritarian oppression. The beehaw mods might want to consider defederating.

we discovered this set the other day by [olivvybee](https://github.com/olivvybee/blobbee/) (Liv Asch), and obviously these are delightfully thematic for our instance. you should be able to find them in our emoji picker as follows. the emoji icon, at least on desktop, is the fourth from left smiley face on comment/post UI:  

welcome to the second-ever Beehaw Community Survey. it's been awhile because of everything going on; we last did one of these with the influx of people last [June](https://beehaw.org/post/849832) and we got 1,500 responses that time. we don't expect anywhere near that many this time, but that's fine. this survey should take about 10 minutes to fill out, so we strongly encourage you to do so when you are able to. you can find it at the following link: ### [Beehaw Community Survey #2](https://forms.beehaw.org/form/s0JHlvdr0mqjPmaEY8dRLezBGKy0VZqUjeWbrB_ACIY) --- the survey is comprised of **eight** optional demographic questions to help us assess the overall identity of our community and **eight** questions relating to Beehaw and the Fediverse. the survey will be open for at least three days but no longer than one week. it'll be locally pinned for the duration of that minimum three days, so please mind that. results will also be aggregated and posted on here/the Docs page in a summary like with the last survey. no ETA on that. --- this is also a good time to remind everyone that Beehaw has moved over to Open Collective Europe Foundation, and we will be taking all donations from there going forward. please direct your donations [there](https://opencollective.com/beehaw-collective) if you haven't switched from our old Open Collective Foundation page yet!

Hello, I've been receiving this notice from voyager and wanted to hesr your thoughts. I don't understand the tech side of this at all. But, I'm curious if you have plans to update, or if I should find a new client to view beehaw. Thanks! https://lemmy.world/post/12479493

I remember watching this project as it was getting started. It was a replacement to all those PHP forums, like PHPBB & Simple Machines BB. This claimed to have more modern features. It's also open-source, and you can self-host or pay them for hosting. (I recommend the latter) And since we're on the subject, has Beehaw considered using an old PHP forum, like I mentioned earlier? They're really basic and quite nice, IMHO.

## tl;dr: Beehaw has moved over to Open Collective Europe Foundation, please direct your donations [there](https://opencollective.com/beehaw-collective) effective immediately. --- In some good news, we've successfully moved over to Open Collective Europe Foundation as our new fiscal host. This process has been mercifully quick and fairly painless, for which we're thankful. Going forward, please make all donations to the [Beehaw Collective](https://opencollective.com/beehaw-collective) there instead of the previous Beehaw page affiliated with Open Collective Foundation. We'll be mothballing that one following this post going live and according to OCF should be able to merge the page back into our new one sometime after April. Our balance of approximately $7,100 is in the process of being transferred and we do not expect issues there. OCF just submitted a transfer request today for us, and OCEF will let us know when that balance hits our new collective. We would encourage you to manually restart your contribution as soon as possible just for sake of ease and because our financial schedule will be very different going forward. However, starting later this month—at least based on what [Open Collective](https://blog.opencollective.com/fiscal-host-transition/) is saying—anybody still signed up to make contributions to the old page *should* receive an email with the following information: - an invitation to renew your contributions on the new collective page - direction to a page which will be pre-loaded with the amount and frequency of the contribution you made on the old collective, which you will then confirm So, don't fret too much if you can't immediately and manually switch. Spaced email reminders should also go out until Open Collective Foundation shuts down at the end of the year. If any of this does *not* happen, please page us and we'll see what's up.

Hello folks, this is an impromptu emergency announcement. In short: Open Collective Foundation, the fiscal host we use for Beehaw, will no longer accept donations starting on March 15, 2024. They will shut down completely at the end of the year, December 31, 2024. This was an extremely sudden decision by them; we were only made aware of it last night through their email to us. The cause given is "Open Collective Foundation’s business model is not sustainable with the number of complex services we have offered and the fees we pay to the Open Collective Inc. tech platform;" they note that they froze accepting new collectives last year. This obviously presents a lot of problems for Beehaw. Here are all the relevant dates given to us by Open Collective: - Last day to accept funds/receive donations: March 15, 2024 - Last day collectives can have employees: June 30, 2024 - Last day to spend or transfer funds: September 30, 2024 - Day they formally dissolve: December 31, 2024 Because Open Collective holds our funds, based on our understanding it seems likely we will not be able to keep our existing funds unless we find a 501(c)(3) organization to be our new fiscal host or become one ourselves by September 30. (EDIT: Or, we just spend it all preemptively.) Open Collective Foundation's also email writes that: > We will be providing assistance and support to you, whether you choose to spend out and close down your collective or continue your work through another 501(c)(3) organization or fiscal sponsor. and so we'll be contacting them as soon as possible to see if we can arrange a solution with just their help. But: in the mean time (and in case they *can't* help us, given the suddenness of this announcement) we need your help to find solutions--and we will probably need them urgently. If you have any help you can provide us, any services you can recommend, or anything that might help us quickly (and as painlessly as possible, given the short notice) transition to another service, that would be greatly appreciated. Fair warning that this will also likely derail the March financial update until we have a clearer picture of what we'll do and if OCF can help us going forward. Thanks, and hopefully we can resolve this situation without difficulty.

I don't want any lemmy.nsfw posts on my All tab. And there are so many instances

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).

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?

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.

#### 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 |

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.

#### 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

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.

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

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.

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

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!

#### 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

The community can be found at !opencourselectures@slrpnk.net. Are there any appropriate places under the beehaw umbrella?

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!

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.

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.

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

#### 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 |

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?

*Permanently deleted*

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. > >

[@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?

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.

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

*Permanently deleted*

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!

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.