@1chemistdown ActivityPub is a public protocol just like every other Internet protocol. Individual server Admins, whether they run KBIN, Lemmy, Mastodon, Calckey, PixelFed, PeerTube servers, are free to block any other server that connects to ActivityPub. You have to ask the Admin of the server you're on or interested in joining.
I agree with all that you've said
I was hoping to store the images directly in an S3 bucket at Wasabi, which is what I do for Mastodon, Calckey, and Peertube. However, this is not yet supported in KBIN. I think only AWS is supported as a hard-coded option.
I tried setting up a FUSE drive connected to Wasabi and I used a symbolic link to point public/image to it, but, alas, the Symfony framework does not support symlinks. Until external S3 is supported, I have to store the images locally. Ernest did post today that external storage for thumbnails is on the horizon. So maybe all media can be externally stored.
Until then, I'm storing them on the local disk. This weekend I'm going to see if I can set up rclone to automatically synchronize the public/image directory to a Wasabi S3 bucket so at least it will be constantly backed up.
When external S3 becomes an option, I'll move the media folder to the S3 bucket and hook it up.
Congratulations! Good job!
It uses PostgrSQL. I'm paying an extra $2/month to keep the database on an external drive. So far, it's only using 151 MB of the 20 GB. I don't think I'll run out of space for a while. But, this weekend, the larger server I move to will come with an 80 GB drive so I don't think I really need an external drive. Currently, the DB doesn't cost anything extra.
But, you reminded me, there is a cost to keeping a database backup. My server is in NYC1. I have an S3 bucket in NYC3 that will be use to hold 5 days of daily database backup, compressed. I pay $5/month for the 250 GB Digital Ocean S3 bucket, I believe.
I share your thoughts on this. The only reason my server has 301 magazines from other servers is because I visited those other servers, searched through their magazines, and one-by-one, entered their full names into mine because they seemed popular. I've confirmed with several others that this is how it works.
I hope this gets changed because what happens now is that there are multiple magazines, covering similar topics, all independent of each other on different servers. If I wanted to join a Linux discussion group, for example, I would want one Linux group shared across all servers. But, unless someone knows of a magazine on the other server and introduces it to the local server to link to it, there will be two independent groups. Multiply this by all the servers and there's quite a mess. People are missing out on discussions.
I want a true content aggregator. I don't think we've reached this goal yet.
:) Compared to Jerry Bell, I'm more of the Jerry Jr.
Wow. Nice!. Is there an option to make it available, or would I just link to it in the "about" page?
Yep. I did what @Granite did. I went around to a number of other instances and manually entered the full magazine names that looked most used. I also looked at the list of subreddits that moved to their own KBIN and Lemmy instances, and connected to them
I used a VPS running Ubuntu and followed the Docker installation. The only issue I ran into was that the docker-ce installation instructions don't work on Ubuntu. They were written for Debian. This is easy enough to work around. Just find the Docker install instructions and the docker compose plug in instructions for your Linux and use them instead of what he has, if you run into an issue.
As long as you follow the instructions exactly it should be fine. Your experience should be enough.
I initially set it up on a really small VPS with with 1 GB / 1 CPU and 25 GB disk. I scaled it up after I got everything working and checked out. It performed fine on that small VPS.
Not good for an application promising to be a "content aggregator"
This will lead to a number of magazines with the same names and topics existing all over the place because people can't see that a relevant one already exists. This will make a big mess and people will miss out on discussions.
And who would want to join any instance other than the biggest if they have to visit the biggest anyway to find interesting magazines?
And even on kbin.social, everyone is missing out on Lemmy ones. :(
Do you know if Lemmy can find magazines on KBIN or other Lemmy servers simply by searching by name?
Jerry
joined 1 year ago
The key word here is "connected" instances. You don't find hashtag-related posts from all the servers, just the servers that your server is connected to and also only posts that your server has seen from other servers.
This is why, on my instance, I relay with over 300 other instances, some of them are the larger ones. All the posts they see on their server are duplicated onto my smaller server. The impact is that while my server is small, it has the same messages as one of the large servers which makes for a better experience. Note that Mastodon.social does not relay with any other instance. Not that most instances could possibly hold all their posts and accounts anyway.
When I search for hashtags on my instance, I do get a lot of hits.
Many smaller servers do not relay as much as I do, or at all, because it requires disk space to store all the posts, images, and accounts that are streaming in constantly from all these other servers. I don't have these concerns because I have unlimited capacity. So, the experience will vary depending on which server your account is on.