Notices by Sharkey - Official Account (sharkey@shonk.social), page 2

Thanks @puniko@mk.absturztau.be for replying to some of the rumors :3

Explaining Rumors about Sharkey, circulating right now.

for those that are to lazy to read the entire thing.
here is a TLDR:

yes, the lead dev marie has quit fedi as a whole but this shouldn't affect the project, as we have active contributors, and the other Project Lead @Amelia@transfem.social is still fully involved in the project.

Long Explanation:

Due to the recent drama sounding TransFem.social and the other dramas before it, marie former lead dev, has decided to quit fedi as a whole this includes leaving the Sharkey Project but she will stay and help out till the next release which is upcoming soon, after that @Amelia@transfem.social (Project Lead) and the other sharkey contributors will continue sharkey as usual, we have spent alot of time over the last month expanding the dev team behind sharkey and inviting more contributors, so the project is not dead, nor at risk of dying and will be developed as usual in the foreseeable future

PS: @Amelia@transfem.social is very dedicated towards the Sharkey Project, and has been in charge of managing the project and the servers / accounts since the beginning.

The increased spam bots have show that misskey instances lack moderation tools to deal with massive spam campaigns, we will be looking into improving instance moderation tools in #sharkey, to maybe get them as powerful as Akkoma MRF or atleast close

@puniko@mk.absturztau.be @flit@akkoma.flitpix.net @Amelia@transfem.social well we are actually planning on some major mod tool changes

Everyone watch out, the spam bot situation has evolved, the bad actors are now actively engaging in doxxing people and using the info the send prank emails to business, and to send bomb threats to public institutions.

Note: is is mainly happening in japan, and law enforcement is already involved

Watch out for them Sharks

IMPORTANT SECURITY UPDATE, BOOST THIS POST
We have released a hot-fix that patches the recent Misskey vulnerability, that allows users to impersonate remote users
https://github.com/misskey-dev/misskey/security/advisories/GHSA-qqrm-9grj-6v32

Please update your instances to the latest stable release with the hotfix 2023.12.1 or if using develop to the lastest develop image or commit

thanks to @sugar@transfem.social for bringing this to our attention before everyone else

We are aware of the current Misskey vulnerability, and are working on getting an update out asap

@yassie_j@labyrinth.zone Im only into soft forks, sorry

Currently we are doing some reorganization of how sharkey development is done:

this includes but is not limited to:

1. Making all future dev discussions channels public, for increased transparency and community involvement
2. adding a new voting system, which will also be public, developers need to vote on new features before any major changes can be made, the vote needs to have a majority to pass, each member of the dev team can block a vote with valid reasoning, such as the feature increasing merging effort resulting in keeping up with misskey changes being hard
3. logging of inactivity of team members
4. Merge requests now require the approval of at least 2 devs, with a dev having the ability to block a merge request, if its a major feature it also requires a vote
5. new team members can now be voted in
6. Project Leads can no be elected in-case they go inactive or leave the team
7. Project Lead can be force fully replaced by a vote, in case a Project Lead, goes inactive for a while without any notice or they do something harmful to the project on purpose
8. a merge request can be merged without approval in emergency cases should an exploit happen that requires quick action, and non of the other team members are available a dev can merge security fixes without approval, this is only for upmost emergencys and should not happen

Other changes that will be done:
- reworking the contributing.md to be in english and have good instructions
- setting up crowdin for translations
- inviting more active contributors

Note: this is not final yet some things may change

We now have IRC channels on irc.libera.chat

#sharkey and #sharkey-support both are bridged to our discord

@puniko@mk.absturztau.be @esm@wetdry.world by replying to my post you have just agreed to be part of the testimonial on the new sharkey site /joke (there won't even be testimonials lol)

@puniko@mk.absturztau.be @esm@wetdry.world How are you liking da shonks so far?

This post is exclusive to :blahaj:Sharkey Blahaj subscribers

The FireFish.Social and joinfirefish.org servers are completly down and don't even respond to pings anymore, this means #firefish is officially dead, the servers no longer run, the git server still runs but seems to be run by a different person than kainoa

We're sad to see firefish go down like this, and we're especially sad about all the users who's data is now gone due to both major instances going down

while this is a major blow to a lot of people, please don't start harassing any one that was involved in the firefish project harassing people isn't going to help, we should see firefish as something to learn from to see what went wrong and prevent something like that happening in the future

and a note be added, Sharkey is not a firefish fork, and does not intent feature parity with it, Sharkey is a misskey softfork its supposed to update with misskey, unlike other fork we will not do big actions like rewrites

IMPORTANT UPDATE, BOOST THIS POST

A critical vulnerability has been found in Sharkey Twitter imports that can lead to arbitrary code execution, we urge all instance admins to IMMEDIATELY update or to disable Note Imports via roles for the time being, steps are being taken to prevent such events in the future.

NOTE:

this happened during our git migration please update your repos and docker images to the following to update to the latest version

Git Users:
run the following in the sharkey folder
git remote set-url origin https://activitypub.software/TransFem-org/Sharkey.git
then do a git pull
Docker Users:
replace the image: part of your docker compose with
image: registry.activitypub.software/transfem-org/sharkey:latest
Note replace latest with develop if u used that branch, also replace stable with latest if u used that tag

after this announcement was made the all affected docker images will be deleted to prevent users from using them and the old git repo will be redirected to the new one


Thanks to @ChaosKitsune@woem.men and @sugar@transfem.social for Reporting and Fixing the issue

We urge all users currently on our Sharkey Matrix rooms to leave and join the Discord

As the Matrix will be shutdown by 14th February due to lack of Matrix Mod tools and increased raids

Sharkey rooms might return on similar foss services in the future like xmpp tho that currently is up to debate

Sharkey has reached 3000 Total users :danceshark:

Don't let a Shark Obsessed @Amelia@transfem.social Name your Software, it won't end well!

Sharkey has reached 100 Active Servers
:shonks: