!technology
@lemmy.mlhttps://apnews.com/article/machine-gun-conversion-devices-justice-department-7bcdd06bcccc987c90da494f746d5765
Justice Department officials are turning to the 3D-printing industry to help stop the proliferation of tiny pieces of plastic transforming semi-automatic weapons into illegal homemade machine guns on streets across America.
https://www.techspot.com/news/104634-lexar-unveils-world-first-sd-cards-made-316.html
https://blogsystem5.substack.com/p/windows-nt-vs-unix-design
NT is often touted as a "very advanced" operating system. Why is that? What made NT better than Unix, if anything? And is that still the case?
https://qz.com/huawei-trifold-phone-preorders-china-apple-iphone-16-1851643088
The Chinese smartphone maker has outpaced Apple in China since releasing its Mate 60 Pro smartphone series
https://cohost.org/staff/post/7611443-cohost-to-shut-down
also the August 2024 financial update, but I’m trying not to bury the lede. Hi everyone, We have come to the decision to cease operations of cohost and anti software software club due to lack of funding and burnout. As of today, none of us are being paid for our labor1; all of our money in the bank, and any money coming in from people who buy our merch or don’t cancel cohost plus, is going towards servers and operations — paying the bills so we can turn the lights off with as little disruption as possible. cohost will become read-only on Tuesday, October 1st. At this time, we will make best-effort attempts to keep the servers online through the end of 2024. Development focus has immediately shifted to data export. We have offered minimal data export for GDPR compliance for a while now, but this is a barebones system that doesn’t meet our quality standards. We will be improving this system over the next few weeks and will issue full data exports for all users when the site goes read-only. We will continue to offer downloads of your data export through the end of the read-only period. When the read-only period concludes, we will delete all of your data from our servers without a backup. Even now we want to reiterate that we think “data brokerage” and other common practices of the software industry are inimical to who we are as people, and we would never consider selling your data to others or asserting any rights to stuff you posted under any circumstance. Majority control of the cohost source code will be transferred to the person who funded the majority of our operations, as per the terms of the funding documents we signed with them; Colin and I will retain small stakes so we have some input on what happens to it, at their request. ---------------------------------------- So, what happened? If you’ve read our financial updates, you know that we have never been profitable. This isn’t surprising, even with a team of four; social media is a notoriously unprofitable industry. We had planned to bring in new revenue with eggbux (our tipping and subscription product) but policy changes from Stripe forced us to cancel earlier this year. Since then, we’ve struggled to fill the revenue and morale gap. Colin and I have been doing this for five years, Aidan for three, Kara for nearly two. We’ve been at or over capacity on moderation, engineering, and general operations nearly this entire time. We have all been on-call 24/7/365 since we launched two and a half years ago. The day-to-day needs of just running the site meant developing alternative funding options wasn’t possible. MAU and MRR are down across the year. We’ve managed to build a social media platform that many of our users love, but we just don’t have enough users and we don’t have the resources to safely scale up. It’s important to know when to call it quits. We’re grateful for all the incredible things y’all have created on cohost. We’re grateful for eggbug. We’re grateful that we were able to try and show a better path for social media, even if it didn’t work out exactly as we would have liked. We’re going to do our best to keep things online through the end of the year with the money we have, but we might need additional funding to keep things up until then. If you would be able to contribute funds if necessary, please e-mail us at corp@antisoftware.club [corp@antisoftware.club]. Thank you all for having used cohost. We’ll see you around. :eggbug: ~ jae (and colin, and aidan, and kara) ---------------------------------------- TIMELINE * Immediately: self-service account deletions are available in the settings page [https://cohost.org/rc/user/settings]. account sign-up and activation is no longer available. Please note that if you delete your account before receiving a data export, you will not receive one; there won’t be any data left for us to export. * October 1, 2024: cohost will become read-only. all cohost plus subscriptions will be cancelled. account deletions will remain available. * starting October 1, 2024: we will begin processing data exports for all users. we expect this process to take some time. once your export is ready, you will receive an e-mail with a link to download it. data export downloads will remain available until the servers shut down on December 31. * December 31, 2024: cohost will go fully offline. all user data will be deleted on our way out the door. * January 1, 2025: we will set cohost.org [http://cohost.org] to redirect to the wayback machine2 to prevent link rot. this is something we will be paying for out of pocket since ASSC will no longer be an operating concern, but it’s max $100 per year total so it’s fine. FAQ this space intentionally left blank while we wait for people to frequently ask questions ---------------------------------------- AUGUST 2024 FINANCIAL UPDATE CategoryAs of August 31As of July 31% ChangeExpenses$41,605$41,0521.35%Income$16,307$28,405-42.59%Net income-$25,297-$12,647-100.03%Active subscribers3,0463,128-2.62%MRR$19,477$20,015-2.69%Subscriber churn rate3.18%3.07%3.58%Revenue per subscriber$6.39$6.40-0.16%MAU16,84618,612-9.49%MAU → Subscriber conversion rate18%16.8%7.14%Artist Alley listing weeks sold7389-17.98% Not great! ---------------------------------------- 1. on that note, we’re looking for new jobs. we’ll each be posting about that bit individually. 2. speaking of which, if you’re with archive team please reach out. we’d like to help make sure there’s a recent archive of all public posts but don’t know who to talk to.
I'm looking for a way to dump raw data from an entire phone or at least the sda
block to a PC, using a method other than adb pull
.
When I run adb pull /dev/block/sda sdaDump.img
, it creates a dump file. To find what I need, I have to search through this raw data using a Hex Editor
. If the dump comes from a fully functioning phone, I can usually find what I’m looking for because all the data is still intact.
However, I accidentally wiped the metadata
partition on my phone, so the decryption keys/files are gone. Now, because of that, some folders appear empty when checked with TWRP's File Manager, even though the actual files are still there.
If I create a dump now, the raw data in the file won't be the same as when the metadata
was present, and those folders weren't showing as empty.
Running adb pull /dev/block/sda sdaDump.img
now results in a dump where the Hex Editor
shows zeroes (no data) where these files should be.
Is there any alternative method to create a raw data dump of the sda
block or entire phone storage, that will capture that data as it is (not empty folders, but the data in them), even if it's encrypted?
I don't want to create the raw data dump onto the phone storage and then transfer it to a PC, but something that works like adb pull
, in the sense that it pulls the data from the phone directly onto a PC.
Thanks a lot in advance to everyone!
https://www.spacebar.news/repairable-phones-problem/
HMD's "sustainable" phones don't have software built to last.
https://werd.io/2024/threads-is-trading-trust-for-growth
Yesterday the Internet Archive lost its appeal in the digital lending case it’s been fighting for the last few years. In March 2020, the Internet Archive, a
I need to ask a small favor from the good people of Lemmy.ml Community.
In short, I accidentally wiped the metadata
partition on my Poco F3
and now I can't boot into the OS and access my data. I have a lot of pictures, videos and other stuff that I would hate to lose, because of a mistake. But all that is still on the phone, I just can't boot the phone to access it.
Thankfully, there is a way to fix this by creating a full backup of the phone with adb
, then using a HEX Editor to manually look through that gigantic file and try to find the files that were in that metadata partition.
A huge thanks to bluet33th, a user from XDA Forums, without whom I would be helpless and couldn't do any of this. It might be a bit complicated and manual process, but it is possible. He explained everything in great detail here, so check it out, especially if you are facing the same problem, this will help you tremendously: https://xdaforums.com/t/how-to-recover-data-if-metadata-partition-was-deleted.4686789/
In order to find these files and put them back where they belong, I need your help, because I have to know their names, exact sizes and at least part of their content, so that I can search for it. Because I'm searching for a specific text in a text file that is 128 GB in size.
I have already tried this on another Xiaomi phone, to make sure this procedure works on Xiaomi phones and it does, but that phone had HyperOS
with Android 14
and since every phone and android version is probably different, in order to be sure, I need this information specifically for Poco F3
with Android 13
.
It doesn't take long, but if you don't have the time to look inside your metadata
partition and tell me which files are inside of that partition and their sizes in bytes, you can just make a backup of the metadata
partition and sent it to me, and I'll do the rest of the work.
Here are the steps on how to create a backup:
TWRP
, then connect your phone to a PC, type cmd
inside Windows search and run cmd, then position cmd into your platform-tools
folder (if you flashed your ROM, you should already have the necessary drivers installed for the next steps to work). For example, if your platform-tools
folder on Windows is inside C:\platform-tools
, all you need to type into cmd is: cd C:\platform-tools
You can also just go inside your platform-tools
folder and type cmd
in the address bar and the cmd will start already positioned inside that folder.
adb devices
and you should see your device, if you do, that means that all the drivers are successfully installed and your phone is detected.adb pull /dev/block/by-name/metadata
metadata
inside C:\platform-tools
. That is the file that I'm looking for and as you can see, it takes just a few minutes to get it.You can skip the next steps (5 and 6), but I'll explain them, just in case someone wants to extract these files for themselves, so that you have them in case something like this happens to you. Of course, you can also proceed to extract the files and tell me their names and sizes.
Here is what you need to do:
Extract the content of the metadata
file, you can use a software like 7-Zip
. Go inside that extracted folder, then into vold > metadata_encryption > key
Inside of that key
folder, you should see a few files. These are the important files and save them somewhere safe in case you ever need them. Since I don't have them anymore, in order to recreate them, I need to know their exact names and sizes in bytes. You can check the size of every individual file by right clicking on the file and choosing Properties
. Then look under Size
, not Size on disk
, and in parenthesis, you should see the size in bytes.
Please, if you could check the size of every file and write down which file has what size. I would really appreciate it.
I'm specifically looking for someone who has a Poco F3
with Android 13
and MIUI
, because I'm not sure if HyperOS
changed something, so maybe the number of files or their size is different. But feel free to post the information even if you have HyperOS
, but please mention that, so that I am aware of it.
Thanks a lot for your help, it really means a great deal.
https://www.dexerto.com/tech/discord-lowers-free-upload-limit-to-10mb-storage-management-is-expensive-2887809/
Discord is lowering the upload limit for free users from 25MB to 10MB, citing operational and financial reasons.