infosec.space is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for info/cyber security-minded people. This instance blocks threads.net

Administered by:

Server stats:

49
active users

Public

For some reason I just remembered how the iPhone didn't even have an app store in the first version, and didn't get copy/paste until like the 3rd or 4th iOS version.

Public

TBH, the first couple iterations of the iPhone were really... Not very good. Which I guess goes to show you just how terrible cell phones were in that era. BlackBerry REALLY fucked up.

Public

@JessTheUnstill One of the big fuckups for BlackBerry was just the delays in getting BlackBerry 10, plus the Z10 and Q10, to market.

I got to use BB10 for a couple of months, and it was nice. It was built on QNX, with a modern swipe/gesture based UI built with Qt.

Arguably a better OS than the iOS and Android releases at that same time.

There was a feature called the Hub, which wax a unified inbox for your email messages, social posts, and text messages. Plus a modern app store, and separate personal/work profiles built into the OS.

There was a version without a physical keyboard (Z10) and with (Q10).

The problem is they didn't start working on it until 2010, and BB10 wasn't released until 2013.

For about two years before BB10 came out, BlackBerry didn't release any new phones.

Had BB10 come out earlier, it *might* have saved the company.

Public

@ajsadauskas @JessTheUnstill also 's was released as a accessory screen for their Phones, which gave it "-Effect" in terms of marketing.

  • Plus relying hard on business clients and their proprietary applianced mail systems and having big carriers upsell to business people made them look outdated & quite literally out of touch once went mainstream.

I mean, the hardware was never their problem and -Typists swear by their 's but BlackBerry's - just like 's - was just hideous to the point that devs like @fuchsiii didn't even want to try making for those devices.

  • Unlike fucking up by refusing to sell devices to , by the time RIM & came from their high horses, their market shares had been squeezed into mere "rounding errors" by and as it was way cheaper and easier to get developed, tested, sold, bought and use them than on their devices.

even released some devices but since they didn't have the same signing keys, one couldn't even apps (not to mention they didn't had the on those either!)...

Public

@kkarhan @JessTheUnstill @fuchsiii On Nokia, I know @tomiahonen is on Mastodon, and might be able to shed more light on what happened internally there?

But the short version is Nokia chose the worst of all possible worlds by going with Windows Phone.

Yeah, Symbian was reaching the end of its life. There were three choices to replace it:

a) MeeGo. Ended up only shipping on one phone: The Nokia N9 in 2011. People still rave about that phone today. Possibly the best option.

b) Android. Basically, what Nokia's successor HMD is doing, except they would have had far more momentum by going early.

c) Windows Phone. History shows how that multi-billion-dollar blunder worked out. And I liked WP. I used it for around a year at one point. But MSFT completely mishandled it.

As for Firefox OS, I think Mozilla completely misjudged the market for it.

No, the first market for an open source phone with an app ecosystem based on open web standards shouldn't have been underpowered devices for emerging economies.

It was for people who run Linux on the desktop at home, people who run deGoogled Android, and people who work in software development/IT/InfoSec.

Public

@ajsadauskas @JessTheUnstill @tomiahonen yes, and to add insult to injury didn't even wanted to sell people like @fuchsiii or me a device, with the only one being "launched" in the being a 'd & 'd phone in one could only attain in-store with all the "" nonsense they had, demanding a legal address in Spain back then.

And like myself are far from the " " for whom stuff that isn't on shelves at Staturn/MediaMarkt, BestBuy, Walmart, ... doesn't exist. I'm used to importing that I want!

Public

@punkfairie @ajsadauskas @JessTheUnstill @tomiahonen @fuchsiii Yeah and is used with cheap phones of a brand named .

Case in point: nee is now drowned in obscurity because of mismanagment and hamfisted approach compared to .

Quiet public

@kkarhan
HMD hasn't issued a new kaios phone for a couple years, they only use S30 now. Plus kaios repo has been dead with zero commits for more than 6 months. So it was quite successful for a time with millions of devices sold, but their idea of closing most of the software, plus mozilla killing all firefoxos code from the repos very quickly made it unsustainable.
@punkfairie @ajsadauskas @JessTheUnstill @tomiahonen @fuchsiii

Public

@bohwaz @punkfairie @ajsadauskas @JessTheUnstill @tomiahonen That's exactly the problem, cuz nee was a good and solid basis not just for -Devices but could've been excellent for a more mobile OS, as it has good potential for and -principle'd that are lean and efficient.

But then again when enthusiasts like @fuchsiii and I were shouting "!" to , they basically refused to sell any , and then we get the "-Effect":

www.youtube.com- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
Quiet public

@kkarhan
Just like anything mozilla does, they don't have a long term plan, if it doesn't work in 2 years they drop the project... Firefoxos was more successful as kaios... Which says a lot.
@punkfairie @ajsadauskas @JessTheUnstill @tomiahonen @fuchsiii

@bohwaz @punkfairie @ajsadauskas @JessTheUnstill @tomiahonen @fuchsiii that's a general problem with .

Public

That would be a nice concept for a change - start with the most locked down, private, and secure upstream you can think of, and then let other projects decide how many pinholes to open up.

@kkarhan @bohwaz @punkfairie @ajsadauskas @tomiahonen @fuchsiii @torproject

Public

@JessTheUnstill @bohwaz @punkfairie @ajsadauskas @tomiahonen @fuchsiii Exactly...

Coincidentially, that's why (and ) doesn't let users have access because billions of devices owned by mostly "" that hardly get would be an even bigger risk if they didn't boot a locked-down image, thus only allowing for in user-privilegued userspace!

Cuz having a mobile OS that shoves everything through and only allows -Apps in the form modern web technologies would be a big and gain.

  • Not to mention is on it's way out and inevitably they gotta have to transition to supporting and eventually - at some point.
#amd64#arm64#riscv
Public

@JessTheUnstill @bohwaz @punkfairie @ajsadauskas @tomiahonen @fuchsiii

But I also consider why @torproject hasn't done so:

  • Because they'd rather focus on the few projects they can maintain at their staffing and budget than become the next "Apache Foundation" piling up .

And lets be honest @tails_live / @tails / is way more important to maintain as with , literally human lives depend on it!

Public

Yeah... That's certainly a major problem of a web browser. Literally its job is to run untrusted input. So it has to be an operating system in and of itself in order to be secure. And that much developer time and resources ain't free.

@kkarhan @bohwaz @punkfairie @ajsadauskas @tomiahonen @fuchsiii @torproject @tails_live @tails

Public

@JessTheUnstill @bohwaz @punkfairie @ajsadauskas @tomiahonen @fuchsiii

Granted, @tails_live @tails / and @torproject / are propably one of the best & most battle-tested options that are useable for ...

THAT'S NOT GOING TO HAPPEN!

If not for being absurd then for the fact that people need to get things done!

  • And it's not as if I haven't taught people how to get started, ranging from having to crash-course someone remotely via chat to hand-on sessions: If it's way more complex than an AKM [www.youtube.com] chances are people won't stick with it!

So you can imagine how glad I was when @thunderbird merged into so there's no more fiddling around getting /MIME to work!