Notices by Fedilab Apps (apps@toot.fedilab.app)

RE: https://mastodon.social/@HolosSocial/116166995091607292

We will introduce the #HolosDiscover API in #Fedilab. It allows to tailor a timeline with up to 20 tags. It can be really useful for small instances.
However, unlike the #Holos app where posts from blocked or muted accounts are filtered out, Fedilab won't be able to apply these filters.

We published #HolosDiscover 1.2.5, this release fixes RSS issues on some readers:

https://discover.holos.social/feeds

Also, for more transparency, we added a real-time stats page showing processed #ActivityPub activities, blocked instances and more.

https://discover.holos.social/stats

RE: https://toot.fedilab.app/@apps/116150834668192683

We added RSS feed support to #HolosDiscover for Trending and Timeline. For the timeline, you can create feeds by filtering with hashtags (up to 20). There is a URL feed generator to make things easier. More at https://discover.holos.social/feeds

@quantum_splash
Service is up again. Sorry for that

Trending data is updated at different intervals: hashtags are refreshed every hour, links are aggregated daily, and posts are ranked in real time based on engagement with time decay.

#HolosDiscover 1.2.0 is available. Thank you for your feedback, we took it into account.
You have access to trending links now.
https://discover.holos.social/

As a consequence, the public timeline from the relay will no longer be available since most activities are now filtered out.
#HolosDiscover will replace it with a public timeline showing content based on your interests.(2/2)

One challenge with #Holos: the relay can accumulate a lot of pending activities. Users have to download everything before seeing their feed.
By design, the relay has no knowledge of your followers or followings and never will. That's why we introduced Bloom filters (https://en.wikipedia.org/wiki/Bloom_filter): your device sends a compressed version of your followings at each sync so the relay only returns what matters. At worst you get a few extra activities, but never miss any. (1/2)

#HolosSocial

@ePD5qRxX
Yes, issue spotted. Thanks for your feedback. @joergi

@catsalad
That confirms the point of @wizard https://gts.zebras.social/@wizard/statuses/01KJGFZBV7P19EFMZC901QZCFT
@joergi

@wizard
Interesting. That looks like a concurrency issue with the UX display before receiving the accept from the remote instance. The app might have cached the response with an empty quoted message.

RE: https://chaos.social/@joergi/116144640503034520

Let's see if it works, please don't hesitate to share if you're also experiencing this bug.

#HolosDiscover 1.1.0 has been released.

The trending algorithm now uses time decay so recent content gets more weight. Older posts don't dominate the results anymore.

A privacy page has been added: https://discover.holos.social/privacy

There's also an API documentation page with interactive testing: https://discover.holos.social/api-docs

API keys are only needed for server-side apps (same IP for all requests). Mobile and desktop apps don't need one, rate limits are per user IP.

@nikclayton
The doc is currently on our repo, we will make things clearer soon https://codeberg.org/tom79/Holos-Discover/src/branch/main/doc/api.md

@lexinova
No worries, bad UX is also a bug in the app. So don't hesitate to share all the details about what you encountered vs. what you expected.

We received several requests to enhance #CastLab, an open source app to cast your photos, videos, and audio to DLNA/UPnP devices like your TV or Kodi.
That will be done. More about this project: https://f-droid.org/packages/app.fedilab.castlab

@lexinova
If you deleted your account, the custom domain should have been removed from the relay as well. Can you confirm what you're still seeing? If something remains, we can clean it up on our side and fix this issue.

@lexinova
The relay profile is just a web representation of a user on the relay, whether they have a custom domain or not. It doesn't reflect the ActivityPub reality. Remote instances know your new identity and interact with your custom domain profile. Our current design is misleading though, we should redirect to the custom domain profile when one is active.

@lexinova
We identified a bug where creating a second account caused issues, fixed in rc-3. Your data should still be available. We can look into your case in detail and develop a patch if needed. Feel free to share more in DM.
Regarding the relay profile: it acts as a proxy for your custom domain, so it can't be fully disabled. It resolves WebFinger and routes ActivityPub requests to your device. We'll add a redirect on it to indicate the custom domain profile.

@lexinova
It's available in rc-3 published today. We removed this action from the relay because it doesn't have access to followers to send them the Remove activity.