That's already possible now! peakd.com/@username/feed Will keep it in mind though for our "advanced recommendations"

Good idea! Maybe someone from @peakd sees this and it'll be implemented there. Not really in the scope of the initial development of this project, but if we get to the point where we'll have our own front-end

Most likely will write a proposal when there's a team and we have something to show

Awesome, we'll have a Discord set up soon and I'd be happy to meet you there and talk some more

In the current state, hive is great for power users. If you invest time to explore you'll find what you want. But not many people are willing to do that, and it shouldn't be a requirement. I'll set up

User tracking + time spend ( and heat mapping) Yes, I also think we'll need those And no, I don't think it's off topic. In the end that's exactly what I'm trying to achieve, better and easier content discovery

I would like to see options in the future for privacy by default, allowing users to reveal just a snapshot of certain information that they would like to make public I totally agree with that. It has to

Thank you!

Privacy should always be the default option imo

I didn't, no, thanks for pointing it out. Need to dig deeper to really understand it, for now it seems like it'll make this project even more complicated :D

I feel most creators do a poor job at making it easy for someone to find more related content of their own once someone finishes consuming a piece of content. And it really shouldn't be their responsibility

That's an interesting thought. Not seperating datasets by language could lead to more false positives for languages with few posts, but that's just an assumption of mine right now. Thanks for the input!

There will always be frontends that don't track, at least hive.blog I agree with the second paragraph, a tutorial would help a lot already. Human assistance is difficult to organize well in a decentralized

Not on-chain, no. A second layer solution is possible though. I agree that communities could be used much better too, but first they have to be able to be set read only.

More like, give regular social media users the possibility to engage with content the way they're used to

I'm not in favour of projects using the posting reward pool to finance themselves, so that adds another hurdle. Personally, I don't work for money but to create something, so a baseline would be covered.

That completely aligns with my experience. Although I'm seriously jealous about that retention rate. Mine is more like 10%, optimistically.

I don't know about other curation projects, but curangel doesn't make profits at all. For now I'll be able to cover the expenses and (slow) development through the witness. If I drop out, price drops a

This has to be explored, tested and evaluated. These types of algorithms aren't static once implemented, they need constant fine tuning.

The algorithm should not show content by profits, votes, or dv if we were to add. absolutely