GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Untitled attachment

Download link

Notices where this attachment appears

  1. Embed this notice
    fedi-block-api notifier (fba@ryona.agency)'s status on Sunday, 28-Jul-2024 22:35:24 JST fedi-block-api notifier fedi-block-api notifier
    mastodon.raykoworld.com has blocked the following instances:

    stop.voring.me for "Vanished"
    In conversation about 10 months ago from ryona.agency permalink
  2. Embed this notice
    fedi-block-api notifier (fba@ryona.agency)'s status on Monday, 10-Jun-2024 11:25:03 JST fedi-block-api notifier fedi-block-api notifier
    hachyderm.io has blocked the following instances:

    stop.voring.me with unspecified reason
    In conversation about a year ago from ryona.agency permalink
  3. Embed this notice
    fedi-block-api notifier (fba@ryona.agency)'s status on Friday, 01-Mar-2024 04:30:27 JST fedi-block-api notifier fedi-block-api notifier
    milk.choco.ink has blocked the following instances:

    9ineverse.com with unspecified reason
    stop.voring.me with unspecified reason
    In conversation about a year ago from ryona.agency permalink
  4. Embed this notice
    :verified_2:防空識別區𝒔𝒐𝒄𝟶 (adiz@soc0.outrnat.nl)'s status on Friday, 09-Feb-2024 15:09:34 JST :verified_2:防空識別區𝒔𝒐𝒄𝟶 :verified_2:防空識別區𝒔𝒐𝒄𝟶
    in reply to

    freespeechextremist.com, djsumdog.com, mk.nya.pub, pl.ericaftereric.top, waifuism.life, mastodontosharkey.tests.joinsharkey.org, akko.hollow.capital, mocha.hoto.rocks, vee.seedy.gq, stop.voring.me, comms.thedigitallancabin.net, mk.plasmatrap.com, levelfivegyattrizzlivvydunnerizzingupbabygronkicespice.whatthedogdoinskibiditoiletinreallifeonlyinohio.lol, pl.nulled.red, pleroma.comfysnug.space, nyanide.alterracloud.com are all down with approximately 500+ delayed jobs each.

    In conversation about a year ago from soc0.outrnat.nl permalink
  5. Embed this notice
    fedi-block-api notifier (fba@ryona.agency)'s status on Tuesday, 16-Jan-2024 10:21:58 JST fedi-block-api notifier fedi-block-api notifier
    bungle.online has blocked the following instances:

    stop.voring.me with unspecified reason
    In conversation Tuesday, 16-Jan-2024 10:21:58 JST from ryona.agency permalink
  6. Embed this notice
    Amelia (Amy) It's sis not cis :verifiedtrans: (amelia@transfem.social)'s status on Sunday, 31-Dec-2023 03:55:37 JST Amelia (Amy) It's sis not cis :verifiedtrans: Amelia (Amy) It's sis not cis :verifiedtrans:

    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

    RE: https://catodon.social/notes/9nvp68a5a10zrdi2

    In conversation Sunday, 31-Dec-2023 03:55:37 JST from transfem.social permalink
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.