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

Embed this notice
Sharkey - Official Account (sharkey@shonk.social)'s status on Monday, 01-Jan-2024 19:04:04 JST Sharkey - Official Account

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.

RE: https://transfem.social/notes/9nvrcuc33g9p0g4g
In conversation Monday, 01-Jan-2024 19:04:04 JST from shonk.social permalink
Attachments
1. Domain not in remote thumbnail source whitelist: transfem.social
  
  Amelia (Amy) It's sis not cis (@Amelia)
  
  Welp the bomb has been dropped, former #firefish team members basically telling us what we suspected is true firefish is basicly dead, since this is out now i might as well talk about some firefish things even tho i hate this happening i don't feel like i should continue to stay quite on some of the issues, as part of my promise to the firefish devs i've talked to i will not mention some things that i know of but will tell my personal experiences with the project and why i think the project is unlikely to recover. well lets start of with the apparent issue, firefish is kainoa's project and as such he is fully in charge of the project, the issue is that firefish has been seemingly developed in a way that's basically right out of the Portal Quotes book > "I'll be honest, we're throwing science at the wall here to see what sticks. No idea what it'll do. Probably nothing" this Quote perfectly describes what firefish has been doing over the last releases, stuff like rust was added never to be touched again, scylladb was hyped and worked on (apparently because discord uses it?) just to be basically scrapped, and rewrite in bun was planned? the attitude was basically adding stuff and making changes without fixing the underlying issues, firefish suffers from alot and by alot i mean a fuck ton of technical issues these won't magically be solved by rewriting it, or changing db sure rewrittes and switching to a better db can help (scylladb is not better for a thing like firefish btw) but that's just putting duck tape on the issue, instead a focus should have been to work on the underlying issues fixing whats causing the issues, like the monster db querys not to mention the fact that some things like scylladb were apparently done even tho multiple firefish devs adviced against it (not a firefish dev can't confirm this but ive been told such) but also as we have seen firefish is extremely dependent on Kainoa being there, without him being there not much can be done on the firefish side of the team which is also very bad a project should not collapse as hard as firefish because the main dev is missing for multiple weeks, thats why in the ideal case u have multiple project leads but even if kainoa comes back and everything returns to normal for a bit if firefish does not majorly change their attitude towards development and organization the project will just continue to crash straight into a wall that said don't start harassing any of the firefish devs or even kainoa firefish is a foss hobby project and projects come and go as of writing this post both main firefish instances firefish.social and stop.voring.me are still down or up but don't federate and|or otherwise unusable EDIT: if you are currently running firefish its highly recommended u consider migrating to either Sharkey, Iceshrimp or Catodon, ofc im going to recommend #sharkey but please do your own research RN: Ugh, I really tried to stay out of #fediverse drama but I guess I have to say a few things. Most of you know me as a #firefish core team member, so I think I owe it to the admins of almost 500 firefish servers out there and to the almost 5000 members of firefish.social. So, yeah, if you haven't noticed, things aren't looking good for firefish. Its owner, Kainoa, has practically abandoned the project, which had its last stable release out on July. My last message to them was a week ago, and I haven't heard back since. Firefish.social, besides the other severe technical problems it's had due to mismanagement in the last few months, now also has serious federation issues. I hope Kainoa is well irl, but this is irresponsible and unacceptable. I hear some of you saying "but you're in the core team too, don't try to put the blame elsewhere!". So I have to explain what being a core team member in firefish meant. Kainoa invited me, Namekuji and a few others to be part of the "core team", but kept all decisions and responsibilities. We didn't co-own this. We never shared donations. We were just volunteers, who were honestly trying to make it a great project. This didn't work well due to concentration of power to one person, who didn't keep their promises. I don't mean to be harsh to Kainoa, I mean we knew they were only 19 when they started the project. Still, it's a bummer to anyone who chose to trust and support Firefish. This includes myself. I don't know if it's early to consider firefish a dead project, but it sure seems like that for a few months now. Maybe it can be resurrected, idk. It's all up to Kainoa. In the meantime, Namekuji and I are starting #Catodon, which will have some differences with Firefish, and will include many changes I had discussed with Kainoa but were never implemented. If you decide to stick with us, we promise to be serious about this. I strongly believe in the fediverse and its potential, and I want to build a great platform for it. This was my goal when I chose to be involved in Calckey/Firefish. It's still my goal with Catodon, only this time I can stand behind it 100%, as the project will be co-managed by Namekuji and me. If Firefish left you with a bitter aftertaste, we hope we can build a better relationship and prove ourselves worthy of your trust. Catodon will go public in a matter of days, possibly even hours. We'll have more to say about its direction then. In the meantime, I just wanted to share my apologies for any inconvenience regarding Firefish, as I'm still technically a core team member, whatever that means. But frankly, I tried so hard to make things go differently - but there's only so much you can do when it's someone else's project. I'm really sorry for how things went. But this is not the end of the fedi journey for me. I'm super excited about the chance to do some things right this time with Catodon. Life goes on, I guess! Hope to see you soon on our #codeberg repo, so we can start a new creative adventure together =) :catodon: xx
Embed this notice
Sharkey - Official Account (sharkey@shonk.social)'s status on Monday, 01-Jan-2024 07:59:59 JST Sharkey - Official Account

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

Read more at:
https://transfem.org/2023/12/31/sharkey-release-2023-12-0

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
In conversation Monday, 01-Jan-2024 07:59:59 JST from shonk.social permalink
Attachments
1. Screenshot of the Many UI changes done in this sharkey release
  https://cdn.shonk.social/files/3223e3d3-8d43-4790-9e26-58aad74d2d5c.webp
2. Domain not in remote thumbnail source whitelist: transfem.org
  
  Sharkey Release 2023.12.0
  
  from Emmi
Embed this notice
Sharkey - Official Account (sharkey@shonk.social)'s status on Sunday, 31-Dec-2023 14:52:45 JST Sharkey - Official Account

As part of our commitment to the #fedipact we will now be blocking every instance /joke

RE: https://tech.lgbt/users/FediPact/statuses/111670512392796918
In conversation Sunday, 31-Dec-2023 14:52:45 JST from shonk.social permalink
Attachments
1. No result found on File_thumbnail lookup.
  
  fedipact.online (@FediPact@tech.lgbt)
  
  from fedipact.online
  
  been seeing a lotta posts lately that're like "OMFG THESE FEDIPACT PEOPLE ARE BLOCKING EVERY INSTANCE THAT FEDERATES WITH THREADS" no. we're not. nothing anywhere on https://fedipact.online says anything about that lmao i have seen exactly one example of someone planning to do this, and that's it it's being blown ridiculously outta proportion #FediPact #meta #threads
Embed this notice
Sharkey - Official Account (sharkey@shonk.social)'s status on Sunday, 31-Dec-2023 05:23:22 JST Sharkey - Official Account
- Puniko ?
- Volpeon :drgn_verified: :drgn_smol:
@volpeon@is-a.wyvern.rip @puniko@mk.absturztau.be Sharkey's misskey fork: wait no

In conversation Sunday, 31-Dec-2023 05:23:22 JST from shonk.social permalink
Embed this notice
Sharkey - Official Account (sharkey@shonk.social)'s status on Wednesday, 27-Dec-2023 01:06:10 JST Sharkey - Official Account

When you've been using Sharkey to much
In conversation Wednesday, 27-Dec-2023 01:06:10 JST from shonk.social permalink
Attachments
1. Untitled attachment
Embed this notice
Sharkey - Official Account (sharkey@shonk.social)'s status on Thursday, 14-Dec-2023 04:16:10 JST Sharkey - Official Account
in reply to
- Tim Chambers
@tchambers@indieweb.social We use misskey quote posts yeah, but sharkey can also handle incoming qoute posts from software like fedibird

In conversation Thursday, 14-Dec-2023 04:16:10 JST from shonk.social permalink
Embed this notice
Sharkey - Official Account (sharkey@shonk.social)'s status on Thursday, 14-Dec-2023 01:46:45 JST Sharkey - Official Account

Reintroduction
#introduction #reintroduction
This is the Offical account of the #Sharkey project.

bringing you random shark facts since 2023
[looks at script: oops wrong script...]

bringing you a Misskey fork that follows upstream when ever possible with added features such as federated post editing, mastodon api, federated profile backgrounds, federated music status via listenbrainz and more since 2023.

this account is used for updates regarding #Sharkey aswell as support but also may occasionally post some random facts about Sharks Sharkey, this account will also be used for Information regarding https://shonk.social
In conversation Thursday, 14-Dec-2023 01:46:45 JST from shonk.social permalink
Attachments
1. Domain not in remote thumbnail source whitelist: cdn.shonk.social
  
  Shonk Social
  
  Welcome to the Flagship Sharkey Instance Shonk Social It's a general purpose instance for Sharkey
Embed this notice
Sharkey - Official Account (sharkey@shonk.social)'s status on Saturday, 02-Dec-2023 05:06:45 JST Sharkey - Official Account
in reply to
- Puniko ?
- Amelia (Amy) It's sis not cis :verifiedtrans:
@Amelia@transfem.social @hope@mk.absturztau.be @puniko@mk.absturztau.be
THERE IS NO ESCAPE:ElainaChristmas:

In conversation Saturday, 02-Dec-2023 05:06:45 JST from gnusocial.jp permalink

After

Public

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

User actions

Following 0

Followers 0

Groups 0

Statistics

Feeds