Saltar a contenido principal


Unable to follow anyone from Threads.net


Whenever I attempt to add any users from Threads.net to my personal instance, the system is unable to find them despite of not being in any block lists. Is this a bug, intentional behavior, or do I need to configure something on my side?

!Friendica Admins

Friendica Admins reshared this.

in reply to Carlos Solís

@Carlos Solís At the moment it is only possible for Threads users from the USA, Canada and Japan to share their posts with the Fediverse. To do this, users must also enable this in their settings.
If they have done this, only their posts will be sent to the Fediverse. Interaction with the users is only possible via likes, because only these are displayed to them. Any replies from the Fediverse are not yet shown to the thread users.
in reply to OldKid

@OldKid I'm aware of the opt-in nature of federation in Threads, but I'm not even able to follow known opted-in users such as, say, barackobama@threads.net .

Friendica Admins reshared this.

in reply to Carlos Solís

@OldKid For instance, the probe output I get for that account is:

Array
(
    [name] => https://www.threads.net/@barackobama
    [given_name] => 
    [family_name] => 
    [nick] => https://www.threads.net/@barackobama
    [guid] => 
    [url] => https://www.threads.net/@barackobama
    [addr] => 
    [alias] => 
    [photo] => https://hub.azkware.net/images/person-300.jpg
    [photo_medium] => 
    [photo_small] => 
    [header] => 
    [account-type] => 
    [community] => 
    [keywords] => 
    [location] => 
    [about] => 
    [xmpp] => 
    [matrix] => 
    [hide] => 
    [batch] => 
    [notify] => 
    [poll] => 
    [request] => 
    [confirm] => 
    [subscribe] => 
    [poco] => 
    [following] => 
    [followers] => 
    [inbox] => 
    [outbox] => 
    [sharedinbox] => 
    [priority] => 0
    [network] => unkn
    [pubkey] => 
    [manually-approve] => 
    [baseurl] => https://www.threads.net
    [gsid] => 835
    [networks] => Array
        (
        )

)

Friendica Admins reshared this.

in reply to Carlos Solís

I don't think so. It's rather a communication problem between your node and threads.net.
in reply to Steffen K9 🐰

@Steffen K9 🐰 @OldKid Yeah I've been having odd problems with a few nodes, for example I'm incapable of adding new relays with the "console relay add" command

Friendica Admins reshared this.

in reply to Carlos Solís

@Carlos Solís which account/server are you trying with? Are you on the stable branch?

It didn't work for me in the past to follow threads users, but barackobama@threads.net just now worked from @utzer [Pleroma] and from @utzer [Friendica] (this account here) as well.

Esta entrada fue editada (hace 1 mes)
in reply to utzer [Friendica]

@utzer [Friendica] This same account and server I'm using to post this message are the ones I'm using to attempt following this user. I'm currently using the latest development branch as pulled from Git.

Friendica Admins reshared this.

in reply to Carlos Solís

@Carlos Solís are you aware that hub.azkware.net/friendica is not reachable? If this is intended, are you restricting access to some endpoints that are needed for AP as well?
in reply to utzer [Friendica]

@utzer [Friendica] I'll have to check why is that the case - I use @YunoHost to self-host my instance, so maybe it's an error on their side of the configuration?

Friendica Admins reshared this.

in reply to utzer [Friendica]

@utzer [Friendica] My #nginx conf for the subdomain goes like this:

location / {

  alias /var/www/friendica/;

  if (!-e $request_filename) {
    rewrite ^(.*)$ /index.php?pagename=$1;
  }

  #allow uploads up to 50MB in size
  client_max_body_size 50M;
  client_body_buffer_size 128k;

  #Default indexes and catch-all
  index index.php;

  # make sure webfinger and other well known services aren't blocked
  # by denying dot files and rewrite request to the front controller
  location ^~ /.well-known/ {
    allow all;
    if (!-e $request_filename) {
      rewrite ^(.*)$ /index.php?pagename=$1;
    }
  }

  include mime.types;

  # block these file types
  location ~* \.(tpl|md|tgz|log|out)$ {
    deny all;
  }

  #Execute and serve PHP files
  location ~* \.php$ {
    fastcgi_split_path_info ^(.+?\.php)(/.*)$;
    try_files $uri =404;
    fastcgi_pass unix:/var/run/php/php8.2-fpm-friendica.sock;
    fastcgi_index index.php;
    include fastcgi_params;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
  }

  # deny access to all dot files
  location ~ /\. {
    deny all;
  }

  #Include SSOWAT user panel.
  include conf.d/yunohost_panel.conf.inc;
}

Friendica Admins reshared this.

in reply to Carlos Solís

@Carlos Solís I have no idea, just two things that you could try. Just guesses.

  1. This setting, if it is on "modern" then set it to intermediate.
    /yunohost/admin/#/tools/settings/security

Then try again.

  1. Disable this user portal layover that is shown.
    /yunohost/admin/#/tools/settings/misc

Try again.

Do this one by one. Just had those two cause some problem before.

in reply to utzer [Friendica]

@Carlos Solís and you can also try to look what happens in the nginx log tail -F /var/log/nginx/hub.azkware.net-error.log when you try to open hub.azkware.net/friendica
in reply to utzer [Friendica]

@utzer [Friendica] I can see plenty of errors regarding that one:

2024/04/09 17:48:18 [error] 1063466#1063466: *21256221 directory index of "/var/www/friendica/friendica/" is forbidden, client: 141.95.205.46, server: hub.azkware.net, request: "GET /friendica/ HTTP/1.1", host: "hub.azkware.net"

So I went to investigate and found I should add a rule to rewrite the dangling "/friendica", like this:

location ^~ /friendica {
    rewrite ^/friendica(.*) /$1 break;
}

And now I don't seem to be getting any more errors for now. Hopefully this works!

Friendica Admins reshared this.

in reply to Carlos Solís

@Carlos Solís but still not right, it should show this:
social.yl.ms/friendica

Edit: See my server does not add the / in the end, that seems to be the difference. (Not Yunohost on my side)

Esta entrada fue editada (hace 1 mes)
in reply to utzer [Friendica]

@utzer [Friendica] Yeah I'm seeing that. Is there some way to properly pass the parameter? Looks like it's using some sort of default folder and assumes there's a subdirectory

Friendica Admins reshared this.

in reply to Carlos Solís

@Carlos Solís I wonder why the rewrite rule is needed? It looks very strange to me. Have you followed some tutorial?

Here are two #StackOverflow examples:
stackoverflow.com/questions/66…

stackoverflow.com/questions/12…

It looks like try_files is your way to go?

Esta entrada fue editada (hace 1 mes)
in reply to Roland Häder

@Carlos Solís The /.well-known/host-meta can now be downloaded, but still /friendica (without a trailing slash!) isn't working. It is still redirecting to a 404 page. Please reset your virtual-host configuration and try again. I guess there is still an invalid entry in it.

Here is what I was able to download:

<?xml version="1.0"?>
<XRD xmlns:hm="http://host-meta.net/xrd/1.0" xmlns:mk="http://salmon-protocol.org/ns/magic-key" xmlns="http://docs.oasis-open.org/ns/xri/xrd-1.0">
  <hm:Host>hub.azkware.net</hm:Host>
  <link rel="lrdd" type="application/xrd+xml" template="https://hub.azkware.net/xrd?uri={uri}"/>
  <link rel="lrdd" type="application/json" template="https://hub.azkware.net/.well-known/webfinger?resource={uri}"/>
  <link rel="acct-mgmt" href="https://hub.azkware.net/amcd"/>
  <link rel="http://services.mozilla.com/amcd/0.1" href="https://hub.azkware.net/amcd"/>
  <Property type="http://salmon-protocol.org/ns/magic-key" mk:key_id="1">RSA.zddpGx5nd20Pa8I-azc0PffEYykQkOdTjRX8V079CslHYeopKCs11aD44h0osS4sbIvME6E8_iesfW4aise9dSHhvsYLWVXJHf0jeDDHy9I5GVPqNZtHf_3KEbFhQIuz2W4n8m5vW51Y9XA86aIpVprtDyz8y_0aR4kxta_fqa0.AQAB</Property>
</XRD>
in reply to Roland Häder

@Roland Häder I'm on it - please check my current configuration:
hub.azkware.net/display/6e2ecb…


@utzer [Friendica] My #nginx conf for the subdomain goes like this:
location / {

  alias /var/www/friendica/;

  if (!-e $request_filename) {
    rewrite ^(.*)$ /index.php?pagename=$1;
  }

  #allow uploads up to 50MB in size
  client_max_body_size 50M;
  client_body_buffer_size 128k;

  #Default indexes and catch-all
  index index.php;

  # make sure webfinger and other well known services aren't blocked
  # by denying dot files and rewrite request to the front controller
  location ^~ /.well-known/ {
    allow all;
    if (!-e $request_filename) {
      rewrite ^(.*)$ /index.php?pagename=$1;
    }
  }

  include mime.types;

  # block these file types
  location ~* \.(tpl|md|tgz|log|out)$ {
    deny all;
  }

  #Execute and serve PHP files
  location ~* \.php$ {
    fastcgi_split_path_info ^(.+?\.php)(/.*)$;
    try_files $uri =404;
    fastcgi_pass unix:/var/run/php/php8.2-fpm-friendica.sock;
    fastcgi_index index.php;
    include fastcgi_params;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
  }

  # deny access to all dot files
  location ~ /\. {
    deny all;
  }

  #Include SSOWAT user panel.
  include conf.d/yunohost_panel.conf.inc;
}

Friendica Admins reshared this.

in reply to Carlos Solís

@Carlos Solís Rewrite the first one to the try_files version (without any if block) and remove the /.well-klnown/ one. It should be covered as well by the try_files line.
in reply to utzer [Friendica]

@utzer [Friendica] Thanks for the tip, but both were already set as such after I had a minor problem with SearX.

Friendica Admins reshared this.

in reply to Carlos Solís

@Carlos Solís that was the one problem I changed the settings for. :-P

If you open an issue at Friendica for Yunohost I'd love to get a link or a ping.

Esta entrada fue editada (hace 1 mes)
in reply to utzer [Friendica]

@utzer [Friendica] Sure, I'll post the issue as soon as I find the proper fix on the nginx side.

Friendica Admins reshared this.

in reply to Carlos Solís

@Carlos Solís Your instance has a lot of trouble: hub.azkware.net/friendica/ gives back a 500 error. I guess it is due to this errors? Your instance doesn't block any domains, according to API.
in reply to Roland Häder

@Carlos Solís And your like is not received here. I suspect that your instance has some trouble.
in reply to Carlos Solís

Every time you perform some request at Threads, Threads will try to resolve the account that requested the content. Possibly you block their requests. Have a look into your webserver's access.log for entries with the user agent "facebookexternalua".