U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
End of the first day at #FOSDEM2020
unique MACs 9103
4184 Linux x86_64
1514 Unknown
1077 Android
642 Mac OS X
600 Apple devices
365 iPhone
361 Darwin
290 Windows
23 Debian
19 Linux aarch64
8 Linux armv7l
8 Linux i686
6 OpenBSD
4 FreeBSD
1 Windows Phone 
uplink traffic: 6,154,983,996 packets input, -25,285,233,385,785 bytes 3,576,381,599 packets output, 9,982,205,744,645 bytes Video traffic only (!) 1,110,775,678 packets input, 971,999,795,662 bytes 2,230,286,981 packets output, 2,637,958,925,710 bytes
Why is @haikuOS listed as "unknown"? Where can we send patches to be properly identified?
I did add it and found ... one device. Could that be correct?
how do you check is it x86_64 or aarch64?
The HTTP user agent includes this and we can extract this on the router.
But they are a hot mess and clients can lie too... 
or one joker spoofing Windows phone!
I did consider that, but checking out the client it truly seems to be a Windows Phone... MAC checks out and such so 
How can you figure out it's Debian?
Because apt still uses http as transport and has APT Debian in the useragent 
We can only capture http data, so if all your other communication is encrypted then that's the only thing we can tell.
If you're running a bunch of agents calling home then we, and they, know more
Could you split « Linux x86_64 » a bit ?
If I captured, found and understood the distribution or device I do, otherwise that's the best I can do with the data
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
