we need

• links from fediverse instances to other fediverse instances
• maybe tools like https://fediversemap.com/ to find fediverse instances that are physically close to you, to connect to people irl and organize irl events
• prefer to post content on already existing instances so you get better exposure

i think search engines are … tricky

i always prefer lists and indexes over search engines because search engines feels a bit like voodoo magic to me, it has unpredictable outcomes. for example, sometimes you need just the right keyword for search engines to give you meaningful results, and otherwise it will just not return anything. and that is a lot like chatgpt … you ask it something and it might give you a meaningful response. or it might completely miss the point. when there’s an actual list of communities that is small and complete, then i can go through it manually to check where it might be.

everything is an echo chamber

can you name a single thing that’s not an echo chamber of some sorts?

the side bars for each community can effectively be a webring. i’m talking about these things here:

(example is the sidebar of the /c/selfhosted@lemmy.word community)

nice, not too bot-infested, privacy-respecting, free, distributed and federated platform

nice, mediocrely bot-infested, publicly readable, donation-funded, distributed and federated platform

ftfy

I think making your articles on the fediverse is better than building your blog website from scratch.

Instead of https://thisismywebsite.com/blog/
instead do https://publiclemmyinstance.com/c/myblog

This way, it better integrates with fediverse mechanics such as follow, like, comment. Also people can discover your stuff through the “all” feed, even though unlikely, maybe one day we’ll get more interesting recommendation algorithms for the fediverse.

emailing his photos to his friends

that’s sometimes difficult, e.g. when you have thousands of photos, and emails have a size limit of 20 MB per email. using matrix chat or sth is also not ideal since the other side will have to download images one-by-one. sending a zip file might work, but the matrix protocol might have a size limit for attachments.

an FTP server might work. also consider that you want to store the images somewhere, not just send them once. how do you do that with messaging services?