- DNS block & SNI filtering: I expect BrightData to rotate the endpoints if this issues gains enough attention. It will take some time once all the apps embedding the SDK catch up, but if they're smart SDK may already have a backup C&C connection they will try to reach out to after prolonged unavailability of the current endpoints.
- TLS fingerprint: unless SDK pins it, it's the cheapest one to rotate continously.
- MDM solution: almost unattainable to private users; not clear how stable the SDK name is to rely on.
Not saying I have a better approach. It seems behavior like this should be explicitly banned on Apple/Google's side with immediate termination of their publisher accounts.
I tried Darktable and I don't doubt it's a powerful RAW editing software but it feels like to be effective with it you need to care about the software more than you do about photography. With Lightroom/Capture One etc. it's the opposite. Darktable is just too 'out there'
At this point I'd take anything but my guess is this will make windshield quite more expensive (and it's already not cheap to replace it due to the sensor array calibration on most newer cars).
Negative feedback is not lost, it's filtered. No one at the top is equipped to deal with the actual feedback from ICs, unless your org is 10 people in a bike shed.
This is not about enjoying or not enjoying jail. If you happen to live and work in Japan in a typical job, getting arrested and held within this process for 23 days almost certainly means you're getting fired because you essentially have no contact with the outside world and even if you manage to sneak a word out through your lawyer, most of the employment contracts have clauses to extent of automatic termination for both missing enough days and breaking moral character.
So even if the prosecution decides to drop your case, you're already fucked -- this is not how proper justice system should work.
First, the biggest issue r/n is the concern that external internet will be limited to a point of no return, for this meshtastic is quite useless because to go across the border you need powerful transmitters and risk of placing and maintaining them near the border. In russia this is not only risk of going to prison but also being literally shot if border patrol/FSB overreacts. Even if you're successful bandwidth is miniscule compared to what a modern country needs to communicate internationally.
Second, due to Ukraine piggybacking on cellular networks for drone targeting/control cell service is frequently disrupted by authorities in the areas of a likely attack (it's obviously as effective as this sounds compounded by general incompetence of the government). While they cannot shut it down completely because russia still doesn't want to go back to the stone age, this concern is largely non-existent for meshtastic though. If it becomes widely popular and coverage expands, it also could be used by Ukraine as a control network, and in this case I would expect russian authorities to just jam the whole frequency range and be done with it. So the moment it becomes viable alternative is the moment it will be shut down.
One of the use cases is pairing it up with ATAK or similar tactical awareness system during SAR operations by volunteer brigades in remote areas with spotty coverage by regular networks.
They absolutely are. Fun example: when Revolut launched in Japan few years back they had a period of a relatively explosive success (especially within the immigrant community), so most of the cards of the period were issued with the same expiration month and with the same IIN (I'm assuming specific to Japan as well) which left very little entropy and lead to brute-force attacks via merchants not requiring 3DS (Uber etc.). Within only one community (approx. 1.5k people) we have had a handful of a 100% verified cases when the card was compromised without any exposure at all (i.e. the card was not used online or offline).
In all cases Revolut promptly reverted the charges and eventually they did a complete reissue of the cards for Japanese market (not sure how they've got around the entropy issue: maybe they've randomized the expiry dates or spread out IINs some more).
- DNS block & SNI filtering: I expect BrightData to rotate the endpoints if this issues gains enough attention. It will take some time once all the apps embedding the SDK catch up, but if they're smart SDK may already have a backup C&C connection they will try to reach out to after prolonged unavailability of the current endpoints.
- TLS fingerprint: unless SDK pins it, it's the cheapest one to rotate continously.
- MDM solution: almost unattainable to private users; not clear how stable the SDK name is to rely on.
Not saying I have a better approach. It seems behavior like this should be explicitly banned on Apple/Google's side with immediate termination of their publisher accounts.
reply