Raulete's rants about technology and everything @raulete - Tumblr Blog

True Love #valentines #foreveralone #beerislove (en cervecería Baden Baden)

maloql-deactivated20190131

What you see is a myosin protein dragging an endorphin along a filament to the inner part of the brain’s parietal cortex which creates happiness. Happiness. You’re looking at happiness.

sarahseeandersen

tastefullyoffensive

Those were the day. (by Sarah Andersen)

Seguro en su guarida de cartón. (en Ciudad Lineal, Madrid, Spain)

business email glossary

thanks in advance: get this done by the time i press "send"

thanks for your interest: why'd you have to bring this up

would you be so kind: fucking do it

best: i have never physically met you

all best: this conversation is over

all my best: i wish you would die

happy to help: this is the easiest thing in my inbox

i hope this helps: i've done all i'm willing to do

i did a bit of research: i googled it, because you're too lazy to

sorry to chase: answer my email

so sorry to chase: answer my FUCKING email

i am really sorry for being a pest but: i am LIVID that you are ignoring me

please contact my colleague: this isn't my problem

i'm copying in my colleague: this isn't my problem and i am thrilled about it

i'll check and get back to you: i might forget to

i'll let you know when i hear anything: i will forget to

can you check back with me in a week?: i'm hoping you will forget to

per our earlier conversation: i just yelled at you on the phone

great to chat just now: you just yelled at me on the phone

thanks!: i'm not mad at you

thanks!!: please don't be mad at me

thanks!!!: i'm crying at my desk

please advise: this might be your fault

kindly advise: this is entirely your fault

mind if i swing by?: i'm already in the elevator

can you confirm for me: you told me before and i deleted the email

sorry if that was unclear: i think you're an idiot

let me know if you need anything else: please never contact me again

fkukso

Science Combat

By Diego Sanches.

samusdolan

Man, Tesla OP.

El espionaje industrial, cada día más sofisticado. #distrust #evilbird (en IBM Madrid)

#distrust #evilbird

Now with face. #reyrules #bb8rolls #kilocrybaby #instagramn00b #nomint (en Madrid, Spain)

#instagramn00b #kilocrybaby #nomint #bb8rolls #reyrules

No Mint #reyrules #bb8rolls #kilocrybaby (en Madrid, Spain)

#kilocrybaby #bb8rolls #reyrules

quellish

How on Earth the Facebook iOS Application is so large

Recently someone on reddit asked “How on earth is the Facebook app size so large ?”. The person asking the question realized that the ~100Mb compressed App Store archive wasn’t all assets - a very large portion was the application binary.

How do you answer that question? You quickly reverse engineer the application!

1 Download the binary to a jailbroken device from the App Store

2 Find the application on the device.

SSH into the device and find the application container on the filesystem:

find / -type d -iname "SomeApp*.app"

3 Decrypt the binary

Install dumpdecrypted on the device. Follow the instructions for using it.

4 Get the files off the device using scp or rsync.

In most cases you will want the application container, the decrypted binary, and the application data container (i.e. what it writes out to the filesystem).

At this point you have the decrypted binary and it’s files. You can now run class-dump on the binary and output a directory of header files for all the classes in the binary, or you can use a disassembler like IDAPro or Hopper to easily see all the classes, symbols, etc.

In the case of the Facebook application, there are more than 18,000 classses in the application:

There is a LOT of crap in there. Even a “FBFeedAwesomeizer” - which alone is a collection of 74 classes and protocols.

This is why the application binary itself is over 114Mb.

raulete

Object-oriented Programing at its best.

mllekarensac

Meh…

PS: Small daily exercise, comic drawn in 30 min

Pixar, 1995: What if toys had feelings

Pixar, 1998: What if bugs had feelings

Pixar, 2001: What if monsters had feelings

Pixar, 2003: What if fish had feelings

Pixar, 2004: What if superheroes had feelings

Pixar, 2006: What if cars had feelings

Pixar, 2007: What if rats had feelings

Pixar, 2008: What if robots had feelings

Pixar, 2009: What if dogs had feelings

Pixar, 2012: What if Scotland had feelings

Pixar, 2015: WHAT IF FEELINGS HAD FEELINGS

This is (yet another reason) why we old schoolers are not too keen on Linux

This is a an example of Linux and its device naming creativity I had not previously come accross yet.

I installed Debian 8 (in an VM). I setted up LVM through the installation program.

Supposedly, root was to be in logical volume "root" inside volume group "workzone-vg".

In good old HP-UX (Linux LVM is a confessed copy of HP-UX LVM, although with several improvements), that would mean the block device for that logical volume vould be always refered as /dev/workzone-vg/root.

Linux thinks othewise. Unique device special files are against Linux tastes it seems.

This is what appears in /etc/fstab. I am moreless used to this format, although I do not like it:

raul@workzone:~$ awk '$2 == "/"' /etc/fstab /dev/mapper/workzone--vg-root / ext4 errors=remount-ro 0 1

But look, this is what is new to me, what appears if I use "df":

raul@workzone:~$ df -k / Filesystem 1K-blocks Used Available Use% Mounted on /dev/dm-0 19382140 4319644 14054880 24% /

WTF?

It has an explanation. The Linux LVM software itself comprises the userspace adminsitration tools and the on disk metadata storage format, that is the headers in the physical volumes that describe the volume group configuration.

But the actual block devices created ar backed up by a generic subsystem, the "device-mapper".

This subsystem uses the /dev/dm-0 special file and also generates the /dev/mapper/workzone--vg-root symbolic link to it. It follows the instructions of the Linux LVM module, which is who creates the /dev/workzone/root symbolic link to /dev/dm-0.

raul@workzone:~$ ls -l /dev/workzone-vg/root /dev/mapper/workzone--vg-root /dev/dm-0 brw-rw---- 1 root disk 254, 0 Jun 17 09:47 /dev/dm-0 lrwxrwxrwx 1 root root 7 Jun 17 09:47 /dev/mapper/workzone--vg-root -> ../dm-0 lrwxrwxrwx 1 root root 7 Jun 17 09:47 /dev/workzone-vg/root -> ../dm-0

So, technically, everything makes all the sense in the world.

But I do not find it too user friendly.

In fact, if "df" contradicts both /etc/fstab and "mount" about the device where a filesystem resides, that is not a "good" behavior.

IMHO.