we discovered this set the other day by olivvybee (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 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

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

tl;dr: Beehaw has moved over to Open Collective Europe Foundation, please direct your donations there 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 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 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. 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. Slight difference though: @jarfil@beehaw.org 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?

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.

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

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 about content issues, server instability and server errors. Here are the days of no support requested. We have improved the uptime and responsiveness 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.

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

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

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.

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

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.

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

On Beehaw there are a few tldr bots from other instances. I present Beehaws own summarizing bot 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

@support Yesterday I saw this post 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 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?