🌈 Social 📸 Photography 🌈

Kevin Karhan :verified:<a href="https://chaos.social/@LaF0rge" class="u-url mention" rel="nofollow noopener" target="_blank">@LaF0rge</a> <a href="https://mastodon.social/@stman" class="u-url mention" rel="nofollow noopener" target="_blank">@stman</a> <a href="https://mastodon.ie/@kDelta" class="u-url mention" rel="nofollow noopener" target="_blank">@kDelta</a> <a href="https://infosec.exchange/@Sempf" class="u-url mention" rel="nofollow noopener" target="_blank">@Sempf</a> obviously that's why it <a href="https://infosec.space/@kkarhan/114863029952059372" rel="nofollow noopener" target="_blank">was discontinued for a time</a> in <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#Germany</a>, as it was considered as obsolete as <a href="https://infosec.space/tags/HSCSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#HSCSD</a> is in light of faster standards that - even without guaranteed bandwith - will yield higher throughput.<ul><li>Obviously <a href="https://infosec.space/tags/CellBroadcast" class="mention hashtag" rel="nofollow noopener" target="_blank">#CellBroadcast</a> will necessitate a constant bandwith allocation for functionality as it's design is based upon repeating a message until it's transmissiom being removed.</li></ul>Still, even in contended <a href="https://infosec.space/tags/spectrum" class="mention hashtag" rel="nofollow noopener" target="_blank">#spectrum</a> this is manageable, espechally since most <a href="https://infosec.space/tags/MNOs" class="mention hashtag" rel="nofollow noopener" target="_blank">#MNOs</a> only maintain vestigal <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener" target="_blank">#2G</a> or <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener" target="_blank">#3G</a> infrastructure solely for <a href="https://infosec.space/tags/emergency" class="mention hashtag" rel="nofollow noopener" target="_blank">#emergency</a> coverage and reliability, as <a href="https://www.youtube.com/watch?v=Q6qb9dml6So" rel="nofollow noopener" target="_blank">most phones will call emergency services over 2G and 3G</a> and not via <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a>. <ul><li>To add insult to injury, most BSCs will downgrade to 2G-only service by default in case of power loss to maximize UPS range and in the case of <a href="https://infosec.space/tags/NewZealand" class="mention hashtag" rel="nofollow noopener" target="_blank">#NewZealand</a> even switch off all services but <a href="https://infosec.space/tags/SMS" class="mention hashtag" rel="nofollow noopener" target="_blank">#SMS</a> & <a href="https://infosec.space/tags/EmergencyServicesCalling" class="mention hashtag" rel="nofollow noopener" target="_blank">#EmergencyServicesCalling</a> to enshure people in need can get their calls out, as the population is instructed to use SMS for person-to-person communication (as SMS is a low-priority, non-realtime service using excess bandwith and thus not compete with calling like <a href="https://infosec.space/tags/EDGE" class="mention hashtag" rel="nofollow noopener" target="_blank">#EDGE</a> and <a href="https://infosec.space/tags/CSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSD</a> would.</li></ul>

Kevin Karhan :verified:[<a href="https://infosec.space/tags/TLDR" class="mention hashtag" rel="nofollow noopener" target="_blank">#TLDR</a>: JUST TELL ME IF YOUR TABLET CAN DO <a href="https://infosec.space/tags/CALLS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CALLS</a>!]<a href="https://infosec.space/tags/DearVendors" class="mention hashtag" rel="nofollow noopener" target="_blank">#DearVendors</a> of <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a>-<a href="https://infosec.space/tags/Tablets" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tablets</a>:Off all the <a href="https://infosec.space/tags/Functions" class="mention hashtag" rel="nofollow noopener" target="_blank">#Functions</a> you can put into a <a href="https://infosec.space/tags/Specifications" class="mention hashtag" rel="nofollow noopener" target="_blank">#Specifications</a> Sheet of your Devices there's one you should ALWAYS answer clearly on your <a href="https://infosec.space/tags/Website" class="mention hashtag" rel="nofollow noopener" target="_blank">#Website</a>:DOES YOUR TABLET [with <a href="https://infosec.space/tags/4G" class="mention hashtag" rel="nofollow noopener" target="_blank">#4G</a> / <a href="https://infosec.space/tags/5G" class="mention hashtag" rel="nofollow noopener" target="_blank">#5G</a> / …) SUPPORT MAKING PHONE CALLS?<ul><li>NOT "It can run <a href="https://infosec.space/tags/WhatsApp" class="mention hashtag" rel="nofollow noopener" target="_blank">#WhatsApp</a>" (or whatever shitty <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCSS</a> for <a href="https://infosec.space/tags/VoIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoIP</a> you think of)...</li><li>NOT "It can do <a href="https://infosec.space/tags/CSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSD</a> / <a href="https://infosec.space/tags/HSCSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#HSCSD</a> / <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener" target="_blank">#2G</a> / <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener" target="_blank">#3G</a> /..."</li><li>But DOES IT SUPPORT <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener" target="_blank">#GSM</a>-<a href="https://infosec.space/tags/Calls" class="mention hashtag" rel="nofollow noopener" target="_blank">#Calls</a> (and/or <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a>)??</li></ul>Like: IS IT TOO MUCH TO ASK TO HAVE THAT INFO IN THE SPECSHEETS?You're obviously able to list all the <a href="https://infosec.space/tags/Codecs" class="mention hashtag" rel="nofollow noopener" target="_blank">#Codecs</a> natively supported and the user-available storage as well as supported Frequency Bands, WWAN modes, WiFi channel width and the Display Glass vs. Panel dimensions including DPI of the latter and whether or not it has a hall effect sensor to detect your overpriced 1st party tablet covers!Now some folks may ask: "WHY does this matter?" or outright dismiss this as a problem.Listen: Not everyone is able or willing to carry two devices when 1 SHOULD BE ENOUGH and also some places (i.e. <a href="https://infosec.space/tags/Turkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#Turkey</a>) have <a href="https://infosec.space/tags/ImportRestrictions" class="mention hashtag" rel="nofollow noopener" target="_blank">#ImportRestrictions</a> re: <a href="https://infosec.space/tags/MobileDevices" class="mention hashtag" rel="nofollow noopener" target="_blank">#MobileDevices</a>, so having more than 1 <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMEI</a> is already a "NOPE!" by the authorities.<ul><li>Also this isn't something one can "fix" post-purchase like installing <a href="https://infosec.space/tags/VLC" class="mention hashtag" rel="nofollow noopener" target="_blank">#VLC</a> to decode some obscure file format in Software: Either the <a href="https://infosec.space/tags/Baseband" class="mention hashtag" rel="nofollow noopener" target="_blank">#Baseband</a> and <a href="https://infosec.space/tags/ROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#ROM</a> support <a href="https://infosec.space/tags/PhoneCalls" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneCalls</a> or they don't!</li></ul>So why do NONE of the <a href="https://infosec.space/tags/Tablet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tablet</a> manufacturers allow to <a href="https://infosec.space/tags/search" class="mention hashtag" rel="nofollow noopener" target="_blank">#search</a> or <a href="https://infosec.space/tags/filter" class="mention hashtag" rel="nofollow noopener" target="_blank">#filter</a> for that???<ul><li>Bonus points if you have lazy fucks like <a href="https://infosec.space/tags/HMD" class="mention hashtag" rel="nofollow noopener" target="_blank">#HMD</a> (aka. <a href="https://infosec.space/tags/Nokia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nokia</a>) who literally copy the <a href="https://infosec.space/tags/Safety" class="mention hashtag" rel="nofollow noopener" target="_blank">#Safety</a> & <a href="https://infosec.space/tags/Useage" class="mention hashtag" rel="nofollow noopener" target="_blank">#Useage</a> information for all <a href="https://infosec.space/tags/Smartphones" class="mention hashtag" rel="nofollow noopener" target="_blank">#Smartphones</a> and <a href="https://infosec.space/tags/Tablets" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tablets</a> and don't even bother to change "Mobile Phone" for "Tablet".</li></ul>NO, instead one has to download an obscenely huge <a href="https://infosec.space/tags/PDF" class="mention hashtag" rel="nofollow noopener" target="_blank">#PDF</a> just to then <a href="https://downloadcenter.samsung.com/content/UM/202410/20241010132004137/SM-X11X_X21X_UM_Open_UU_Ger_Rev.1.2_240925.pdf" rel="nofollow noopener" target="_blank">read on page 34</a> that for any "<a href="https://infosec.space/tags/telephony" class="mention hashtag" rel="nofollow noopener" target="_blank">#telephony</a>" function you NEED YET ANOTHER DEVICE FROM THE SAME MANUFACTURER AND HAVE TO SIGNUP WITH AN ACCOUNT and even that level of <a href="https://infosec.space/tags/abuse" class="mention hashtag" rel="nofollow noopener" target="_blank">#abuse</a> WON'T GUARANTEE THAT IT WORKS...<ul><li>I mean, come on, this ain't some obscure functionality like <a href="https://infosec.space/tags/OMAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMAPI</a> to do some "evil sourcery" like managing an <a href="https://infosec.space/tags/eSIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#eSIM</a> that is in a <a href="https://infosec.space/tags/SIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIM</a>-Card form factor!</li></ul>Pretty shure A LOT of other folks have the same question and ain't willing to get yet another device & <a href="https://infosec.space/tags/SIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIM</a> just to recieve the occasional call because <a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterates</a> can't be assed to send an <a href="https://infosec.space/tags/eMail" class="mention hashtag" rel="nofollow noopener" target="_blank">#eMail</a> or learn <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMEMO</a> to message one...<ul><li>Obviously they same manufacturers are able and willing to specify f-stops of the built-in cameras and list EVERY SINGLE <a href="https://infosec.space/tags/WEARABLE" class="mention hashtag" rel="nofollow noopener" target="_blank">#WEARABLE</a> they made and certify as 'compatible' with, as if anyone is gonna take their non-<a href="https://infosec.space/tags/waterproof" class="mention hashtag" rel="nofollow noopener" target="_blank">#waterproof</a> <a href="https://infosec.space/tags/Tablet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tablet</a> for a marathon or god forbid triathlon...</li></ul><a href="https://infosec.space/tags/Rant" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rant</a> <a href="https://infosec.space/tags/TechSupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechSupport</a> <a href="https://infosec.space/tags/Technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#Technology</a> <a href="https://infosec.space/tags/Support" class="mention hashtag" rel="nofollow noopener" target="_blank">#Support</a> <a href="https://infosec.space/tags/Sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sysadmin</a> <a href="https://infosec.space/tags/Procurement" class="mention hashtag" rel="nofollow noopener" target="_blank">#Procurement</a> <a href="https://infosec.space/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> <a href="https://infosec.space/tags/SpecSheet" class="mention hashtag" rel="nofollow noopener" target="_blank">#SpecSheet</a> <a href="https://infosec.space/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tech</a>

Kevin Karhan :verified:<a href="https://infosec.space/@sabi" class="u-url mention" rel="nofollow noopener" target="_blank">@sabi</a> for the most part: <a href="https://infosec.space/tags/HSCSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#HSCSD</a> @ 115,2 kBit/s (mostly due to throttling on <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener" target="_blank">#3G</a> networks which peaked at 7,2MBit/s...But the absolute first was 64kBit/s <a href="https://infosec.space/tags/ISDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISDN</a>... <a href="https://en.wikipedia.org/wiki/Circuit_Switched_Data" rel="nofollow noopener" translate="no" target="_blank">https://en.wikipedia.org/wiki/Circuit_Switched_Data</a> <a href="https://en.wikipedia.org/wiki/UMTS" rel="nofollow noopener" translate="no" target="_blank">https://en.wikipedia.org/wiki/UMTS</a>

Alexander Kurz :camera:<a href="https://mastodon.social/@pallenberg" class="u-url mention" rel="nofollow noopener" target="_blank">@pallenberg</a> bei mir war es das <a href="https://kurz.social/tags/SonyEricsson" class="mention hashtag" rel="nofollow noopener" target="_blank">#SonyEricsson</a> <a href="https://kurz.social/tags/P800" class="mention hashtag" rel="nofollow noopener" target="_blank">#P800</a>. Ich war so begeistert von der Technologie, dass ich das Wagnis eingegangen bin und mir damals noch vor Marktstart ein Developer-Kit bestellt habe. Es kam im Dezember 2002. Verbunden hat man sich damals mit <a href="https://kurz.social/tags/GPRS" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPRS</a> oder wenn es „schnell“ sein sollte mit der GSM-Kanalbündelung <a href="https://kurz.social/tags/HSCSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#HSCSD</a>. Und schon damals gab es erste experimentelle Apps für Push-Mail.

Recent searches

Search options

Administered by:

Server stats:

#hscsd