Earlier quoted context omitted.
I agree, I started looking at setting up a mastodon instance and didn't get very far before looking at alternatives. Thanks for the suggestion. I don't really want to run another Wordpress, but Gnu Social looks promising.
Check out pleroma. It uses much less resources than mastodon so it’s been nice as a single user instance.
Microblog.pub – A self-hosted, single-user, ActivityPub powered microblog
31–40 of 62 posts
Re: Microblog.pub – A self-hosted, single-user, ActivityPub powered microblog
#32Earlier quoted context omitted.
Do you see their posts in your feed?
There's definitely some weirdness with the @t@hexa.ninja account given as an example of an instance in the wild. Loading that in Mastodon's "Web" says it contains "4 posts", but consulting the "Posts and replies" tab will reveal the contents of 5 posts. Meanwhile, this number is about half of the expected number, based on the posts that are actually visible on the https://hexa.ninja/ > landing page (i.e. as viewed in…
ActivityPub is a publisher/subscriber protocol
Re: Microblog.pub – A self-hosted, single-user, ActivityPub powered microblog
#33The problem is self-hosting is too difficult for the average person. But that doesn't have to be the case. Self-hosting shouldn't be any more complicated or less secure than installing an app on your phone. You shouldn't need to understand DNS, TLS, NAT, HTTP, TCP, UDP, etc, etc. Domain names shouldn't be any more difficult to buy or use than phone numbers. Apps should be sandboxed in KVM/WHPX/HVP-accelerated virtual machines that run on Windows, Mac, and Linux and are secure-by-default. Tunneling out to the public internet should be a quick OAuth flow that lets you connect a given app to a specific subdomain, with TLS certs automatically obtained from Let's Encrypt and stored locally for end-to-end encryption.
Re: Microblog.pub – A self-hosted, single-user, ActivityPub powered microblog
#34Earlier quoted context omitted.
ActivityPub and GNU Social users! There are dozens of us, Michael, dozens!
It’s not very surprising. I was looking around for an easy way to set up anythi g using ActivityPub using a single docker instance, and all the big players are ‘check out from source and run directly on your server’. No thanks.
I think there are probably two main groups interested in ActivityPub. The 80% will want to just register on someone else's instance. The rest are nerds who will set up their instances for fun, and will not be massively hindered by the lack of simple set-up options. I would guess that users like you ('curious, but not invested') would likely not gravitate to ActivityPub anyway, and almost certainly not to hosting your own instance.
Re: Microblog.pub – A self-hosted, single-user, ActivityPub powered microblog
#35Application-wise this looks awesome. I would love to see way more people using something like this. The problem is self-hosting is too difficult for the average person. But that doesn't have to be the case. Self-hosting shouldn't be any more complicated or less secure than installing an app on your phone. You shouldn't need to understand DNS, TLS, NAT, HTTP, TCP, UDP, etc, etc. Domain names shouldn't be any more diff…
Re: Microblog.pub – A self-hosted, single-user, ActivityPub powered microblog
#36Earlier quoted context omitted.
There's definitely some weirdness with the @t@hexa.ninja account given as an example of an instance in the wild. Loading that in Mastodon's "Web" says it contains "4 posts", but consulting the "Posts and replies" tab will reveal the contents of 5 posts. Meanwhile, this number is about half of the expected number, based on the posts that are actually visible on the https://hexa.ninja/ > landing page (i.e. as viewed in…
ActivityPub does not handle old posts. This post number is the number of posts since at least one person on that instance followed them. Before that, the instance didn't know they existed ActivityPub is a publisher/subscriber protocol
That is incorrect. Mastodon is the one doesn't handle old posts[1], because they insist on presenting to the user only what has already been federated with it. See [2] for a more in-depth explanation.
If they would use the protocol as intended, and actually perform requests on the remote Outbox collection when the user wants to view the posts of a remote actor, there would be no issue.
[1] https://github.com/mastodon/mastodon/issues/14017
[2] https://github.com/mastodon/mastodon/issues/14017#issuecomme...
Re: Microblog.pub – A self-hosted, single-user, ActivityPub powered microblog
#37Application-wise this looks awesome. I would love to see way more people using something like this. The problem is self-hosting is too difficult for the average person. But that doesn't have to be the case. Self-hosting shouldn't be any more complicated or less secure than installing an app on your phone. You shouldn't need to understand DNS, TLS, NAT, HTTP, TCP, UDP, etc, etc. Domain names shouldn't be any more diff…
All of which is why SaaS is a thing, no?
Re: Microblog.pub – A self-hosted, single-user, ActivityPub powered microblog
#38I saw that mastodon.technology is shutting down soon. Would this microblog.pub be a good alternative to hosting my own mastodon? I don't have any other users, so it'd just be for me to maybe interact with people on other mastodon instances.
Re: Microblog.pub – A self-hosted, single-user, ActivityPub powered microblog
#39> Uses SQLite, and no external dependencies except Python 3.10+ I don't know if it's the way it's been written, but it reads to me that only python is needed, no libraries. I'm assuming this isn't true though: I can see a lot of libraries: https://github.com/tsileo/microblog.pub/blob/v2/pyproject.to...
I would have guessed that it means something like "you know how you need to get postgres, redis, and elasticsearch up for a good mastodon install? none of those"