Notices by Luca Hammer (luca@vis.social)

@forteller Should be fixed now.

@lakoja @ProgGrrl Correct. Hashtag search on instances only shows you posts that are known to the instance (because of follow, boost or URL search).

When you are on a smaller instance, you won't find many posts. Because of that I build #mastovue years ago. I use it regularly to search for posts known to mastodon.social

Compare https://mastovue.glitch.me/#/mastodon.social/federated/search to https://mastovue.glitch.me/#/vis.social/federated/search

@Beth @lakoja @ProgGrrl

User on small instance: That's correct. You will only see few posts when searching for hashtags.

Professional on own instance: Without followers, your posts won't show up in any search outside of your own instance. You need at least one follower from an instance to have your posts show up on that instance for every user there.

It's not the amount of followers that influence the visibility, but the instance diversity of those followers.

@ProgGrrl @Beth @lakoja

- An instance can only show posts in the search that it knows of. (Exception: Using a Relay)
- Ways of knowing posts:
- - By users on that instance ("local posts")
- - By users followed by at least one user on that instance
- - Boosted by an user followed by at least one user on that instance
- - Searched for by URL by an user on that instance
- Instances remove remote posts after a certain time (Content cache retention period)
- All feeds are reverse chronological

@interru That argument goes both ways.

Not having fedi-wide search means that people who want to be found, flock to the biggest instances hence more centralization.

Making such a search engine open source, could lead to multiple search instances and prevent people from using mastodon.social for search.

@interru Now, I am even more confused.

The fediverse is already global. I can follow any account I want. That leads to the typical longtail distribution. Because of how search works at the moment, the few accounts with massive followings are visible on more instances than the ones with few followers. A fediverse wide search would give visibility to accounts with fewer followers.

@johnmu Mastodon has a search engine opt out setting for each profile which sets a noindex meta tag (https://vis.social/@Luca/109620741021800649). Honoring that and the robots.txt should be enough in my opinion. But as you have seen, many people see that differently.

The majority of people I reach are fine with hashtags in public posts being indexed: https://vis.social/@Luca/109619582185050938

Over the last few days, I experimented with moving my Twitter archive to my personal #Mastodon account @luca@social.luca.run and finally succeeded.

I had to modify the Mastodon source to allow backdated posts and prevent it from spamming other instances with old posts. Because image descriptions aren't included in the Twitter export, I had to request them from the API. There I got full text for truncated Retweets as well.

Incomplete notes:
https://github.com/lucahammer/fediporter

#TwitterMigration #MastoAdmin

@puniko @marcel Die false positives sind auf der Website gesondert aufgeführt und nicht im CSV import. Ich lasse sie anzeigen, damit kein false negatives verloren gehen (etwa Server, die derzeit offline oder zu langsam sind).

I started to work on #Mastoview.

Quickly peek into instances.

https://mastoview.glitch.me/

Rebuilt #MastoView with #vuejs and added a Toots per user table.

New URL: https://mastovue.glitch.me/ #mastovue

You can now search for #Hashtags with #mastoview and choosing if you want to get only results from one instance or its federated results.

https://mastovue.glitch.me/

#mastodon #search #tools #mastovue

I wrote a nano tool that tries to extract the #Fediverse accounts of your #Twitter followings: https://fedifinder.glitch.me/

It searches for the patterns @user@host.tld, user@host.tld and host.tld/@user in the screen name, description, location and URL field. It displays them to you in the correct format for easy copying as well as a CSV download that can be imported to #Mastodon.

Known issue: Mail addresses are included as false positives because people write their handle without a leading @: name@host.tld