Currently, the #Holos relay has different TTLs depending on activity type. For instance, follow requests stay longer (365 days) while public messages remain for 7 days. Each admin can change these values and they are displayed on the about page. At the app level, you can adjust this value between zero and the max set by the relay. We will also make the relay a little smarter to automatically reduce these values when accounts become inactive, as these are a lot of wasted resources.
This is how #Holos currently handles #E2EE DMs over #ActivityPub. Holos is a project we develop alongside #Fedilab.
This is how #Holos currently handles #E2EE DMs over #ActivityPub. Holos is a project we develop alongside #Fedilab.
If you have no connectivity, yes #Holos will work. If you do actions like boost, like, or even write a message, the app will automatically queue them and process your actions when the connection is back. That's how we will handle the automatic deletion of your messages once they reach the TTL you set. You can always manage this in your settings.
We've optimized data loading so #Holos feels fast and seamless despite running its own server.
What's next:
- Interaction controls (#GoToSocial approach) to manage who can reply/boost/like your posts
- Keywords filtering on the public timeline to reduce noise and show what matters to you
- Community domain blocklist subscriptions with auto-sync
We've optimized data loading so #Holos feels fast and seamless despite running its own server.
What's next:
- Interaction controls (#GoToSocial approach) to manage who can reply/boost/like your posts
- Keywords filtering on the public timeline to reduce noise and show what matters to you
- Community domain blocklist subscriptions with auto-sync
We're looking into implementing interaction controls in #Holos, following the approach proposed by #GoToSocial. This would let you decide who can reply, like, or boost your posts. It fits well with the Holos philosophy of giving you full control over your online presence. More details here: https://docs.gotosocial.org/en/latest/federation/interaction_controls/
We have really improved the sync process when starting the app. Home messages and notifications are now displayed quickly. Before the next RC release, we have to deal with a major issue: the auto-cleanup process isn't working properly, which is why databases keep growing. On the bright side, they are more robust and should not get corrupted. We should be able to publish the release this week.
We have really improved the sync process when starting the app. Home messages and notifications are now displayed quickly. Before the next RC release, we have to deal with a major issue: the auto-cleanup process isn't working properly, which is why databases keep growing. On the bright side, they are more robust and should not get corrupted. We should be able to publish the release this week.
If you have no connectivity, yes #Holos will work. If you do actions like boost, like, or even write a message, the app will automatically queue them and process your actions when the connection is back. That's how we will handle the automatic deletion of your messages once they reach the TTL you set. You can always manage this in your settings.
Currently, the #Holos relay has different TTLs depending on activity type. For instance, follow requests stay longer (365 days) while public messages remain for 7 days. Each admin can change these values and they are displayed on the about page. At the app level, you can adjust this value between zero and the max set by the relay. We will also make the relay a little smarter to automatically reduce these values when accounts become inactive, as these are a lot of wasted resources.