[-] mack123@kbin.social 2 points 1 year ago

I am so new to this that I cannot say. It may be area for the many apps under development to shine.

[-] mack123@kbin.social 1 points 1 year ago

Have a look if you don't have an accidental subscription to kbin.social.

I had a similar problem. That seems to be a connection point for federated posts and makes all of them appear in your subscribed feed. It does not appear on your magazine list.

[-] mack123@kbin.social 1 points 1 year ago

I have seen the same behaviour on my mobile browser. Desktop seems to not have rhe issue. Error when upvotiing, fixed by a page reload followed by an immediate upvote.

[-] mack123@kbin.social 3 points 1 year ago

Agreed on your point. We need a way to identify those links so that our browser or app can automatically open them through our own instance.

I am thinking along the lines of a registered resource type, or maybe a central redirect page, hosted by each instance, that knows how to send you to your instance to view the post there.

I am sure it is a problem that can be solved. I would however not be in favour of some kind of central identity management. It is to easy a choke point and will take autonomy away from the instances.

[-] mack123@kbin.social 1 points 1 year ago

That should just work. You view the post on your own instance and reply there. That reponse trickles to the other instances.

It may take a while to propagate though. The paradigm is close to that of the ancient nntp news groups where responses travel at the speed of the server's synchronisation. It may be tricky for rapid fire conversation, but works well for comments of articles.

[-] mack123@kbin.social 1 points 1 year ago

There is an important distinction that we must make. Community vs application.

My experience is like yours, made an account on lemmy, beehaw and here. When we saw the Reddit writing on the wall. The community here has been so much fun interacting with, that I have mostly stayed here.

The software is in its infancy and that is exciting. Tricky and maybe a little unstable, but conceptually exactly what I have wanted for ages. It will get there eventually. Ernest and team has been doing a spectacular job keeping the loghts on.

I expect that we will get many different aggregators for federated content as the platform matures.

[-] mack123@kbin.social 0 points 1 year ago

Sometimes the mobile U/I wins, but I decided to let it stand regardless of replying to the wrong comment. Maybe the troll learns something, though I doubt it.

[-] mack123@kbin.social 0 points 1 year ago

The rules of the internet remains unchanged, regardless of platform. Do not feed the trolls.

[-] mack123@kbin.social 2 points 1 year ago

The exciting thing about this space is that much of it is undefined. It is all about the protocols and the main features at the moment. The 2nd generation tools will be born out of what we discuss now and think about now.

How do you make sure a user is not trapped in his special interest bubble and still gets to see content that has everyone excited? How will we make use of the underlying data, on both posts and users to suggest and aggregate content.

I think there will be more than one solution eventually, different flavours of aggregators running on the same underlying data.

So much possibility. And we control it. If you don't like the way your lemmy instance or kbin aggregates, choose another site or build your own. The data is there.

[-] mack123@kbin.social 2 points 1 year ago

That is a good way to think about it. What is the need from the reader's perspective and from the poster's.

One would certainly read a post with low upvotes from a author with high reputation if you are interested in the specific magazine. I wonder if the reputation should not be topic bound and not just general. That would be useful from the reader's perspective.

[-] mack123@kbin.social 1 points 1 year ago

An excellent read. Thank you

view more: ‹ prev next ›

mack123

joined 1 year ago