Jump to content
View in the app

A better way to browse. Learn more.

Invision Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Invision Community Blog

We've upgraded our blog to the new 1.4 version for the first round of testing. We will have a beta version available for download next week, until then enjoy the new version here and let us know what you think. We're very excited to hear your feedback and suggestions on this blog preview!

New Default Style

IP.Blog has been overhauled with a fresh new style, one which feels more like a traditional blog. Additionally, it has been designed with themes (see below) in mind, so there is plenty of room for theme authors to experiment in their designs.

Themes and Custom Headers

You can now install 'theme packs' and allow your users to choose which of these themes will be applied to their blog. Using themes you can completely change the look and layout of an individual blog (to see a demonstration of a theme in use, check out Rikki's blog). Users are also able to create their own unique theme, these user themes must be approved by an adminstrator before they are publically viewable by other users. The new custom header system allows you to create multiple header images for users to choose from.

Content Block Plugin System

It's now much easier to create your own content blocks, using a new plugin system. It's now possible to define settings for a plugin that apply to individual blogs, this means that you can integrate with 3rd party widgets that require a unique username for each blog. We've also included new content blocks in this release: Twitter, MyBlogLog, Google Reader, Friends Blogs, and Recent Visitors.

Social Bookmarks

A new bookmark manager allows you to define bookmark services for your blog system. These services will allow blog entries to be easily submitted to the bookmark services that you setup. There are several preconfigured services: Del.icio.us, Digg, Facebook, Mixx, Reddit, and Stumbleupon. Please feel free to suggest any services that you would like to see included by default.

Media Integration

The new tag allows you to automatically convert various media types into a more useable format. FOr example, [ blogmedia ]http://www.test.com/somemp3.mp3[/ blogmedia] would be converted into a mp3 player for the specified file. You can define any media type you like in the Media Tag manager, by default we include: Flickr Image Set, GameTrailers, Google Video, MP3 Player, MySpace Video, Veoh, and YouTube. Please suggest any additional media tags that you would like to see included by default.

Akismet Integration

It's now possible to use Akismet to filter spam for both the comment and trackback system.

Feedburner Integration

Users can now override the default rss syndication and use FeedBurner.

Other Changes:

Edit Entry Date Display article count for categories Blog Offline Mode Entry author replies in comments are now highlighted Admins can select a 'Featured Entry' to be displayed on the blog listing
  • 5,203 views
We plan to release a small update later this month, with a slightly refreshed style and a few extra features. We haven't locked down exactly what these features will be, but we will be talking about it more soon. I know that many of you were expecting a larger release and we apologize for the link of time from the last major update to IP.Blog. The larger update is coming, which will be IP.Blog 2, is coming and will release along side IP.Board 3.

We plan to have a beta of 1.4 available in the next two weeks, it's not too late to suggest in minor tweaks and changes that you would like to see included in this release.

We're very excited about the future of IP.Blog and have many new features planned for version 2 and we thank you for your patience during this development time. We'd love to know what features you are most interested in for the next major release, now would be a great time to post those suggestions in the IP.Blog forum.

IP.Blog 2.0 Discussion
IP.Blog 1.4 Discussion
  • 2,206 views
We have put together a login module which fully supports OpenID 1.x and 2.x protocol specifications.

This module is a beta release which we hope to expand upon. It is available freely to all customers with access to our official resource site in the IPS Releases category.

Click here to view this file

For those not familiar with OpenID, it is a protocol specification that allows a user to select a trust root (a site they can trust) and register. Then, on any site that supports OpenID, the user actually logs in through their trust root, instead of your site. Behind the scenes, your site and the trust root verify that the user is who they say they are, and if authenticated your site will allow access.

More information on OpenID can be found at openid.net (official site) and on Wikipedia.

This module only adds OpenID Consumer support - it does not add OpenID Provider support.

Please remember - this is a beta release of the login module, and as such there may be bugs or other issues with the module. If you are interested in using this login functionality you should test it out on a test site before applying it to your live site, to be certain there are no issues. As with any modifications, IPS does not support this modification directly. If you have issues with the module and require assistance, you should leave a comment on the file's download page.
  • 4,252 views
For those of you who have been with IPS for some time you may have been aware of a previous announcement regarding the development of two separate products called Nexus and Dynamic. Nexus was to be an ecommerce billing system and Dynamic was to be a content management system.

As we developed these products the Internet market had changed quite a bit so we have made the decision to totally discontinue Nexus and Dynamic production as they were. We know many of you were looking forward to either Nexus or Dynamic as they were first intended and we apologize if this disrupts your plans.

Instead we have decided to create a new product that combines the previous goals of ecommerce and content management along with a host of features including customer management, support, business organization, and a modular structure in which features are only limited by our imagination.

Since everyone at IPS loved the term "Nexus" to describe this system we decided to recycle that name and so IP.Nexus was born. IP.Nexus is a complete business management suite which includes many of the previously stated goals along with so many more. We look forward to releasing this new product line.

It is worth noting that this time around the new product is nearly complete rather than an idea in development. Expect a lot more information including the first public betas in the coming weeks! Watch our announcements forum and this blog for more information.
  • 4,639 views
In part due to the awesome success surrounding our first community-supported project, we are in initial stages of preparing our next Community project.

As many of you may already know, Stewart had been working for some time on a Gallery uploader tool - an application a user could install on their computer to easily manipulate and upload multiple images to an IP.Gallery web installation. Stewart made great progress on the tool before he left, and while we do have employees here capable of programming in the C# language the tool is written in, we felt this would be another great opportunity to launch a community-supported project, similar to IP.Tracker.

We would like to gather up a handful of members who are familiar and able to code with C#, and who are interested in working on this project for IP.Gallery, so that we can put the necessary final touches on the project and release it freely to the community at IPS Beyond.

The applicants will need to work closely with me, as a heavy part of the project will involve php code necessary to interact with IP.Gallery. Additionally, any users who are also versatile in perl (or a similar CGI language) could be of use in overcoming many of the php limitations we commonly face (maximum file upload sizes, maximum execution times, and so on).

If anyone is interested, please send bfarber a PM with some background and how you think you will be able to help. I cannot guarantee immediate responses to everyone, and almost certainly not everyone will be chosen, but we look forward to hearing from anyone interested.
  • 3,234 views
While IP.Gallery 2.2 has not yet been released at this time, I wanted to take a moment to outline a few of the new features and touchups in Gallery that may not be as evident.

A strong focus for this release of Gallery was strengthening the backend - many Gallery users know that some core functionality was just missing and it was time to bring Gallery in line with the rest of our offerings. For example, users could not control the ordering of their albums, nor could moderators move images from/to albums. This has all been fixed. Additionally, Gallery has been updated to use IP.Board's caching methods to help reduce the number of SQL queries run on each page, and it has been moved over to a component for forward compatibility reasons.

Arguably, it's the little things that make or break Gallery software. You have to strike the right balance between the image (which is of course the main focus in a Gallery) and the rest of the content. We streamlined the image view page considerably to help make the image viewing more pleasant and less distractive. The exif/iptc data that can be extracted from images was moved into a popup/movable div so it doesn't display directly on the page. The edit/delete/etc. links were put into a single dropdown to reduce the number of buttons below the rest of the data. Here is a screenshot showing the drop down and the popup together



Another frequently requested feature was easier ability to hotlink images.



And of course the "Set as Avatar" has finally made it's appearance via an "Avatar" button next to the Options button.

Other small but important changes involve navigating the Gallery, which many users requested be simplified. We've added some things to make this easier for users. Firstly, at the top right we've added "First, Previous, Next, and Last" links which will take you to the respective images inside the container you are viewing.



Additionally, in the photostrip at the bottom of the page, there are << and >> buttons added (as appropriate) to allow you to cycle through the photostrip using AJAX. This can help you get a quick overview of the images in the container, and be able to jump to an image in the container easily. Go ahead, visit an image inside the IPB Community Personal Photos and try the AJAX navigation.



And of course, one of the more noticable changes is support for lightbox in the Gallery. For an example of how this works, view this page and then click on the image. This of course can be disabled if the administrator wishes.

There are many other important updates naturally, with some more notable changes being

Drag-n-drop support for reordering post form fields and categories Custom post form fields now automatically insert into the image view page and submission form Ability for admins to deny ability to members to create private albums Zip import support for members ACP language abstraction Slimmer templates for easier skinning Forum-style listing for albums Improved search capabilities Email notification options for comments and image submissions Image dimensions display on the image view page And many other smaller things you will have to find out when you install or upgrade your very own Gallery!
  • 2,686 views
One of the driving focuses for IP.Board 2.3 was resource usage. We wanted to spend some time on improving the underlying operation of IP.Board, even if this meant not adding a lot of new features on the surface. As with most applications that develop beyond a few releases, over time so many features have been stacked into IP.Board that, while not necessarily ineffecient, we felt we could revamp some of the underlying code to make IP.Board run even better.

We wanted to highlight a few of these changes for those who are interested.
The parse_member method of topics.php has been moved to ipsclass.php to make it more centralized, as it's used by many various classes in IP.Board. Similarly the member_set_information method out of profile.phpand into ipsclass.php as well. We've added a new feature that allows skin template bits to be shared across different skin files. With 2.3 you can now simply edit the some template bits and automatically update all skin files where those bits are used. There are several template bits making use of this functionality to help reduce the number of skin files loaded on any given page view.

If you would like to make use of this functionality (for example, with a custom modification), you can select to share a template bit to another skin file by going to Look & Feel -> Edit Template HTML for the skin -> (Select a skin group) -> (Select a template bit). Click the drop down button where you would normally edit the template's incoming data variables, and hit "Edit Cache Settings". You can select (or review) secondary skin cache files that will share the template bit you are viewing. We've added a few more database indexes based on our analysis of some common database queries that IP.Board runs. With 2.2, we introduced the new profile portal functionality in IP.Board. This uses an iframe to load center content, which requires a second call back to the server to load the center column content. In 2.3 we've pre-loaded the first tab's content to prevent this second request (on the initial profile page load) from being required. For 2.3 we've added a setting in the Admin CP under CPU Saving and Optimization labeled "Use multi-byte safe wordwrap". International users can continue using the word wrap function more suited to matching 2 and 3 byte character sets, while users with only English text on their forum can use a much more effecient word wrapping function that doesn't need to take multi-byte characters into account. We've also added a setting in the Admin CP under CPU Saving and Optimization labeled "Disable Topic Summary". Setting this to Yes will turn off the topic summary displayed at the bottom of the Add Reply page. This setting is Off by default (the summary will still display unless you turn it off). We've disabled the custom error handler by default in IP.Board 2.3, which prevents our custom error handling function from being called with every PHP Notice (which are not displayed). If you'd like to revert this functionality, just edit init.php and change

define( 'CUSTOM_ERROR', 0 );
to


define( 'CUSTOM_ERROR', 1 );
We've optimized our post parsing routine by preventing two expensive usort calls from being required, as they are already run when the associated data is saved in the admin CP. We've enhanced our MySQL database driver when doing field_exists and table_exists method calls byUsing a 'SHOW FIELDS' query rather than a 'SELECT COUNT(col)' query to determine if a database field exists We cache the fields in a table, and the tables in a database, the first time a field_exists or table_exists query is run to prevent having to query the database for the same data later during script execution Announcements, Private Messages, Calendar Events, and Topic Posts are now parsed entirely on save, rather than when displaying the data (or in the case of topic posts, half on save and half on display). This prevents the parsing from running on display, and prevents having to load several parsing libraries and associated caches when displaying the data. We've enhanced the rebuild posts tool to also support private messages, calendar events, and announcements for users who will upgrade and need to rebuild the content (to parse html and custom bbcode appropriately). Rebuilding posts will be necessary after upgrading in order to ensure all custom bbcode is parsed, however upon doing so we will be saving many resources at run time, which is by and far a more important consideration.

I hope this helps detail and clarify some of the resource improvements made for 2.3. The good news is that if you didn't notice any of these things already here on the company forums, then our changes are working exactly as we had hoped - same surface functionality, a much stronger backend to handle it.
  • 2,819 views
We're pleased to announce that the first release of the bug tracker, now known as IP.Tracker, is available for download at IPS Beyond. We'd like to thank Michael, C_ind, and Krocheck for doing such a great job getting this first release available. We'd like to encourage everyone to stop by the tracker forum and post your feedback, as well as submit your own code for inclusion into IP.Tracker.

Download Link: http://www.ipsbeyond.com/forums/index.php?...p;showfile=1043
Support Topic: http://www.ipsbeyond.com/forums/index.php?showtopic=22774
Suggestion Forum: http://www.ipsbeyond.com/forums/index.php?showforum=76

We're very excited to see how the Tracker will evolve and plan on creating more projects like this in the future.

Please note that this free module is not included in your IPS support, if you need any assistance please use the support topic linked above.
  • 3,838 views
As many know, we are in the process of revamping IPS Beyond. Along with that, we will be offering many more supported resources from IPS.

The first will be a new supported skin that will be offered as a secondary default skin to the board. This first skin will be designed as a very basic skin (no gradients for example) thereby allowing for much easier color changes and such when you want to match it to your site. As a supported skin it will be updated between versions of our software.

We will be previewing the new skin on our company forums in the next few days and it will be available along with IP.Board's 2.3 release.
  • 2,428 views
We just wanted to thank BoxerPals (http://www.boxerpals.org) for sending us that lovely box of cookies and fudge. You know how to go straight to our staffs' heart.

We occasionaly get thank you gifts from customers and it's always appreciated.
  • 1,932 views
I have a quick update for you on the bug tracker project now. I'm happy to announce that Michael and C_ind of IPS Beyond will be leading the bug tracker project. They both have a great track record and have been a huge benefit the the IPS Beyond community and we're very pleased to have them working on the bug tracker. We'll be delivering the code to them tomorrow, and then work will begin on getting the bug tracker into a releasable form.

They'll work on cleaning up what we have and getting an initial release out to the public. From there everyone will be welcome to submit code contributions to them and they will decide to include them or not. I know they have a lot of great ideas themselves, which I'm sure they'll post about soon.

We'll have more information on this soon, if you have any questions please ask in the comments and we'll do our best to answer them.
  • 2,803 views
One of our major goals is to support our modification community and today I'm excited to tell you about a new venture to help the mod community. As many of you know we have our own internal bug tracker that we use on these forums. We've had numerous requests to release it and now we're ready to do just that, at no charge to our existing customers. The bug tracker will soon be released to IPS Beyond for everyone to download.

This is going to be a unique project for us, we're going to have the IPS Beyond community run the bug tracker project. We'll be selecting a few IPS Beyond members to help us manage this project, they'll be responsible for reviewing and integrating community code contributions. Everyone will be welcome to submit a code contribution for approval.

We're really excited about this project and hope that all of you are too. There will be more details coming soon, such as license, availablity, and who will be heading up this project. We're still considering people for this, if you're intersted feel free to email me at [email protected], please include both your IPS Forum user name and your IPS Beyond user name. Please note that I may not be able to respond to everyone, but we do appreceiate anyone that offers their assistance.

This is just the first in a string of changes to both IPS Beyond and IP.Board that we hope will further energize our already great modding community. Keep checking this blog for news on future changes, they aren't far off. We'd also love to hear your feedback on this and any suggestions you have, please leave a comment and let us know what you think!
  • 2,406 views
Zend, the company that makes the PHP engine, offers certification for users who are interested in measuring their PHP expertise and qualifying their PHP skill level. From Zend's FAQ:





http://www.zend.com/education/zend_php_cer...tion/faq#root_4

You are tested on your fundamental knowledge of the PHP language, as well as various classes used in PHP and design patterns PHP developers should be aware of.

I took the certification test this past Monday and passed the examination. I am now officially a "Zend Certified Engineer".

  • 3,741 views
A lot of the time a significant portion of development time is spent working on items that the end user will never get to see. A case in point is the attachments system.

The attachments system was introduced back in the early days of IP.Board. During the development of IP.Board 2.2 the attachment system came under focus for two reasons.

The first reason was that we were already testing the 'new' attachment system in IP.Dynamic (as shown in this movie) and we wanted to introduce that into IP.Board. The original system forced one to wait for an entire page reload before continuing with a post. The new version used a fancy concoction of javascript and iframes to upload data 'inline' - that is, without a page reload. Naturally, AJAX (XMLHttpRequest) would have been an obvious choice but it is impossible to upload data using current XMLHttpRequest methods.

The second reason was that the code was due an overhaul because it was originally developed long before we had our components system in place. This made the original system inflexible and not very extensible. Infact, Remco had to maintain his own attachments system for the IP.Blog component which duplicated PHP code, HTML templates and SQL information.

With this in mind, we abstracted the code into component friendly modules. This allowed one to simply create a new module to manage the component's settings and upload paths. The main attachment class handled the rest. This saved us a lot of code re-use and allowed us to store attachments from several components in one table.

We think the new interface alone is a marked improvement over the old system. It's much quicker and allows one to upload several attachments quickly.

We have plans to further abstract the attachments system in a later version of IP.Board to allow attachments to be saved and retrieved in different formats.

This rather minor feature really highlights how new web technologies and ways of thinking can push even a secondary feature further along and how we're always looking to improve the efficiency of IP.Board and its components.
  • 2,052 views
Last time I talked in very broad strokes about how we developed IP.Board 2.2, today I'm going to go into detail on exactly how the new profile system evolved from concept to the finished product you see today.

Our initial goal was to bring some of the social network concepts to the profile system, without going overboard and turning it into a myspace clone. This is a fine line we walk in adding any new feature, how do we make this useful without going to far? We knew that we didn't want to let users customize the CSS or HTML for their profile image, that introduces any number of security and other technical concerns. We thought about letting users move blocks around, to give them some amount of customization, but in the end that was dropped due to the time involved. Here's a portion of the spec we came up with this for this feature:




From that basic spec, Rikki created this mock up:



This is generally how we work with a major feature, we create a rough outline of the features we want to include and then create a mock up to make sure everyone is on the same page. This mock up is quite a bit different from the final product, but you can see most of the elements of the final profile in it. A lot of things changed, the location of the profile picture for example. While this design looks cleaner, it's also less flexible, what if the user wants larger images? With this mock up there isn't much room for that. Also the tabs are clearly different, while we liked these tabs, they did not really fit in with the overall design of IP.Board.

Here's an early shot of the profile system actually running:



This has much more of the final functionality included, even if the design is not quite there yet. You can see that we've already changed how the profile picture looks, as well as how the tabs look. Another major change is that the comments are displayed below the main content area, rather than on the right where they eventually ended up. This change was made for a number of reasons, if the main content area had a lot of information, you'd have to scroll to find the comments and could easily miss them. So we moved them, but added a tab to the content area so that you could view them there if you want.



This screenshot shows a few more changes, you can see the options to edit gender, location, and birthday inline with the profile view. You can also now rate the user as well as see their gender icon next to their name in the visitors/comments/friends block. The options drop down was also added to the top right of the name block, although it would eventually move to the left hand menu.

And here's the final result: My Profile

Through the entire process our staff is constantly reviewing the latest build of the profile and making suggestions. We also brought our test group in around the second screenshot you see, they provided valuable feedback that helped a lot in shaping the final product. They were given a few different builds that included the profile, before we announced the feature to the general public.

Not everything that we wanted made it in to the final product, that happens with essentially every single feature. For example, multiple personal profile photos did not make it, even though we really wanted that. You have to know when to call it a day though, or you'll never be done. We decided that the particular feature did not offer enough of an improvement over what we already had with gallery integration, so it was dropped.

That was another important concept for this feature, we had a lot of user information out there via our various components. We wanted to pull all that data into a central location, to provide much tighter integration and a better overall flow to our products. We also wanted to give mod authors the ability to easily add their mods to the profile tabs.

So to wrap this up, we wanted to bring a fresh look to the profile and at the same time move IPB forward by bringing in social networking concepts where appropriate. I personally think we did a pretty good job of this and we all hope that you agree. If you have any questions or want more info, please ask and we'll do our best to answer.
  • 2,194 views
I see this question come up once in awhile on the forums and I thought it would be nice to give you a little behind the scenes information on how we designed IP.Board 2.2.

When we map out a new release, we usually have a specific goal in mind for that release. This can be anything from increasing security, reliability, new features, or some combination of the three. For example, when we started mapping out IP.Board 2.2 the overriding goal of the release was to streamline the software and make it easier to use. We didn't want to focus on adding a lot of new features, we wanted to improve what was already there.

We spent a lot of time looking over every section of the forum and figuring out how we could make everything easier to use. We already knew most of the areas that needed improvement from our day to day customer service issues. We ended up with a huge list of tweaks, enhancements, and minor features that we wanted to include in 2.2.

With development of 2.2 now underway, we began discussing adding one major feature to the release to add a little flavor. We decided that the profile could really use a overhaul, it really had not changed much since 1.0 and was one of the more stagnat portions of the forum. In fact a new profile system was something we had discussed off and on for a few years and with social networks on the rise, it seemed a good time to finally make those changes to IP.Board. Also, while the profile system was certainly a massive change, it still was more or less inline with our goal of improving existing functionality.

We also selected a small group of customers to test 2.2 as it was developed and give feedback on the changes we were making. They were shown the profile system in a few different stages and their feedback was instrumental in the final profile.

All the while this is going on, we continue to closely monitor the feedback forum and keep an internal list of features we want to add to the board. This list basically breaks down into three sections: Include in this release, would be nice in this release, and to be included in a later release. Anything that fit in with our goals for this release found it's way onto one of the first two lists. Anything that did not, but was still a good idea, found it's way onto the third list. After 2.2 was feature locked, everything left was moved to the last category.

That's obviously a pretty broad overview of the process, but I think it gives you a good idea of how we handled 2.2. I plan to go into more detail on some of these points in the next couple weeks. If you have any questions about our development process, feel free to post them here and we may blog on it in the future.
  • 2,435 views
Everyone has actually been quite busy lately even with the lack of Blog and News announcements. We thought it time to post something here so you knew we had not all decided to take a month off or something.

After any large release there is a lot of "clean up" work to do like starting on small updates to fix issues or going back to some neglected projects and finishing them up. Our staff has been working hard to do just that and are nearly done and ready to move on to more exciting things.

As stated in a previous entry: we are working on the IPS Beyond enhancements and are quite excited about getting IPS Beyond upgraded. More on that in the coming weeks.

Don't forget that we are hiring! See the job postings announcements for details.

There is a lot of development resources being focused on the IPS Business product line. We will be posting the first official preview of this product line in the coming weeks. We are extremely excited about our approach to business services and are looking forward to releasing this entirely new product line.

Thank you to everyone who has given feedback and noticed our recent customer service improvements. We have another round of customer service improvements that will be phased in soon so expect things to continue to improve. We will also be posting a survey next month for existing customers and hope you can give us ideas.

That's all for this update - we will be posting again soon. Thanks!
  • 2,114 views
Just a quick note on support response times for those not on a guaranteed SLA:

We recognize and apologize for the recent slower than normal response times to support tickets. The release of IP.Board 2.2.0 is causing a huge increase in volume.

The influx of new tickets is starting to calm down and things should be returning to normal soon.

To speed resolution for your support tickets please be sure to include your login information in your original ticket. If you do not, the tech support team is forced to move on to another ticket which slows down the whole process.

Thanks for your understanding! We're working on catching up now.

As an example: from the date of this post, in the last 24 hours the tech support team has sent out 731 replies.
  • 2,584 views
Now that IP.Board 2.2.0 is out and being well-received we are going to turn our focus to IPS Beyond. If you are not familiar with IPS Beyond already it is our official customer resource site.

At IPS Beyond customers can enjoy an informal atmosphere in which they can receive customer-to-customer technical support, chat about the products, share tips and tricks, and more. There are also modifications available for download to extend the feature set of your boards.

Many ask why they should use IPS Beyond when tickets are available and the short answer really is: it's up to you. You can certainly use our ticket system if you want the response times quoted under your license type or if you prefer your assistance made in private directly with our staff. IPS Beyond is great for people that want to take our products beyond (har har) what they would normally do or need help in areas not covered by our official support.

Ok, definition done, now here are the upcoming plans:
The web site will become... a web site, so not all the features are interlinked with the forums Components provided directly from IPS! Some free some low cost. Premade skins directly from IPS to start off your forum customizations Greater recognition and rewards for those active members of our community who help others and provide modifcations/skins. Tighter integration between IPS Beyond and our company forums
Work has already started on the revamp. We will keep you updated. There are lots of details we are still sorting out so give the IPS Beyond team time to get the pieces together... you should be quite pleased.
  • 2,744 views
After literally years of paperwork and waiting on the government's United States Patent and Trademark Office to do its thing we have, at long last, a registered trademark. While our logo and name were always a trademark in the ™ sense they are now a registered trademark in the full on always fun
  • 2,355 views

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.