match the selected account focus.
The best of this would be another path : sync search/lists/hashtags from the web version to the mobile app version. Imagine adding a new column on your #mastodon account only to have it synced and directly available on your mobile.. That would be really neat!
When I monitor different stuff I like not being budjed by noise that can be considered as signal from another account point of view and vice versa.. But that's @firstname.lastname@example.org - 2/3
I need to understand why some #mastodon instances can be followed (Public toots from the instance itself) and other instances don't seem to have a public stream.
Where is that configured when administering a Mastodon instance?
The #mastodon "progressive web app" isn't that bad, I suspect my phone is slowing it down & perhaps the server has also a role in this lag compared to using #fedilab but other than that it's pretty good from mobile, also has its own integrated app icon, so it's really behaving like a native application.
How do you handle notifications from different #Fediverse building blocks ?
Imagine you have a #mastodon #pixelfed and #peertube account somewhere, you can get notifications on each services..
#fedilab handle the 3 services, so one can switch between identity & check the notifications, interact and so on..
But what if we could define a Main identity as a receiver of other self identities on different services & pilot interactions & notifications read/unread all from the same - 1/2
from app devs the easier it is to follow development & even contribute with bug reports etc..
3) I was bit worried about resources usage, it seems activating the relay & allowing registration expose one's instance to quite a lot of pressure.
Thought : I wish there was a very low footprint, single user manner to join the fediverse without the complexity & feature set of #mastodon the good thing is it seems several attempts at doing just that are ongoing.. The future of the fediverse - 2/3
After a few months running my own #mastodon instance I came back to public instance for a bunch of reasons :
1) my instance was running on a existing server where I already host lots of different stuff.
Lesson : better to have a dedicated machine because of resources, relay, user registration etc..
2) Since my backend was docker I was depending on a chain of good willing people to update app packages to always get latest version (I'm using cloudron.io)
Lesson: the closer you get - 1/3
| Love to promote #Indieweb & self-hosting approaches to reclaim the web. | Geek | Social & Climate Justice ¦ He/Him
Discover & explore Mastodon with no ads and no surveillance. Publish anything you want on Mastodon: links, pictures, text, audio & video.
All on a platform that is community-owned and ad-free.