Notices by Nolan (nolan@toot.cafe), page 3

Eiji Kitamura (agektmr@toot.cafe)'s status on Tuesday, 08-Oct-2019 07:50:05 EDT Eiji Kitamura

Verify phone numbers on the web with the SMS Receiver API https://web.dev/sms-receiver-api-announcement/
In conversation Tuesday, 08-Oct-2019 07:50:05 EDT from toot.cafe permalink Repeated by nolan
Attachments
1. Verify phone numbers on the web with the SMS Receiver API | web.dev
  
  from web.dev
  
  Finding, memorizing, and typing OTPs sent via SMS is cumbersome. The SMS Receiver API simplifies the OTP workflow for users.
Nolan (nolan@toot.cafe)'s status on Tuesday, 08-Oct-2019 07:14:47 EDT Nolan

"Into the web multiverse" by Christian Heilmann https://christianheilmann.com/2019/09/25/into-the-web-multiverse/
Long but interesting read on the different kinds of web users and developers, and what they want from the web. It's good to remember that not everyone is an expert and that paying attention to a small vocal minority of aficionados can leave a lot of people behind.

In conversation Tuesday, 08-Oct-2019 07:14:47 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Monday, 07-Oct-2019 10:27:23 EDT Nolan

@dpogue Yes, it's a dependency of the other project. So unfortunately I can't seem to get any sort of Linux-based iOS Safari debugging to work. :(

In conversation Monday, 07-Oct-2019 10:27:23 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Monday, 07-Oct-2019 08:45:43 EDT Nolan
- ˗ˏˋ Doug Belshaw ˎˊ˗ 🇪🇺☠️✊
@dajbelshaw That's a good point! In that case, this might also involve PRs to Mastodon itself and to joinmastodon.org though. I'm not sure how smooth the signup/login process is on a KaiOS device right now.

In conversation Monday, 07-Oct-2019 08:45:43 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Monday, 07-Oct-2019 08:42:01 EDT Nolan
- Kornel
@kornel Nope, Pinafore would be the first, as far as I can tell. Assuming it passed the KaiStore review process. :)

In conversation Monday, 07-Oct-2019 08:42:01 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Monday, 07-Oct-2019 08:40:47 EDT Nolan
- ˗ˏˋ Doug Belshaw ˎˊ˗ 🇪🇺☠️✊
@dajbelshaw Fair enough, although I wonder how much of a draw Mastodon/Pleroma really is for a mass-market audience. 🙂 (And especially one that seems concentrated at the low-end of the market in India and Brazil; the fediverse seems to skew tech-savvy and Western.)

In conversation Monday, 07-Oct-2019 08:40:47 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Monday, 07-Oct-2019 08:37:31 EDT Nolan

I think partly I just wanted to prove to myself that Pinafore could run well on a feature phone with 512MB of RAM. Now that I've proven that, I wonder whether it's really worth pushing it over the finish line.

In conversation Monday, 07-Oct-2019 08:37:31 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Monday, 07-Oct-2019 08:36:03 EDT Nolan

My little KaiOS experiment with Pinafore was a neat proof-of-concept (https://nolanlawson.com/2019/09/22/the-joy-and-challenge-of-developing-for-kaios/), and it fixed some accessibility and small-screen bugs. But I've run into a fairly blocking issue with getting the login flow to work (https://github.com/nolanlawson/pinafore/issues/1542), and plus I would have to submit it as an app to the KaiStore. So I'm wondering if it's really worth the effort.
In conversation Monday, 07-Oct-2019 08:36:03 EDT from toot.cafe permalink
Attachments
1. The joy and challenge of developing for KaiOS
  
  By Nolan Lawson from Read the Tea Leaves
  Recently I spent some time getting Pinafore to run on a KaiOS device. Overall, I found it to be challenging but enjoyable. In this post, I’ll talk about some of the tricks that helped me to work with this curious little feature phone.
  
  Why KaiOS? Well, I guess I’ve always been a bit of a gadget geek. I’ve been developing for Android since the early days of the HTC Dream, I managed to get my Nexus 5 to triple-boot into Android, Firefox OS, and Ubuntu Touch, and I’ve also played around with the Amazon Fire Phone, Windows Phone, iPod Touch… You get the idea.
  
  Recently though, I’ve found the mobile landscape a bit boring. Android and iOS are the two big players, and it’s been that way for nearly a decade. Firefox OS, Blackberry OS, Windows Phone, and other would-be contenders have long since bitten the dust.
  
  That’s why I’m excited about KaiOS. It’s a platform that’s growing surprisingly fast and is actually based on Firefox OS (may it rest in peace). It’s especially popular in India, where it’s already the second-most popular OS after Android.
  
  KaiOS can run regular websites, but it can also run “packaged” apps, ala Firefox OS. So how can an aspiring KaiOS developer get started?
  
  Step one: buying a development phone
  
  I like to test on real devices, because I want to experience my app with real-world hardware and performance constraints, as an actual user would. I decided to get the Nokia 8110 4G because it was available on Amazon for $70.
  
  Note that this phone only supports AT&T in the U.S., so if you plan on using it as your actual personal phone, you may be out of luck.
  
  When you first unbox the phone, you’ll have about 5 minutes’ worth of setup screens, after which you’re ready to go. I’d also recommend going into the settings and upgrading the OS, since mine needed an upgrade right away.
  
  Next steps: development environment
  
  The best resources I’ve found for KaiOS development are the official developer guide and Paul Kinlan’s quick start guide. Paul’s guide is the best place to start, since it’s short and will get you up and running quickly.
  
  Paul says that he could only get WebIDE to work in Firefox 48, but I found that Firefox 59 also worked (per the KaiOS developer guide). So let’s use that.
  
  First you’ll want to download Firefox 59 for your OS (in my case, Ubuntu) via Mozilla’s download site. Sadly I could not get Firefox 59 to run alongside the latest Firefox (which is my go-to browser), and I also found that Firefox 59 tried to aggressively update itself, so every time I reopened it, it would be running the latest version. To work around that, you can run this script:
  
  rm -fr firefox profile mkdir profile tar -xjf firefox-59.0.3.tar.bz2 ./firefox/firefox-bin -profile profile
  
  This will delete Firefox’s stored data and restart it with a fresh profile every time. It’s handy for quickly restarting Firefox!
  
  After you input the “secret” code that Paul mentions (*#*#33284#*#*), you should see a little bug icon in the corner:
  
  At this point you should be able to run:
  
  adb devices
  
  …and see your device in the list of devices:
  
  List of devices attached 4939400 device
  
  If adb isn’t running, you can run adb kill-server && adb start-server to restart it.
  
  This didn’t work for me out of the box – I got an error saying it couldn’t connect to my device due to faulty udev rules. Luckily the KaiOS developer guide has a “Setting USB access” script that will fix that.
  
  After running that script, I used Paul’s trick of setting up adb forwarding:
  
  adb forward tcp:6000 localfilesystem:/data/local/debugger-socket
  
  After this, you should be able to connect in Firefox WebIDE by clicking “Remote Runtime.”
  
  One thing I noticed is that occasionally my device would get disconnected from WebIDE. In that case, you can just forward to another port:
  
  adb forward tcp:6001 localfilesystem:/data/local/debugger-socket
  
  …and then reconnect WebIDE to the new port, and it should work.
  
  Next steps: actually writing code
  
  As far as I can tell, KaiOS is based on Firefox 48. You can tell by the user agent string:
  
  Mozilla/5.0 (Mobile; Nokia_8110_4G; rv:48.0) Gecko/48.0 Firefox/48.0 KAIOS/2.5.1
  
  This means that you won’t necessarily have all the latest-and-greatest JavaScript or Web API features. Here’s a brief list of what I found didn’t work:
  
  async functions
  
  ServiceWorker
  
  Intl
  
  As a quick gut-check of whether your app will run on KaiOS, you can try downloading Firefox 48, loading your website, and seeing if it works. (I found this easier than trying to debug on KaiOS right out of the gate.) You can use the same script above to run Firefox 48 with a fresh profile.
  
  Once your code is sufficiently backwards-compatible (I found that @babel/preset-env with the default settings plus an Intl polyfill was good enough for me as a starting point), you have two options for testing your app:
  
  as a packaged app
  
  as a hosted app
  
  (If you’ve done Firefox OS development before, you’ll find these options familiar.)
  
  I tried both techniques, but found that the hosted app was easier for quick testing. If your development machine and phone are on the same WiFi network, then you can create a manifest.webapp file per KaiOS’s documentation and then load a URL like so:
  
  http://192.168.1.2:4002/manifest.webapp
  
  (If you’re not sure what IP address, to use, run ifconfig -a | grep inet.)
  
  Then you should see your app listed, and you can run it on the device by clicking the “play” button:
  
  You can also try the packaged-app route, but I found that it didn’t play well with the routing library in my framework of choice (Sapper) due to the extra /index.html. Plus, if I ever actually submit this app to the KaiStore, I’ll probably go with the hosted route since it’s less maintenance work.
  
  Optimizing for KaiOS
  
  In terms of web development, there are a few good things to be aware of when developing for KaiOS, and in particular for the Nokia 8110 4G.
  
  First off, the available screen size is 240×294 pixels, which you can check by using window.innerWidth in JavaScript, @media (max-width: 240px) in CSS, etc. If you set "fullscreen": true to hide the status bar, you can get slightly more breathing room: 240×320.
  
  I had already optimized my app for the iPhone 4’s screen size (which is 320×480), but I found I had to do extra work to make things show up correctly on an even tinier screen.
  
  The iPhone 4 is already pretty small, but it’s a giant compared to the Nokia 8110 4G.
  
  Next, the input methods are quite limited. If you’ve actually taken the time to make your webapp keyboard-accessible, then you should be most of the way there. But there are still some extra optimizations you may have to make for KaiOS.
  
  By default, the ↑ and ↓ arrows will typically scroll the page up or down. I decided to use the ← and → arrows to change the focus – i.e. to act as proxies for the Tab and Shift + Tab keys. I wrote some fairly simple logic to navigate through the focusable elements on the page, taking special care to allow the arrow keys to work properly inside of text inputs and modal dialogs.
  
  I also found that the focus outlines were a bit hard to see on the small screen, so I scaled them up for KaiOS and added some extra styling to make the focus more obvious.
  
  Some apps may opt to display an onscreen cursor (this seems to be the default behavior of the web browser), but I found that to be a bit of a clumsy experience. So I think managing the focus is better.
  
  Other KaiOS web developer hurdles
  
  The next most difficult thing about KaiOS is still the lack of modern browser standards. For instance, I couldn’t get SVG <use> tags to work properly, so I fell back to inlining each SVG as a workaround.
  
  CSS Grid is (mercifully) supported, so I didn’t have to backport my Grid logic. Since Grid is not supported in Firefox 48, this hints to me that KaiOS must have tweaked the Firefox OS code beyond what Firefox 48 can support. But I haven’t done the full rundown of all the supported features. (And I still find it helpful to use Firefox 48 as a minimum bar for a quick test target.)
  
  As with all web development, this is the area where you’ll probably have to roll up your sleeves and test for what’s supported and what’s not. But overall I find KaiOS to be much easier to develop for than, say, IE11. It’s much further along on the standards track than a truly legacy browser.
  
  Once you’ve gotten past those hurdles, though, the result can be surprisingly good! I was impressed at how well this tiny feature phone could run Pinafore:
  
  (Much of the credit, I’m sure, is due to the excellent SvelteJS framework.)
  
  Conclusion
  
  Building for KaiOS is fun! The device is quirky and lightweight, and it makes me excited about mobile development in a way that I haven’t felt in a while. In terms of development, it feels like a nice compromise between a feature phone with limited hardware (small screen, no touch, limited key input) and a smartphone OS with cutting-edge web technologies (it has CSS Grid! And String.prototype.padStart()! It’s not so bad!).
  
  However, I’m not a huge fan of app stores – I don’t like having to agree to the ToS, going through a review process, and ultimately subjecting myself to the whims of a private corporation. But KaiOS is neat, it’s cute, and it’s growing in developing markets, so I think it’s a worthy venue for development.
  
  And unlike fully proprietary development platforms, you’re not writing throwaway code if KaiOS ever goes away. Since it’s ultimately just a webapp, improvements I’ve made to Pinafore for keyboard accessibility and small screens will accrue to any other device that can browse the web. Other than the manifest.webapp file, there’s nothing truly specific to KaiOS that I had to do to support it.
  
  Overall, I find it fun and refreshing to build for something like KaiOS. It helps me see the web platform from a new perspective, and if nothing else, I’ve got a new gadget to play with.
2. Add login mode compatible with KaiOS · Issue #1542 · nolanlawson/pinafore
  
  from GitHub
  
  For environments like KaiOS especially, it would be useful to have another way to log in. I cannot seem to get KaiOS to work with the current login structure, because KaiOS is very particular about...
Nolan (nolan@toot.cafe)'s status on Monday, 07-Oct-2019 08:33:48 EDT Nolan

Does anyone in the fediverse actually have a #KaiOS phone? If I made #Pinafore compatible with it, would you use it?

In conversation Monday, 07-Oct-2019 08:33:48 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Monday, 07-Oct-2019 07:47:02 EDT Nolan

@toast It's probably a Pleroma issue then. Thanks for the details! I've opened a bug: https://github.com/nolanlawson/pinafore/issues/1551
In conversation Monday, 07-Oct-2019 07:47:02 EDT from toot.cafe permalink
Attachments
1. Streaming bug in Pleroma · Issue #1551 · nolanlawson/pinafore
  
  from GitHub
  
  Apparently there is a streaming bug, looks like it fails to parse the JSON and then somehow this leads to weird rendering. At least as far as I can tell from the bug report: https://toast.cafe/obje...
Nolan (nolan@toot.cafe)'s status on Monday, 07-Oct-2019 07:45:31 EDT Nolan

So apparently, the debug bridge for iOS just stopped working recently. I can't get it to work in either Chrome or VS Code. >_<
https://github.com/RemoteDebug/remotedebug-ios-webkit-adapter
Based on the commit history, it looks like abandonware. Really sad that a tool maintained by Microsoft was the only way to debug iOS devices on Linux (using Chrome Dev Tools). Like… anyone at Google or Apple could have worked to keep it up to date, but instead they probably just expect us to buy Macs

In conversation Monday, 07-Oct-2019 07:45:31 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Monday, 07-Oct-2019 07:42:15 EDT Nolan

@toast Hmmm unfortunately that's not enough information to work with. Is this a normal Mastodon instance or Pleroma or glitch-social or something else? Which Mastodon version?

In conversation Monday, 07-Oct-2019 07:42:15 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Monday, 07-Oct-2019 06:51:57 EDT Nolan
@Tryphon @stevegenoud @belljar Thanks very much, everyone! I think this tells me how I should solve the bug now. I'll have to have separate behavior for iOS 12 and 13. Thanks much!

In conversation Monday, 07-Oct-2019 06:51:57 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Monday, 07-Oct-2019 06:13:02 EDT Nolan

Could somebody who has iOS 13 please test if this Safari bug is fixed? https://bugs.webkit.org/show_bug.cgi?id=190982#c2
The steps to reproduce are very simple and are described in the link above. It takes about 5 minutes to check. Thank you!

In conversation Monday, 07-Oct-2019 06:13:02 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Monday, 07-Oct-2019 05:53:37 EDT Nolan

@toast @toast There's probably an error in the Dev Tools console. If you type Ctrl-Shift-I you should be able to see it. It would also help to know what kind of browser this is. Thanks!

In conversation Monday, 07-Oct-2019 05:53:37 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Thursday, 26-Sep-2019 08:53:34 EDT Nolan

"Charting a new course for tech competition" by Chris Riley https://blog.mozilla.org/netpolicy/2019/09/26/charting-a-new-course-for-tech-competition/
Interesting read. I wish there were more concrete examples, though, of what they mean by "mandating federation" or "restricting APIs and API policies." Although I guess if there were, then the whitepaper may get muddled by questions of whether a specific example really demonstrates anti-competitive behavior.

In conversation Thursday, 26-Sep-2019 08:53:34 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Wednesday, 25-Sep-2019 14:14:40 EDT Nolan
- Hugo Gameiro
@hugo I was wondering why search on mastodon.social was broken in Pinafore...

In conversation Wednesday, 25-Sep-2019 14:14:40 EDT from toot.cafe permalink
Hugo Gameiro (hugo@masto.pt)'s status on Wednesday, 25-Sep-2019 12:53:19 EDT Hugo Gameiro

I think I have to take a day of work just to go through all the changes for Mastodon v3.0 https://github.com/tootsuite/mastodon/releases/tag/v3.0.0rc1 :)
In conversation Wednesday, 25-Sep-2019 12:53:19 EDT from masto.pt permalink Repeated by nolan
Attachments
1. tootsuite/mastodon
  
  from GitHub
  
  Your self-hosted, globally interconnected microblogging community - tootsuite/mastodon
Nolan (nolan@toot.cafe)'s status on Wednesday, 25-Sep-2019 14:02:37 EDT Nolan
- Henry 🐖
@hjst That's exactly why platforms like KaiOS are so amazing. The default assumption is that the mobile web is "slow." But clearly it's possible to build mobile webapps and browsers that run well on feature phones, or else KaiOS wouldn't have millions of users.

In conversation Wednesday, 25-Sep-2019 14:02:37 EDT from toot.cafe permalink
Nolan (nolan@toot.cafe)'s status on Wednesday, 25-Sep-2019 12:18:34 EDT Nolan

FirefoxOS was based on the premise that the best OS for a low-end phone is the web. FirefoxOS failed, but it would be amusing if KaiOS and Google's new feature phone OS proved the original assumption to actually be correct.

In conversation Wednesday, 25-Sep-2019 12:18:34 EDT from toot.cafe permalink

After
Before

Public

Notices by Nolan (nolan@toot.cafe), page 3