91–100 of 165 posts
Earlier quoted context omitted.
They've got bills to pay. Something's gotta give. Are you willing to pay to use Twitter?
I was just thinking why not go the extra mile, I'd pay for using this though 1$/month - but I could also make it myself through tampermonkey or the api
I love this. I was always frustrated by the ever-growing-in-size Twitter app. Which is around 105 Megabytes now (aka ~73 1.44 floppies). So I welcome this.
[0] https://f-droid.org/repository/browse/?fdfilter=twidere&fdid...
Broken on FF android, http://i.imgur.com/p3jWX87.png
I am so happy this is a website and not an app. No more walled gardens!
The term walled garden refers to service lock-in where membership and mode of access is tightly controlled. It's not about using an app.
I hope they won't discard mobile.twitter.com it's lighter than lite and works without javascript
What exactly is the issue with allowing javascript. The entire internet runs on it. I keep seeing this comment on various other posts. Javascript is here to stay, and for you to get the best experience, or at all, you're going to need it.
This simply is NOT true.
Twitter Lite appears to omit Promoted Tweets (for me, for now), which is a bonus for experience.
Earlier quoted context omitted.
I don't understand why some mobile app are so large. If Twitter can write a webpage that provides the functionality in only 1Mb then what is in the mobile app?
Answering my own question, I just unpacked the iOS Twitter client thinking that it must contain massive graphic resources or something. Nope: mostly frameworks, the biggest being the T1Twitter.framework - 80.1Mb of who-knows-what. That doesn't include the 17 other frameworks all over 1Mb in size (there are innumerable other smaller frameworks) for periscope and other features. Seems to me they could ship a 5Mb app th…
I believe that, currently, if you iOS app uses any Swift code, you have to include the Switch libraries in your app. This has something to do with how quickly Swift has been changing, and Apple wanting you to reference your own library instead of the system one for now.
This has caused a number of apps to balloon in size lately, but the hope is that it is temporary.
Earlier quoted context omitted.
Answering my own question, I just unpacked the iOS Twitter client thinking that it must contain massive graphic resources or something. Nope: mostly frameworks, the biggest being the T1Twitter.framework - 80.1Mb of who-knows-what. That doesn't include the 17 other frameworks all over 1Mb in size (there are innumerable other smaller frameworks) for periscope and other features. Seems to me they could ship a 5Mb app th…
This is pure speculation on my part. I believe that, currently, if you iOS app uses any Swift code, you have to include the Switch libraries in your app. This has something to do with how quickly Swift has been changing, and Apple wanting you to reference your own library instead of the system one for now. This has caused a number of apps to balloon in size lately, but the hope is that it is temporary.
It is unfortunate that apps can't dynamically link to standard swift libraries in the OS, but that still doesn't explain the other 150Mb of binaries.