ilinamorato

joined 1 year ago
[–] ilinamorato 1 points 1 day ago

Overall, in my experience, any improvement will require the same amount of time; whether from bad to acceptable or acceptable to good.

[–] ilinamorato 3 points 1 day ago* (last edited 1 day ago) (2 children)

I'm not saying it's a matter of desire. It's a matter of time. A full-time developer has to feed their family, so they have to put most of their time into the stuff that makes them money. That means that their passion project is just naturally going to get less time as a function of the number of hours left in the day and the amount of energy for coding that the developer in question has.

Further, ux design is a less "atomic" process; small amounts of time working on ux is going to have less impact than small amounts of time in coding. A programmer could conceivably fix a bug or make a minor improvement or feature request in ten minutes, and a Wikipedia editor could spend ten minutes improving the grammar and punctuation of an entire article; but the ux process requires mockups, iteration, asset creation, and coding for every change—and even if that can be done in ten minutes, the rest of the ui will look completely different, meaning that the overall ux will be worse than before, despite that one thing looking better.

What can we do to change it? Companies that rely on FOSS should contribute to projects so that the people who work on them can afford to do so at least part-time, or empower their own employees to contribute to FOSS on company time. Those are really the only two options, barring some sort of UBI or public grant for open source software.

[–] ilinamorato 13 points 2 days ago* (last edited 2 days ago)

That just means it's in active development and will come to the beta browser soon, and then to the stable version.

[–] ilinamorato 6 points 2 days ago (4 children)

Well, that's intentional though. The stuff that's buried is the stuff that doesn't make them money.

Bad ux in open source is because nobody has any money.

[–] ilinamorato 6 points 2 days ago

Honestly, just building an RCS app with easy grouping, quick captions, streak tracking, and delete requests would be the way to go with this. Then you have an immediate network effect of every iPhone and Android user in the world, and you don't have to get your friends to switch if they don't want to.

[–] ilinamorato 9 points 4 days ago

"ugh I know exactly why this is happening" is such a frustrating feeling. Especially when it's stuff that should've been found in testing, or that you know probably was found in testing, but they deprioritized the fix.

[–] ilinamorato 4 points 4 days ago (1 children)

Honestly this is the big thing I've found handy about using Mint. If there's something wrong and I can't find it a Mint answer, nine times out of ten I can fix it by searching for the Ubuntu solution. There's so much Ubuntu troubleshooting going on.

[–] ilinamorato 24 points 5 days ago

All I see here is people tricking the government into putting in a nice little micropark.

[–] ilinamorato 3 points 1 week ago

He also decided he could pardon himself last time, so there's that.

[–] ilinamorato 9 points 1 week ago (1 children)

Goals, for sure. The guy just does whatever he wants at this point. I think he's doing photography now?

[–] ilinamorato 3 points 1 week ago

I prefer "sackbut."

5
submitted 10 months ago by ilinamorato to c/support
 

I had 2FA enabled for lemmy.world before the big update this past weekend, and when I logged out/in this morning I discovered that 2FA had been turned off for my account. I've got it turned back on and I think it's working now, but just a heads up that if you had 2FA enabled you might need to re-enable it.

27
submitted 1 year ago* (last edited 1 year ago) by ilinamorato to c/android
 

In the latest Messages for Android Beta, scheduled send is broken due to a date validation bug. It won't let you schedule messages after today's date number in any month. So, for instance, today's date is 29 November, 2023; it won't allow any messages to be scheduled in December unless they're scheduled on the 29th, 30th, or 31st. Also, it won't allow any messages to be scheduled in 2024, for what I assume are similar reasons.

Reverting to the latest stable version fixes it and allows messages to be scheduled for any future date.

view more: next ›