All credits go to superuser answer.
Get-ChildItem | Where-Object { $_.PSIsContainer } | ForEach-Object { $_.Name + ": " + "{0:N2}" -f ((Get-ChildItem $_ -Recurse | Measure-Object Length -Sum -ErrorAction SilentlyContinue).Sum / 1MB) + " MB" }
Venting out, sharing findings that took me time or just keeping notes for myself.
All credits go to superuser answer.
Get-ChildItem | Where-Object { $_.PSIsContainer } | ForEach-Object { $_.Name + ": " + "{0:N2}" -f ((Get-ChildItem $_ -Recurse | Measure-Object Length -Sum -ErrorAction SilentlyContinue).Sum / 1MB) + " MB" }
Last update: 2026.04.07
2024.10.17
Time Tracker for Android is another app I made for my own use. I released it on December 4, 2010, and the last update was 5 years ago. I had pretty much forgotten about it until I started receiving constant warnings from Google Play that my app would be removed from their store. Instead of abandoning it, I decided to update it.
At that time, the app had 22 installs and exactly 0 monthly active users. AdMob was reporting lifetime earnings of $79 USD — another financial success of mine.
The first step was to move the code repository from CVS (anyone remember that one?) to GitHub. Android Studio couldn't even build the code when I opened it.
![]() | |||
| The app launcher icon, before and after the redesign |
![]() |
| Sample screenshot, before and after the redesign |
Time Tracker for Android has been redesigned using Material Design 3 with Dynamic Colors. Check out the short video demo here: Time Tracker for Android video demo.
To sum it up, I invested a few hours, and Time Tracker is back on track! I've also been thinking about the future of this app and my other projects. Once I finish getting my other apps through the F-Droid pipeline, I plan to open-source Time Tracker as well. This will give other developers the opportunity to contribute or fork it for their own purposes.
In the meantime, if you want to try out the updated version, you can download it directly from Google Play: Time Tracker on Google Play.
2026.04.07
My other apps are still somewhere in the F-Droid pipeline, but Time Tracker has been open sourced!
Ovaj
post je za sve marljive i kreativne cure koje se bave vezenjem,
pletenjem, kukičanjem, etc. i furaju se na hard core vintage.
Časopis
Weldon’s Practical Needlework počeo je izlaziti prije nekih 150 godina i
sadržavao je detaljne upute i ilustracije za ručni rad iz
viktorijanskog doba. Časopisi su naknadno izdani u nekoliko svezaka,
neki od njih su kompletno skenirani i dostupni su on-line. Ja sam
iskopao 3. Linkovi su niže, za slučaj da vam još nisu dopali u ruke.
Eto, ako ste oduvijek htjele onaj šeširić ili korzetić sa čipkom iz te
ere, izgovora više nema.
[Volume 2] [Volume 3] [Volume 10]
Fotografija za bolju vidljivost posta: Slim-Fit Undies. (Weldons Practical Needlework No. 207)
Breaking news: Jared Diamond nije bio u pravu i za kolaps otočne civilizacije nije kriv suicidalni ekocid. Kolapsa prije dolaska Europljana zapravo nije ni bilo.
Rapa Nui (Veliki Rapa) ili Te Pito o Te Henua (Pupak svijeta), poznat i pod imenom kojeg su mu dodijelili kolonizatori - Uskršnji otok, najizoliranije je mjesto naseljeno ljudima. Nalazi se usred Tihog oceana, na istoku ga dijeli 3.700 km od Južne Amerike, a na zapadu 1.900 km do prvog sljedećeg naseljenog otoka (Pitcairn, slavan po tome što su ga pobunjenici sa broda Bounty odabrali za svoje utočište).
Rapa Nui je toliko velik da se biciklom može obići u pola dana (otprilike 60 km obalne linije, površinom kao pola Korčule), a najpoznatiji je po ručno klesanim golemim kamenim statuama - Moaima.
Posljednja genetska istraživanja (jučer objavljena) potvrdila su da nije postojao nikakav nagli pad broja stanovnika otoka prije prvog kontakta sa Europljanima. Populacija je čitavo vrijeme blago rasla i, po svemu sudeći, lokalno stanovništvo je znalo živjeti i nakon što su izgubili i posljednje stablo na otoku. Istraživanje je također pokazalo da su se u periodu 1280 – 1495. miješali sa stanovništvom Južne Amerike, ali nije poznato jesu li plovili do tamo i nazad ili su Južnoamerikanci posjećivali njih. Obje opcije su moguće.
Izvor:
https://www.nature.com/articles/s41586-024-07881-4
Skraćena verzija:
https://www.nature.com/articles/d41586-024-02962-w
Audio:
https://www.nature.com/articles/d41586-024-02963-9
Published: 2024.08.03.
Last update: 2024.09.24.
Healthy Battery Charging is a free, open source app that notifies you when your battery level reaches a certain threshold. To minimize battery consumption, battery level checks are performed at most every 15 minutes.
Thanks to the open-source community, I recently translated the app into Portuguese. However, when I tried to publish the update on Google Play, it was rejected due to a Deceptive Behavior Policy violation:
Attached screenshot:
At this point, I gave up arguing with them. Google Play users won't receive this update, and possibly future ones as well. They can find the app elsewhere:
Please note that GitHub is the best source for immediate updates.
As I already mentioned, Healthy Battery Charging is a free and open-source app without any ads, so my finances aren't affected in this case. It makes me wonder about the consequences if it were one of my commercial apps. Perhaps these policy violations count against my app publisher 'score' and could lead to my app publisher account being closed? I hope not.
I'd love to hear about similar experiences other developers have had. If you find yourself in a similar situation and want to communicate with a real person instead of a brain-damaged bot, this post might be helpful: Google Play Store contacts for Android app developers.
Update 2024.08.07: I contacted Google Play Business via twitter, and they just confirmed their initial decision:
Update 2024.08.11: Asked for community help here - False Deceptive Behavior Policy violation, app doesn't claim features impossible to implement.
Update 2024.08.12: I once again contacted support via email, describing the app functionality, and here is their reply:
At the same time I received this reply, my app update was approved. I'm not sure how to explain this inconsistency in the approval process. Probably the reviewer wasn't informed of the app suspension or he/she had a different interpretation of the policy.
Update 2024.09.17: My app is suspended again, the same policy violation. This time the sentence "Make your smartphone or tablet battery last longer!" is causing the problem.
Still, the most terrifying thing about false accusations of Google Play policy violations is the following: the termination of your Developer account. Your indie dev future is actually in the hands of bots and uninformed half-bot reviewers.
My original community help post (False Deceptive Behavior Policy violation, app doesn't claim features impossible to implement) was locked, so I have created a new one here:
False Deceptive Behavior Policy violation, part II.
Update 2024.09.24:
My appeal was rejected, unsurprisingly, with threats of a complete suspension of the developer account included.
The app will remain free and open-source, and it will be available on alternative app stores. It's time to move away from Google.