Jump to content

Morgin

Members
  • Posts

    797
  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Morgin

  1. See above discussion. I’m not basing anything I’m saying on my own personal anecdotes about user numbers (aside from pushing back against this turning into an iOS vs android debate, and providing rationale for why I care). The only entity that matters is IPS. Until they come to say otherwise, I’m going to make a pretty confident assumption that their stats say that ~1% of users of an IPS community being on iOS is below average, and they make development priority decisions based on averages. If their data matched yours and showed iOS was only used by ~1% of community users globally, I’d reckon this topic wouldn’t need to exist. Anyway, we’re going in circles. I honestly don’t care if you like or don’t like iOS or think it should be relevant to this discussion or not. The reality is that it is relevant, IPS has said they don’t plan on developing a feature solely for android, and if you want to add meaningful input to help speed this along, there is a mechanism to do so outlined above. Beyond that, anyone adding “+1 I want push” is just adding noise, because it’s ignoring everything that’s already been said in this topic.
  2. I suspect most of us like having users who keep our communities viable. >50% of mine use iOS to access via mobile browser. I don’t give a sh*t about android vs iOS or people’s inane fanboyism, I just want to service my users.
  3. “A very small number of users” is your opinion. It may be informed by your own site’s statistics, but I trust IPS to have better overall data that is informing their development priorities. If iOS was as insignificant as you believe, I have no doubt we’d have a mobile push strategy in place here. Also, for what it’s worth, it’s not even that straightforward on android yet. Copying the Xenforo implementation requires additional php plugins that invision would have to vet to make sure are going to be supported long term, requires a version of php that something like 50% of the userbase doesn’t even use yet, and requires sites to be using https. IPS has always been methodical and user-focused when introducing features. I can’t really think of any circumstances where they split their customer base by introducing something only a subset can use. Based on their comments in this thread and what has historically been their entire development philosophy, IPS community will have mobile push when the web widely supports mobile push for all users. Again, on that basis, the task now shifts to us to advocate to make that a reality. Personally, I’m disappointed IPS hasn’t put together their own submissions to the webkit team as I think they are in the strongest position to advocate, but if they won’t then it falls to us to do so. I’ve inspired myself to write something up and submit today, I hope everyone else does as well.
  4. Doesn’t really matter. How can IPS offer a feature that a huge portion of their customer’s users can’t use? It’s a splintered and impractical approach. If you want IPS to have a fully workable PWA with push, then you need to advocate for iOS. Sucks, but is what it is. I see your edit - look, Xenforo took the approach you suggest, and now has a bunch of people on their site complaining about no iOS support, and no one has stepped up to file a bug report as was requested by the WebKit devs explaining the use case. IPS devs above say they are waiting until they can solve for everyone. People can +1 the request here all they want, but if you actually want to see movement, there’s a path to speak directly to the people who can make it happen outlined above. We have hundreds of clients here, xenforo in the same boat, and no one has bothered to follow the process yet (myself included) to put this in front of WebKit. Can’t be that important I guess.
  5. Did you provide feedback to the WebKit team as per the above note? Getting push on iOS is key to getting push in invision.
  6. 😂😂😂 🔥🔥🔥 I don’t want a preview button. Invision should keep me happy and not have it there. And since I’m their favourite customer, that’s exactly what they did. Geddit?
  7. I can +1 the cloudflare business. They seem like a really positive company too.
  8. If Apple ever offers push PWA, it undoubtedly will also require enrollment in Apple's Developer Program, so I think it's likely a foregone conclusion that anyone wanting to play with that ecosystem needs to fork over the $99/year fee at some point.
  9. That guy is not an official spokesperson for webkit or apple, however. Apple's dev Maciej Stachowiak (who is one of the lead PWA devs from the looks of it) and Webkit's engineer Chris Dumez have both confirmed on twitter to use the webkit bugzilla for providing the use case feedback on the request. Providing through official apple feedback channels is obviously a good idea too, but feedback of any sort is the key here.
  10. FYI, in response to being asked about the list from the medium article, Apple PWA dev responded as follows: EVERYONE WHO IS READING THIS, PLEASE PLEASE PLEASE PROVIDE FEEDBACK HERE: https://bugs.webkit.org/show_bug.cgi?id=182566 EXPLAINING WHY PWA PUSH NOTIFICATIONS ARE VERY IMPORTANT TO SOFTWARE LIKE INVISION WHERE A WHITE LABEL MOBILE APP FOR EACH COMMUNITY IS NOT FEASIBLE. PLEASE TRY TO AVOID "+1 I NEED THIS" AND PROVIDE AS MUCH SPECIFIC, CONCRETE DETAIL ON HOW YOU WOULD MAKE USE OF THE ABILITY TO SEND PUSH NOTIFICATIONS TO MOBILE USERS AND WHY A NATIVE APP ISNT A SOLUTION I asked Invision if they had plans to make a formal use case proposal through this channel and as of right now they do not, so it is on us as a community to advocate loud and often for why push needs to be implemented on iOS with concrete examples of how our communities would use it (and just as importantly, not abuse it). @Matt, I appreciate that the view is that Apple is strategically holding back push support in iOS so as not to cannibalize the app store, but when the Apple dev who is responsible for implementation is specifically asking for concrete examples from people who would benefit from push API PWA support in iOS, we should still work together to provide that feedback even if it's ultimately a dead-end. @Joel R you are probably one of the best in this community at taking all the noise from in here and distilling into actionable efforts, so anything you can do to help wrangle us into a coherent community driven effort to make our request heard loud and clear to Apple here would be sincerely appreciated. Also tagging some of the devs I see posting often who might be able to help provide the technical info submissions for their apps, etc. @Fosters @Adriano Faria @CodingJungle @opentype @newbie LAC @TheJackal84 @All Astronauts Also, as a final thought, I'm not sure how much communication there is between the development teams for Invision, Xenforo, NodeBB, Discourse, Vanilla, etc. etc., but this is one of those topics where forming a lobbying group of developers where you can aggregate the number of users across all platforms and deliver some consistent messaging would be really helpful IMO. Any victories we can make with PWA in iOS ultimately serves to keep all of our communities alive and able to compete with other closed platforms, as ultimately user engagement on mobile through notifications (and in the case of iOS, the complete lack thereof) is going to make or break many of us.
  11. https://medium.com/dev-channel/progressive-web-app-progress-in-ios-12-2-beta-1-build-16e5181f-a18cd05ca361 is a great article that summarizes the state of PWA in ios, and has a call to action at the bottom of the article. https://twitter.com/othermaciej is the apple dev on webkit who has been the public face of PWAs. As recently as last month, it appears apple is still only "considering" push support https://twitter.com/othermaciej/status/1132795589068910592 I would urge all of you to offer feedback in the official channels.
  12. I don’t have any sort of group promotion in place for activity. Some sort of combination of content count or days of activity or whatever. Usually the Korean spam bots are brand new accounts, so if someone has more than X approved content, it’s probably ok for them to use the characters
  13. I just had an occurrence where some longer term members started communicating in Korean via PM and got banned. Any chance there could be a threshold to the autoban - if member has > X amount of posts, or some other way to prevent it from impacting people with some history?
  14. I think the solution there is to show it was edited. I’d rather avoid content duplication vs having someone say something that’s gonna be removed and then have to go edit another 10 posts to remove what they said from all the people quoting it. Whether it’s doxxing, etc
  15. The biggest issue with quotes vs reply is that quotes turns the original content into new content and doesn’t dynamically show based on what was there. The obvious issue here is when content is moderated or edited, the quoted text itself has to be edited or moderated separately. I don’t think the quote concept is fundamentally the wrong approach, but in future I would love if editing/moderating content automatically updated any content quoting that original content.
  16. I’m not sure I agree that 74.5% constitutes a vast majority, but otherwise point taken.
  17. They aren’t working on push from all accounts.
  18. FWIW, global mobile device sales tells me nothing. My own analytics shows me >50% of my mobile traffic is iOS. Others have posted similar anecdotal numbers. Invision likely has it own numbers as well. I’m not saying no community would benefit, but I would be shocked if there is a majority of users of IPS communities using android such that we are at a point where the dev team investing is PWA development makes sense.
  19. PWA is currently essentially broken for what the main benefits should be on iOS. No app icon flag support (I.e notifications). Forced page refresh every time you go back to it. No push notification support at all. Limited support of PWA standards. re Twitter mobile, I’d make the same point I made earlier - what are the actionable changes to the mobile version of the presentation of the platform you would suggest?
  20. How do you propose they fix it? White label app design doesn't work. App stores don't like multiple versions of the same app with different branding being submitted based on which community is using it. An omnibus "IPS Forum app" that wouldn't allow users to directly monetize their own communities and requires users to go in and find their community and register to it doesn't appeal to a lot of people either, myself included, largely because they'd need to adopt a "one-size" approach. Invision has also noted they've tried app development and it didn't work out for them, so this is all kind of moot. PWAs are not supported in a form that is beneficial to >50% of mobile traffic and until apple embraces it, it will never be more than a niche technology. I'm not saying apple is this important, it's just that in markets where a lot of us have large forums, our users are predominantly apple/iOS users. With the current state of things, the mobile responsive skin is overall pretty good. If you don't like it, you can change it to a different mobile design. I think it can be improved based on some new ideas from other mobile forum skins I have used from other platforms (some of what discourse is doing is quite interesting) but it's not like the IPS mobile skin is outside of the top 3 for forum software. There is a lot of complaining here, but not a lot of direct actionable items. Why not try suggesting specific things that can actually be achieved?
  21. If and when iOS supports push notifications would be my guess!
  22. Yes. Google is still inserting them wrong.
×
×
  • Create New...