@FrailLeaf @waifu No, simply im tired of some inconsistencies in the way pleroma is configured and the fact that after a big upgrade (bump from 2.1 to 2.5) many things broke in my instance
peep this @FrailLeaf @waifu Is this an akkoma fork? what difference have with normal akkoma?
@elliemortem @waifu yeah its a fork, it gets rid of a tonne of lock down "features" akkoma introduced.
@elliemortem one of the nasty works from akkoma dev reverted: https://git.froth.zone/sam/pleroma/commit/b460c3904a6700ebf7708233f5336e729947ebc8
@FrailLeaf @elliemortem @sam @waifu that's pretty cool. maybe I should move asbestos.cafe to it, it's a bit stupid to use a fork as petty as that
@meso @elliemortem @sam @waifu yeah imagine not passing block messages to MRF because "it perpetuates bad behavior" lmao ok, mr fediverse CEO
@FrailLeaf @elliemortem @sam @waifu in general akkoma's developer is not very friendly. i understand why that's probably the case but like 
maybe don't say "skill issue" when someone asks about a problem with your software. this is why I actually like alex gleason more even if he's whiny about pleroma banning him from gitlab and transphobic. he's a friendly guy, even to trans people. he's helpful
maybe don't say "skill issue" when someone asks about a problem with your software. this is why I actually like alex gleason more even if he's whiny about pleroma banning him from gitlab and transphobic. he's a friendly guy, even to trans people. he's helpful@meso @elliemortem @sam @waifu I'd fuck alex gleasonoid too.
>"skill issue" when someone asks about a problem with your software
bruh he says that? that's messed up
>public account for all akkoma-related dev stuff/releases/whatever else
>notifications probably aren't actively monitored so if you need me, raise a git issue or message the IRC
picrel.
imagine having a fediverse account only to tell people that you won't interact with them and have them go through hoops to be able to talk to you. Sukkoma sisters, really?
<
oh ok, I am running your fediverse software and instead of talking to your over the fediverse, i have to talk to you over git/irc ? yeah cool, let me NOT do that and use a sensible alternative.
>"skill issue" when someone asks about a problem with your software
bruh he says that? that's messed up
>public account for all akkoma-related dev stuff/releases/whatever else
>notifications probably aren't actively monitored so if you need me, raise a git issue or message the IRC
picrel.
imagine having a fediverse account only to tell people that you won't interact with them and have them go through hoops to be able to talk to you. Sukkoma sisters, really?
<
oh ok, I am running your fediverse software and instead of talking to your over the fediverse, i have to talk to you over git/irc ? yeah cool, let me NOT do that and use a sensible alternative.
forgot to attach image
@FrailLeaf @meso @sam I compiled sam's pleroma but still refuses to connect to the database, I can only say that progresql is dumb
what kind of connection refusal is it?@FrailLeaf Its say its a timeout error, no idea how to interpret this or why it is failing on akkoma
11:57:52.399 [error] #PID<0.1811.0> running Pleroma.Web.Endpoint (connection #PID<0.1810.0>, stream id 1) terminated
Server: bunny.cafe:80 (http)
Request: GET /api/v1/timelines/home?since_id=ASCXfR9jYJ8gv1T7gm&with_muted=false&limit=20
** (exit) an exception was raised:
** (DBConnection.ConnectionError) tcp recv: closed (the connection was closed by the pool, possibly due to a timeout or because the pool has been terminated)
(ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1
(ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:828: Ecto.Adapters.SQL.execute/6
(ecto 3.9.4) lib/ecto/repo/queryable.ex:229: Ecto.Repo.Queryable.execute/4
(ecto 3.9.4) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
(pleroma 3.5.0-1865-gf48068b8-froth-akkoma) lib/pleroma/web/mastodon_api/views/status_view.ex:108: Pleroma.Web.MastodonAPI.StatusView.render/2
(phoenix_view 2.0.2) lib/phoenix_view.ex:557: Phoenix.View.render_to_iodata/3
(phoenix 1.6.15) lib/phoenix/controller.ex:772: Phoenix.Controller.render_and_send/4
(pleroma 3.5.0-1865-gf48068b8-froth-akkoma) lib/pleroma/web/mastodon_api/controllers/timeline_controller.ex:5: Pleroma.Web.MastodonAPI.TimelineController.action/2
11:57:52.615 [error] Postgrex.Protocol (#PID<0.1408.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.1822.0> timed out because it queued and checked out the connection for longer than 15000ms
#PID<0.1822.0> was at location:
:prim_inet.recv0/3
(postgrex 0.16.5) lib/postgrex/protocol.ex:3171: Postgrex.Protocol.msg_recv/4
(postgrex 0.16.5) lib/postgrex/protocol.ex:2201: Postgrex.Protocol.recv_bind/3
(postgrex 0.16.5) lib/postgrex/protocol.ex:2056: Postgrex.Protocol.bind_execute_close/4
(db_connection 2.4.3) lib/db_connection/holder.ex:354: DBConnection.Holder.holder_apply/4
(db_connection 2.4.3) lib/db_connection.ex:1413: DBConnection.run_execute/5
(db_connection 2.4.3) lib/db_connection.ex:1508: DBConnection.run/6
(db_connection 2.4.3) lib/db_connection.ex:644: DBConnection.parsed_prepare_execute/5@elliemortem @FrailLeaf did you do the migrations? I believe akkoma and plemora don't have the exact same db
@waifu @FrailLeaf I tried once and probably will need to try again, but my database is like 25 gb so its a lot of time to dump and import
- replies
- 1
- announces
- 0
- likes
- 1
@elliemortem @waifu let us hope it is not over for you
@meso @elliemortem @FrailLeaf @waifu I merge upstream yes, consistent no I do it basically both whenever I feel like it and whenever I can