Still better if the manufacturer has too few words to compose names and uses them ALL. Especially when looking for the firmware for *your* model...
Sony Xperia Pro Sony Xperia Mini Sony Xperia Mini Pro Sony Xperia X10 Mini Sony Xperia X10 Pro Sony Xperia X10 Mini Pro
Xiaomi Mi 5 Xiaomi Mi 5s Xiaomi Mi 5s Plus Xiaomi Mi 5X Xiaomi Redmi 5 Xiaomi Redmi 5 Plus Xiaomi Redmi 5A Xiaomi Note 5A Xiaomi Redmi Note 5 Xiaomi Redmi Note 5 Pro Xiaomi Redmi Note 5 AI Dual Camera
SIM cards die over time. 10+ years, you're lucky it still works. And new cards have extra cuts so you can 'extract' mini, micro, or nano as you need, then push it back into the frame and put into a larger slot. (or even not extract from the whole big credit card sized SIM card and put into an antique phone that accepted these.)
In a lot of cases the insurance agent will give you advice how to reduce your premium by applying simple safety tips that will reduce your risk - and their risk to pay your claims.
In rare cases the insurance agency will take it upon themselves to fund certain safety features in public space, just to reduce the value of claims they must pay due to lack of these features. And lobby the lawmakers to mandate safety features that will reduce their costs.
What program relies on those, **and** would benefit from files placed in Dropbox directory?
Remember Dropbox is for storing/sharing your personal data files. It normally resides as a subdirectory of your ~home or "My Documents". It's not NFS or Samba where you can share the same binaries between many computers, share printers and other shit. It's for storing data you expect to share between different devices.
If you moved the data from the computer you renamed it on, to the one where it "broke", using a thumb drive, you'd lose these attributes too.
> That and making sure no other application is writing at the same time Dropbox is reading or vice versa.
Recheck the file after reading. Sync newest version. Currently, Dropbox most happily kept repeatedly syncing a file I was downloading, as it kept growing. It was most definitely open for writing the whole time. It was something annoying but not critical.
If Dropbox is currently writing a file, it's the reading program's (or the user's) problem to make sure the file is complete and synced.
> Or how would you recommend to sync a file containing alternate data streams to a file system that returns an error code when an application attempts to write one?
Two approaches.
1: don't care. Keep the record of the minimum set of features that is supported by every semi-sane filesystem, say, Fat32. Set the rest to defaults if fetching a new file from the server. Don't touch the attributes if you don't know them. 99% of users will be perfectly happy, the rest will choose a different solution.
2: maximum reach. Do add support for any features of the OS you may imagine. Record every meta-feature that is currently present in the file into database of files - on server and synced into.dropbox dir or wherever Dropbox holds its indices. When writing, apply any attributes that are present in the DB, don't worry if you can't. If the attribute is missing in the local copy, just don't overwrite it with NULL in the db so if you sync back into the 'featureful' FS it will have the extended attributes as before.
And 3. Anything in between. Store and retrieve as many attributes as you wish, fill the rest with defaults.
So your 'alternate data streams' file will have its primary data stream in the file on disk, the rest in DB if the devs want to support them. If they don't, the extra streams won't propagate across Dropbox cloud copy; will be left alone locally.
A bunch of Dropbox features are written in Python; it's a layer on top of the base engine. Mostly bloat you really don't want and don't need but they felt they needed to fix what wasn't broken and kept adding that shit.
and third, you read it up to your allowed quota and then stop, 'storage space exceeded', bye. If a user really, really wants to shoot themselves in the foot, let them. You have no valid reason to place the/dev/zero pseudo-file in your Dropbox directory.
> Dropbox is run by retards who have no clue about proper software development.
It is. My phone died on my trip and I had to buy some other quick; went for a cheapo that has 4GB of internal flash, 3 of which are preloaded with OS and various crapware. There's 1GB for user apps and data left. After mandatory updates of the built-in apps and installing some bare essentials (including Dropbox), I still had some 450MB free. I installed Dropbox to download the files I had on the old phone and I would need, like bus schedules at the destination, where network coverage was too dodgy.
Nope. Can't make an 80KB file available offline through Dropbox. You need at least 500MB of space on your device. Free up some space. Oh, and I don't give a fuck that you still have 14GB free on your SD card. No 500M internal storage free, no offline files for you!
Dropbox made some really dumb design decisions early on, tying the program way deeper into the OS works than it really needed, and suddenly they discovered that if you dig all the way through the one uniform friendly abstraction layer meant to be used by everyone and sufficient to everyone, you suddenly discover there are many different variants of works down below, of things you weren't supposed to touch in the first place. And they change a lot, and are hard to use.
And now they try to pin the blame on someone else.
Read file, write file, check timestamp. That's all Dropbox needs. All filesystems provide this through uniform OS calls. Why in the world does Dropbox care what filesystem it's running on? Where in their twisted designer minds did they come up with features that dig so deep below the basic userspace abstraction layer they'd rather lose users than just keep things simple.
If you load a shotgun shell with gravel instead of buckshot, it will be only slightly less lethal. The metal base on a shotgun shell is metal for convenience of assembly, not necessity. Instead of the cap, you can use an "unsafe" match head.
A Gatling isn't automatic. The energy to operate it comes from a crank, or a motor, or a hydraulic drive. No drive = no shoot, no matter how many rounds you have.
So if I make the gun's reload mechanism powered by any other energy source than chemical energy of the cartridge, that makes it non-automatic? Like, GAU-8/A Avenger is a 30 mm hydraulically driven seven-barrel Gatling-style autocannon shooting 3,900 30×173 mm rounds per minute, the gun around which the A-10 "Warthog" airplane was built, is not automatic?
Why'd you choose one of the hardest out there? Converting AK to full auto without semi-auto option takes like 5 minutes with no tools, just a piece of wire to tie two parts together. There's a book on Amazon, "Full-Auto Conversion Of The SKS Rifle." To convert FN FNC you need to make this kind of part. This all within 10 minutes of googling.
BTW, converting AR to full-auto with no semi-auto option is supposedly not all that hard either.
...if that. Obtaining parts that modify guns into full auto, or modifying them by yourself isn't all that hard, and if you're going to do a mass shooting you don't really care about legality of what you do. The bump stocks are an easily accessible, half-assed solution that requires holding the gun just right so that it shoots like full auto, and not as firmly as with real full auto - resulting in accuracy going to shit. Without bump stocks the shooters would quite likely seek out genuine full auto - and that would result in more people injured or killed.
Slashdot Mirror
Still better if the manufacturer has too few words to compose names and uses them ALL. Especially when looking for the firmware for *your* model...
Sony Xperia Pro
Sony Xperia Mini
Sony Xperia Mini Pro
Sony Xperia X10 Mini
Sony Xperia X10 Pro
Sony Xperia X10 Mini Pro
Xiaomi Mi 5
Xiaomi Mi 5s
Xiaomi Mi 5s Plus
Xiaomi Mi 5X
Xiaomi Redmi 5
Xiaomi Redmi 5 Plus
Xiaomi Redmi 5A
Xiaomi Note 5A
Xiaomi Redmi Note 5
Xiaomi Redmi Note 5 Pro
Xiaomi Redmi Note 5 AI Dual Camera
SIM cards die over time. 10+ years, you're lucky it still works. And new cards have extra cuts so you can 'extract' mini, micro, or nano as you need, then push it back into the frame and put into a larger slot. (or even not extract from the whole big credit card sized SIM card and put into an antique phone that accepted these.)
> Now what am I supposed to do?
Buy a different phone, that's what!
Sometimes it does prevent harm.
In a lot of cases the insurance agent will give you advice how to reduce your premium by applying simple safety tips that will reduce your risk - and their risk to pay your claims.
In rare cases the insurance agency will take it upon themselves to fund certain safety features in public space, just to reduce the value of claims they must pay due to lack of these features. And lobby the lawmakers to mandate safety features that will reduce their costs.
Oh. I didn't know. An interesting option.
What program relies on those, **and** would benefit from files placed in Dropbox directory?
Remember Dropbox is for storing/sharing your personal data files. It normally resides as a subdirectory of your ~home or "My Documents". It's not NFS or Samba where you can share the same binaries between many computers, share printers and other shit. It's for storing data you expect to share between different devices.
If you moved the data from the computer you renamed it on, to the one where it "broke", using a thumb drive, you'd lose these attributes too.
BTW, wrote about the experience with Dropbox's built in feedback, "what I don't like".
Spent several emails attaching screenshots as demanded and explaining details, to hear "this is expected behavior." Yeah, no shit.
Unfortunately, my primary device is a Linux laptop. Dropbox dropping Linux means I'll be moving to a different platform soon.
Just like it did so far. Detect the file got deleted, detect a new file was created, sync the new file.
> That and making sure no other application is writing at the same time Dropbox is reading or vice versa.
Recheck the file after reading. Sync newest version. Currently, Dropbox most happily kept repeatedly syncing a file I was downloading, as it kept growing. It was most definitely open for writing the whole time. It was something annoying but not critical.
If Dropbox is currently writing a file, it's the reading program's (or the user's) problem to make sure the file is complete and synced.
> Or how would you recommend to sync a file containing alternate data streams to a file system that returns an error code when an application attempts to write one?
Two approaches.
1: don't care. Keep the record of the minimum set of features that is supported by every semi-sane filesystem, say, Fat32. Set the rest to defaults if fetching a new file from the server. Don't touch the attributes if you don't know them. 99% of users will be perfectly happy, the rest will choose a different solution.
2: maximum reach. Do add support for any features of the OS you may imagine. Record every meta-feature that is currently present in the file into database of files - on server and synced into .dropbox dir or wherever Dropbox holds its indices. When writing, apply any attributes that are present in the DB, don't worry if you can't. If the attribute is missing in the local copy, just don't overwrite it with NULL in the db so if you sync back into the 'featureful' FS it will have the extended attributes as before.
And 3. Anything in between. Store and retrieve as many attributes as you wish, fill the rest with defaults.
So your 'alternate data streams' file will have its primary data stream in the file on disk, the rest in DB if the devs want to support them. If they don't, the extra streams won't propagate across Dropbox cloud copy; will be left alone locally.
...or I'll just switch to any other of dozens of cloud storage services.
A bunch of Dropbox features are written in Python; it's a layer on top of the base engine. Mostly bloat you really don't want and don't need but they felt they needed to fix what wasn't broken and kept adding that shit.
and third, you read it up to your allowed quota and then stop, 'storage space exceeded', bye. If a user really, really wants to shoot themselves in the foot, let them. You have no valid reason to place the /dev/zero pseudo-file in your Dropbox directory.
> Dropbox is run by retards who have no clue about proper software development.
It is. My phone died on my trip and I had to buy some other quick; went for a cheapo that has 4GB of internal flash, 3 of which are preloaded with OS and various crapware. There's 1GB for user apps and data left. After mandatory updates of the built-in apps and installing some bare essentials (including Dropbox), I still had some 450MB free. I installed Dropbox to download the files I had on the old phone and I would need, like bus schedules at the destination, where network coverage was too dodgy.
Nope. Can't make an 80KB file available offline through Dropbox. You need at least 500MB of space on your device. Free up some space.
Oh, and I don't give a fuck that you still have 14GB free on your SD card. No 500M internal storage free, no offline files for you!
Dropbox made some really dumb design decisions early on, tying the program way deeper into the OS works than it really needed, and suddenly they discovered that if you dig all the way through the one uniform friendly abstraction layer meant to be used by everyone and sufficient to everyone, you suddenly discover there are many different variants of works down below, of things you weren't supposed to touch in the first place. And they change a lot, and are hard to use.
And now they try to pin the blame on someone else.
What the fuck.
Read file, write file, check timestamp. That's all Dropbox needs. All filesystems provide this through uniform OS calls. Why in the world does Dropbox care what filesystem it's running on? Where in their twisted designer minds did they come up with features that dig so deep below the basic userspace abstraction layer they'd rather lose users than just keep things simple.
> Statist states are going to state.
ftfy
If you load a shotgun shell with gravel instead of buckshot, it will be only slightly less lethal. The metal base on a shotgun shell is metal for convenience of assembly, not necessity. Instead of the cap, you can use an "unsafe" match head.
So if I make the gun's reload mechanism powered by any other energy source than chemical energy of the cartridge, that makes it non-automatic? Like, GAU-8/A Avenger is a 30 mm hydraulically driven seven-barrel Gatling-style autocannon shooting 3,900 30×173 mm rounds per minute, the gun around which the A-10 "Warthog" airplane was built, is not automatic?
So, any state can legalize slavery and it will be legal because state rights outweigh the constitution?
> AR
Why'd you choose one of the hardest out there? Converting AK to full auto without semi-auto option takes like 5 minutes with no tools, just a piece of wire to tie two parts together. There's a book on Amazon, "Full-Auto Conversion Of The SKS Rifle." To convert FN FNC you need to make this kind of part. This all within 10 minutes of googling.
BTW, converting AR to full-auto with no semi-auto option is supposedly not all that hard either.
Another update: The shooter was a member of Anti-Trump resistance. So, extremist Leftist.
Somehow, that wasn't what the shooter praised. The killer was a member of "Anti-Trump Resistance".
Oh, and violent sports (NFL) and violent video games (Madden).
...if that. Obtaining parts that modify guns into full auto, or modifying them by yourself isn't all that hard, and if you're going to do a mass shooting you don't really care about legality of what you do. The bump stocks are an easily accessible, half-assed solution that requires holding the gun just right so that it shoots like full auto, and not as firmly as with real full auto - resulting in accuracy going to shit. Without bump stocks the shooters would quite likely seek out genuine full auto - and that would result in more people injured or killed.