@silverpill Doesn't seem as if I get normal notifications, but that could be because I cannot seem to follow anyone. Also, would you mind walking me through how to install BloatFE? I have it compiled but I cannot figure out how to install it to my instance. If I choose to redirect to either 8080 or the onion, it boots me to mitrafe.
Notices by alenshore (anonymous6479@ryona.agency)
-
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Friday, 01-Dec-2023 05:59:42 JST 
alenshore
-
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Friday, 01-Dec-2023 05:59:42 JST
alenshore
@silverpill After changing to UTF-8 I appear to get mentions in my feed now. Testing to see if I get normal notifications.
-
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Wednesday, 29-Nov-2023 22:33:17 JST
alenshore
@silverpill I'll give it a try either today or over the weekend when I have more time to burn. -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Wednesday, 29-Nov-2023 22:33:15 JST
alenshore
@silverpill I was able to find the relay for ryona.agency, but not their onion link. Also the follow isn't automatic I am not sure if that is by design. Currently asking mint if they can see it.
failed to import profile relay@ryonagujouss6tp6tpuxdjonaetk24b4ksekvkktnwxutq2m3mhhu5qd.onion: error sending request for url (http://ryonagujouss6tp6tpuxdjonaetk24b4ksekvkktnwxutq2m3mhhu5qd.onion/.well-known/webfinger?resource=acct%3Arelay%40ryonagujouss6tp6tpuxdjonaetk24b4ksekvkktnwxutq2m3mhhu5qd.onion): error trying to connect: dns error: failed to lookup address information: Name does not resolve -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Wednesday, 29-Nov-2023 22:33:14 JST
alenshore
@silverpill So I am going to start a new post instead of editing for the 15th time. So it turns out the follows ARE going through, at least to me. This is both ways, though I don't show up on ryona for some reason.
That said, I am not getting new posts from my ryona account. Testing the mitra account. -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Wednesday, 29-Nov-2023 22:33:13 JST
alenshore
@silverpill Debug info for a follow from an onion address:
2023-11-28T17:14:27 mitra::mastodon_api::search::helpers [WARN] failed to import profile anyawnymous@rawrxd4mden7rmbobaftao3qjyxbrvj4rrooehkqxlqcsdtnnn2hndid.onion: error sending request for url (http://rawrxd4mden7rmbobaftao3qjyxbrvj4rrooehkqxlqcsdtnnn2hndid.onion/.well-known/webfinger?resource=acct%3Aanyawnymous%40rawrxd4mden7rmbobaftao3qjyxbrvj4rrooehkqxlqcsdtnnn2hndid.onion): error trying to connect: dns error: failed to lookup address information: Name does not resolve 2023-11-28T17:14:27 tokio_postgres::prepare [DEBUG] preparing query s22: SELECT post, actor_profile, ARRAY( SELECT media_attachment FROM media_attachment WHERE post_id = post.id ORDER BY media_attachment.created_at ) AS attachments, ARRAY( SELECT actor_profile FROM mention JOIN actor_profile ON mention.profile_id = actor_profile.id WHERE post_id = post.id ) AS mentions, ARRAY( SELECT tag.tag_name FROM tag JOIN post_tag ON post_tag.tag_id = tag.id WHERE post_tag.post_id = post.id ) AS tags, ARRAY( SELECT post_link.target_id FROM post_link WHERE post_link.source_id = post.id ) AS links, ARRAY( SELECT emoji FROM post_emoji JOIN emoji ON post_emoji.emoji_id = emoji.id WHERE post_emoji.post_id = post.id ) AS emojis FROM post JOIN actor_profile ON post.author_id = actor_profile.id WHERE post.id IN ( SELECT post.in_reply_to_id FROM post WHERE post.id = ANY($1) UNION ALL SELECT post.repost_of_id FROM post WHERE post.id = ANY($1) UNION ALL SELECT post_link.target_id FROM post_link WHERE post_link.source_id = ANY($1) UNION ALL SELECT post_link.target_id FROM post_link JOIN post ON (post.repost_of_id = post_link.source_id) WHERE post.id = ANY($1) ) 2023-11-28T17:14:27 tokio_postgres::query [DEBUG] executing statement s15 with parameters: [34127] 2023-11-28T17:14:27 tokio_postgres::query [DEBUG] executing statement s16 with parameters: [34125] 2023-11-28T17:14:27 tokio_postgres::query [DEBUG] executing statement s15 with parameters: [34171] 2023-11-28T17:14:27 tokio_postgres::query [DEBUG] executing statement s15 with parameters: [34172] 2023-11-28T17:14:27 tokio_postgres::query [DEBUG] executing statement s16 with parameters: [34170] 2023-11-28T17:14:27 tokio_postgres::query [DEBUG] executing statement s15 with parameters: [34082] 2023-11-28T17:14:27 tokio_postgres::query [DEBUG] executing statement s15 with parameters: [34434] 2023-11-28T17:14:27 tokio_postgres::query [DEBUG] executing statement s15 with parameters: [34435] 2023-11-28T17:14:27 tokio_postgres::query [DEBUG] executing statement s16 with parameters: [34433] 2023-11-28T17:14:27 tokio_postgres::query [DEBUG] executing statement s22 with parameters: [[]] 2023-11-28T17:14:27 tokio_postgres::prepare [DEBUG] preparing query s23: SELECT post_id FROM post_reaction WHERE author_id = $1 AND post_id = ANY($2) 2023-11-28T17:14:27 tokio_postgres::query [DEBUG] executing statement s23 with parameters: [018bebff-f677-dd27-344d-a5a2528079ae, []] 2023-11-28T17:14:27 tokio_postgres::prepare [DEBUG] preparing query s24: SELECT post.id FROM post WHERE post.id = ANY($2) AND EXISTS ( SELECT 1 FROM post AS repost WHERE repost.author_id = $1 AND repost.repost_of_id = post.id ) 2023-11-28T17:14:27 tokio_postgres::query [DEBUG] executing statement s24 with parameters: [018bebff-f677-dd27-344d-a5a2528079ae, []] 2023-11-28T17:14:27 actix_web::middleware::logger [INFO] GET /api/v2/search?q=%40anyawnymous%40rawrxd4mden7rmbobaftao3qjyxbrvj4rrooehkqxlqcsdtnnn2hndid.onion HTTP/1.1 : 200 : 127.0.0.1 2023-11-28T17:14:37 tokio_postgres::prepare [DEBUG] preparing query s25: UPDATE background_job SET job_status = $1, updated_at = CURRENT_TIMESTAMP WHERE id IN ( SELECT id FROM background_job WHERE job_type = $2 AND scheduled_for < CURRENT_TIMESTAMP AND ( -- queued job_status = $3 -- running OR job_status = $1 AND updated_at < CURRENT_TIMESTAMP - $5::text::interval ) ORDER BY -- queued jobs first job_status ASC, scheduled_for ASC LIMIT $4 ) RETURNING background_job 2023-11-28T17:16:13 actix_web::middleware::logger [INFO] GET /api/v2/search?q=%40relay%40http%3A%2F%2Frawrxd4mden7rmbobaftao3qjyxbrvj4rrooehkqxlqcsdtnnn2hndid.onion HTTP/1.1 : 200 : 127.0.0.1 2023-11-28T17:16:13 tokio_postgres::prepare [DEBUG] preparing query s56: SELECT user_account, actor_profile FROM oauth_token JOIN user_account ON oauth_token.owner_id = user_account.id JOIN actor_profile ON user_account.id = actor_profile.id WHERE oauth_token.token = $1 AND oauth_token.expires_at > CURRENT_TIMESTAMP 2023-11-28T17:16:13 tokio_postgres::query [DEBUG] executing statement s56 with parameters: ["M_SZCjLVgeA_iEeAKZCDyDHNzxI"] 2023-11-28T17:16:13 tokio_postgres::prepare [DEBUG] preparing query s57: SELECT timeline_marker FROM timeline_marker WHERE user_id = $1 AND timeline = $2 2023-11-28T17:16:13 tokio_postgres::query [DEBUG] executing statement s57 with parameters: [018bebff-f677-dd27-344d-a5a2528079ae, Notifications] 2023-11-28T17:16:13 actix_web::middleware::logger [INFO] GET /api/v1/markers?timeline%5B%5D=notifications HTTP/1.1 : 200 : 127.0.0.1Either way I get no results.
-
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Wednesday, 29-Nov-2023 01:42:05 JST
alenshore
@silverpill I can login now. Going to try to set it up and see how it works. -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Wednesday, 29-Nov-2023 01:42:04 JST
alenshore
@silverpill Okay so I am stumped. How do I view the public timeline? There is one right? I've looked all over the documentation and my own test instance and I cannot find it for the life of me. Though federation suggests that, yes, there is.
Also where's the config to add instances to federate with? Or does that happen automatically? I know on pleroma you have to add the server's relay, and the documentation suggests a similar setup is required here.
Also, for a Tor-only instance attempting to talk to non-tor instances, do I need nginx set up? -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Thursday, 23-Nov-2023 11:34:15 JST
alenshore
@silverpill Indeed. I would always access myself from localhost:port because it's faster, but eventually I will move to a more advanced setup. This is mostly for testing and time. -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Wednesday, 22-Nov-2023 06:54:50 JST
alenshore
@silverpill @mitra >Does request come from 127.0.0.1 when you run it as an onion service?
Yeah. On the web fe it says bad request. -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Wednesday, 22-Nov-2023 06:45:39 JST
alenshore
@silverpill @mitra >I'd appreciate if you tell me what parts were difficult to follow I'm sure it really is NOT that hard to follow, but the documentation you have now mostly expects you to already know what most of the options for an instance on any other software (pleroma for example) does.
For example, it says the storage_dir in the config, but that could mean just about anything. It obviously means what it says on the tin, but if you want to change it's default because you're autistic (like myself) you need to already know what will, generally, be put there, or boot it up. I booted it. It would also be nice if a slightly larger line could be drawn between it and web_client_dir, especially for those of us with minor knowledge in other software. I keep reading it as "static dir" and "other dir" and my brain was having a hard time making the connections.
Obviously I am retarded, so no need to work around my retardation. Still if there had been a minor config doc for example just giving a small overview of the basic options it would have saved me headaches.
-
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Tuesday, 21-Nov-2023 09:12:10 JST
alenshore
@mitra I was able to get mitra installed and at least at first glance everything seems fine. You really need better and more in-depth documentation btw.
However when I attempt to log into my instance using localhost:8383 I get the following errors:
2023-11-20T01:21:49 actix_cors::middleware [DEBUG] origin validation failed; inner service is not called 2023-11-20T01:21:49 actix_web::middleware::logger [DEBUG] Error in response: OriginNotAllowed 2023-11-20T01:21:49 actix_web::middleware::logger [INFO] POST /oauth/token HTTP/1.1 : 400 : 127.0.0.1How do I change the allowed domains list?
-
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 22:27:48 JST
alenshore
@mint @dcc Seems to be same problem as before. I can see their relay but not users. And I believe your instance was also timing out on me. Can you tell me the exact nature of the issue so I can add it to my bug report? Seems like an issue with pleroma proper. -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 22:23:00 JST
alenshore
@mint @dcc That one was my bad. Was trying to use https:// on an onion link. The relay sticks now. -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 22:19:46 JST
alenshore
@mint @dcc I'm still winding down. I really should just hit the sack. But I figured I'd try to add some more relays. FSE's relay was added (though not federating) however rawrs gives a forwarding error. Figured I should mention it. -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:57:26 JST
alenshore
@mint @dcc Oh, one last thing I keep getting these warnings. I am not sure they mean anything:
[warning] Can't find LRDD template in "https://rawrxd4mden7rmbobaftao3qjyxbrvj4rrooehkqxlqcsdtnnn2hndid.onion/.well-known/host-meta": {:error, {:tls_alert, {:unknown_ca, 'TLS client: In state wait_cert_cr at ssl_handshake.erl:2111 generated CLIENT ALERT: Fatal - Unknown CA\n'}}} -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:57:26 JST
alenshore
@mint @dcc Alrighty. gn -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:54:13 JST
alenshore
@dcc @mint I gotta be honest, I have to end on a high note, and I should have been asleep hours ago. I am going to shove off for now. I'll get back to you ASAP if you figure anything else out. Should I leave the instance running or can I shut it off? -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:52:30 JST
alenshore
@dcc @mint Also still nothing in my known timeline, but a huge step in the right direction from where I was. -
Embed this notice
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:50:30 JST
alenshore
@mint @dcc As expected, the lag is immense, but the posts are federating both ways now! yayayayayayaya!
All GNU social JP content and data are available under the