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
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
@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)
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
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
With #firefish sadly turning into a seemingly dead project all we can do is learn from its mistakes, as such our project has 2 project leads, while being a soft-fork of Misskey drastically decreasing work required to maintain #sharkey, we will also try to involve our community more and more. so even in the in the unlikely event both project leads go MIA the community can still keep the project alive by itself.
After an entire month of waiting its finally time for a new Sharkey release and happy new year :blahaj:
this release includes many long requested features such as: note detailed view live updating, revamped threads / note ui, bubble timeline, custom post length and many more
The entire Sharkey team wishes you all a Happy New Year 🎆
NOTE due to the git migration you will need to update the repo / docker images please check the linked article for more info also there have been a few config changes that require updating
Sharkey is an Misskey fork following upstream changes when possible, with added features!It has features such as:* Federated Post editing* MastodonAPI* UI Improvements* Federated Profile Backgrounds* Federated Music Status via ListenbrainzIt is possible to migrate to Sharkey from:* FireFish (Pre ScyllaDB migration)* IceShrimp* MisskeyFollow the Devs:@Marie@transfem.social@Amelia@transfem.social#Sharkey #FOSS #OpenSource #Docker #Misskey #Fediverse