Yeah, I agree that the above is excellent advice. Engaging in a way that comes off as "you're a shit parent so I'm going to do it for you" isn't likely to build conflict. It's possible how the mother reacts regardless of what you say (due to insecurity about her parenting), but it's going to be much better if everyone is working together rather than against each other, so that's the best place to start.
lotanis
joined 1 year ago
This is great, but I found the alphabetical sort order made it difficult to analyse. Perhaps it would be better to sort by AVG?
Coincidentally, I've been looking at these as I'm due a new phone soon.
The flip 5 style has no value apart from gimmick as far as I can see. It goes in your pocket in a smaller height which might be of use to some people but that's about it. Same volume of phone, same size of screen.
The Fold 5 style makes a lot more sense to me. You get a phone the same size as a normal one (roughly) but then a screen twice sized normal (roughly). I'm sure not everyone is interested in that, but there's definitely a practical value there for some.
Is there anything that only the rich can currently afford but that everyone will have in the future?
Yes, but the public transport in Singapore is excellent. I wish more cities did it.
See the other message I have written - you should always recommend search. The URL only works if someone has already searched for that community. If you're on a big instance, that's almost always true, but on a smaller instance it often isn't.
The above advice isn't perfect - in general, use Search first.
Until the first person searches for a community on your instance, your instance doesn't know about it and the URL won't work. Searching (usually using the [email protected] form) should always work.
Equally, your instance doesn't start pulling data on a community (messages etc.) until someone subscribes to it, and then when subscribed it will sometimes take a a few hours to get it all (it should immediately start getting new posts and comments).
The general concept you're describing is called Risk Compensation. It feels intuitively correct, but in whatever context it's been studied in almost all cases it turns out that the safety feature is actually better overall. Some people might be a bit riskier knowing about the safety net, but not enough to counteract the safety improvement.
Also - in the UK - road deaths go down over time, while miles driven goes up. Driving is getting safer. Cars are part of that, but so is road nd signal design and driver training.
It's a core capability, but it's a lot of work due to all the different types of thing you can post.
An app that can read posts and write comments is still useful without submitting posts, but an app that can submit posts but not read them is pretty useless. So, when you're making stuff you do reading posts first, then you do writing comments, then you do submitting posts. That makes sense, right?
Let's say it takes a few weeks to do each, and you've got to the stage where you've done reading and comments, but not submitting. That's useful already! You're not done, but what you've got is still useful for people and people want it, so why not release it at that point? Then carry on working and release the remaining features after.
Releasing as early as you can is good for everyone - the developer starts getting income for the work they're doing, they learn about bugs and issues earlier in the development process and we get to start using it sooner. For me Sync without submitting is still better than the other apps, so I want to use it.
Everything=all but there is a Lemmy oddity here.
Everything shows everything for all the communities subscribed to by anyone on your instance. So it might be different from one instance to another because the users have subscribed to different sets of communities.
It's likely to be a small difference between two big instances (lots of users so most communities will have at least one subscriber), but if you self host an instance it'll be pretty useless.
Yeah, this is the rare case where you do actually want the direct link. In general though the bot is very helpful.
I think we need to separate the system from the product. With Reddit they're the same, with a single owner. With Lemmy/ActivityPub, just like with email, there's an underlying system that nobody owns. It's an ecosystem of pieces created by lots of different people.
It is a good thing that people are building products on top of that. Some of them are FOSS and some of them not. As long as no-one gets too much control of the underlying system then that's great! Users retain choice and can choose FOSS apps if they want, or they can choose something like Sync.
I agree it would be sad if the only apps were paid, but I think a mix is a sign of a healthy ecosystem.
I think we need to be realistic that we aren't going to do much better than this price point. Instead, I'm hoping that they can stay at this point and periodically improve the hardware.