Comments should be removed before shipping.
I am Rooki Cookie. I am a programmer and i try to help everyone :)
Comments should be removed before shipping.
“You dont have to care about infrastructure…” is the bigest lie of those microservice hosting providers.
Sorry but i have to rant.
There is a lot of misleading information in this post.
Not misleading, straight to the point, on things no one else wanted to point out.
Correct the CSAM wave was handled by admins on their own. As far as I remember there were no specific feature requests that would have helped in this regard, and anyway they would have taken too long to implement and publish.
Yes we were put just aside because the feature we recommended was “pictrs” stuff.
There is a fundamental lack of confidence amongst a majority of Lemmy instance admins towards the lead developers of Lemmy.
Thats true and so far many instances ( i dont want to say who, because they should come out if they want to be known ) i and the lemmy.world team have many reports from users, admins that they want a better replacement for lemmy. ( e.g. Sublinks ).
The moderation is TERRIBLE after 0.19, the sorting totally wrong unchangeable, every “resolve” leads to page refresh ( have fun finding your report you left on ). New reports are just never seen again, because you cant sort by new. The “All” view is terrible in reports and private messages. Marking Private Messages as “read” just refreshes the page and on the ui doesnt change anything, but after refresh it is marked as read.
On 0.19 there are some occasions of untested things, like “Remove an admin” is not correctly translated. Something THAT primitive.
We / Jgrim never opened a feature request because we already got enough by seeing in the history of feature requests of others.
The ui gets just worse and worse, untested features goes to prod and not getting even a “Warning Untested feature” flag.
We know you are just some guys in their free time. But then why not take your time, test it, make sure everything works, then release it.
Quality is the key for a thriving software, not pushing versions like its a tournament on how many versions can someone push to prod.
You are not a big corpo that can deploy fast fixes that fix any issues that could block instances, so quality is here even a higher priority.
Thrive? The only thing i see is an cash grabs from big corporations.
Wow a pc but for 1 hour or be plugged in like any other macbook. So its a accessory like a macbook to the wall socket ;D
Same for the reason, i dont say its not innovative combining vr and ar, but the closed ecosystem will kill it in the end.
So literally like any other VR headset, but for less money. For 3.5k you can buy a great pc AND a vr headset.
It is hard to think it will get any support by anything, because its just restricting them to be a only apple product, where with any other VR headset you can use Steams VR Games or other compatible ones
It is a bit like the foldable phone. But with two more hinges.
But then there would be a gap between one of those segments.
Yeah, its a bit tricky and react is not supper SEO friendly. But occasionally google indexes some pages it can find. ( Or at least the front page )
To be honest they couldnt chose any worse color palette. They should have not chosen yellow, darker yellow and orange.
WoW guys, you did a great job of making a good look on newcommers!
For this i reward this post the golden Lock.
Every instance is good because every instance can interact with many other instances with comments, posts etc. So you arent really locked into one instance. its the magic of federation.
Its the basic free market idea… you dont like company ( for our side “instance” ) A then why dont buy it from Company(“instance”) B?
The only difference is that you can still access posts/comments from other instances after you switched.
On lemmy, you dont have 1 instance with that community, if a mod or admin is not good, just swap the instance and make there a better community.
deleted by creator
Recieved the test ;D
I guess there could be just a script before deployment.