Jetpack Blog

Parse.ly | Python Data Engineer or Infrastructure Engineer | Remote | Full-Time | https://parse.ly Are you a Python programmer based in North or South America, interested in large-scale data processing (terabytes per month, petabytes in our archive), and making use of massively-parallel computing architectures, such as those behind Spark and Dask? Do you have any existing interests in real-time streaming data, such as can be powered by systems like Apache Kafka and Redis Streams? Or, are you a DevOps-minded Linux expert with a love of cloud automation, configuration management, and immutable architecture? If so, then you should apply for our fully distributed team, since we are hiring! Python Data Engineers[1] write code that runs on hundreds of cloud nodes, using best-in-class distributed database technologies like Kafka, Cassandra, and Elasticsearch. Infrastructure Engineers[2] focus their Python and Linux skills on cloud server automation, such as Ansible and Terraform. Folks with both skillsets are on the same team, in the spirit of "true DevOps". Members of this team power a massive time series analytics engine and content crawl database that offers an elegant user experience to hundreds of enterprise customers. We do all of this on a team that's "small enough to be nimble, but large enough to be dangerous." Right now, we are ~20 total product/engineering team members, spanning skills like backend Python batch / streaming jobs, frontend JavaScript / D3.js / Vue.js…

I can't speak for blogging usecases, but for agency websites we would disable revisions and a bunch of other things for every single wordpress installation(even the blog posts that show up on the main admin area) Heck even Jetpack, Automattics official plugin, recommends limiting revisions: https://jetpack.com/blog/wordpress-revisions/ Lastly, Wpengine never fully disabled post revisions, they just limited it to 2-3.

Searching for “jetpack” in a fresh —no cookies— browser session returns: • https://jetpack.com/ • https://twitter.com/jetpack • https://wordpress.org/plugins/jetpack/ Which are the canonical URLs for JetPack, by Automatic. KidkArolis will have a hard time promoting his project. --- My suggestion for KidkArolis is to rename his project to one fo these: • “ConvePack” considering the slogan “Webpack made more convenient” • “WrapPack” considering the description “Jetpack wraps webpack” • “SimplePack” assuming his project is simpler than WebPack

This project is not a plugin API though, it's in a completely different universe. If you must complain about a project called "Jetpack", point your arrows towards Wordpress[1]. [1] http://jetpack.me/

WordPress recently added 'Tiled' galleries via their JetPack plugin. It seems like a similar approach. You can see an example gallery here: http://ma.tt/2013/07/jay-z-picasso/ Additional info: http://jetpack.me/support/tiled-galleries/ Code: https://github.com/crowdfavorite-mirrors/wp-jetpack/tree/master/module…

I suspect WordAds support will appear as an update to Jetpack (WP.com powered stats etc. for self-hosted sites - http://jetpack.me/) before too long.

One of Matt's complaints was that WPE disabled revisions...which JetPack (owned by Automattic) suggests to do in order to improve performance. https://jetpack.com/blog/wordpress-revisions/ I ran servers for an agency with ~1200 WordPress installs on Azure VMs, and I disabled revisions on every one of the sites. How is that different? Did I fiddle too much, despite it being in official documentation on how to do so? Even despite it being actually recommended by Automattic itself for performance improvements? Many of his complaints don't add up. The copyright and WP confusion, I get...but the rest is largely non-sense. Even his Stripe/Woocommerce complaint is largely bunk. The best outcome is for Matt to step down, Wordpress.org/WP Foundation gets sold to multiple hosting providers (WordPress.com, WPE, 1&1, GoDaddy, etc) and they all commit x amount of money to the project (given it is a very important platform for all of them) and in exchange WPE drops its suit. Unfortunately, I doubt that will happen, because some of this seems very ego driven.

Automattic (WordPress.com, Jetpack, WooCommerce, .blog, Polldaddy, Gravatar) | Search Wrangler | Full Time | REMOTE We're a distributed company with employees in >60 countries. Help us influence search and recommendations for the 30% of the Web that runs on WordPress. We're looking to take our Elasticsearch infrastructure up a few notches. A bit on what we're working on: - We've launched multiple applications for search, related posts, and recommendations over the years. Recently we launched a consumer version of our site search product as a part of our Jetpack plugin: https://jetpack.com/features/design/elasticsearch-powered-search/ - We want to continue improving our search algorithms for the billion plus monthly users of our search systems. - Search is not just about the algorithm. We're working to build great user interfaces and product integrations that engage users. No walls around the garden. Make the Open Web a smarter place. http://automattic.com/work-with-us/search-wrangler/ Our hiring process can take a bit of time. Read about it here: https://www.google.com/search?q=automattic+hiring+process#q=automattic…

> Is it simply because no such product exists? It's definitely possible! You could self-host WordPress, then use the Jetpack plugin, which can support premium content options (https://jetpack.com/support/newsletter/paid-newsletters/). You could also do this with WordPress.com (https://wordpress.com/blog/2020/06/04/premium-content-and-paid-newslet… I'm sure there are even more solutions, or you could roll your own -- WordPress is extremely flexible. Disclaimer: I work for Automattic. I haven't set up a premium blog before, but it's definitely possible to self-host something very similar to substack.

A link to the article on Jetpack's website: https://jetpack.com/2022/01/18/backdoor-found-in-themes-and-plugins-fr…

source, instead of this blog spam: https://jetpack.com/2022/01/18/backdoor-found-in-themes-and-plugins-fr…

A few hops to get to the list of known backdoored themes and plugins: https://jetpack.com/2022/01/18/backdoor-found-in-themes-and-plugins-fr…

> does anyone know why the functionality there requires a wordpress.com account (or rather, are there any efforts towards being able to self-host that part?)? The list is long: http://jetpack.me/features/ (probably half of those require the connection) Examples include stats (a pain to scale on shared hosting), related posts (also known to kill database servers), site uptime monitoring, image CDN (including on the fly thumbnailing), and so on. It basically provides the things that you probably don't want to self-host. You get some of the scaling of WordPress.com while being able to do your own thing (plugins, custom theme, etc.).

Sort of. WordPress provides the gallery; the carousel comes from the Jetpack plugin [1] which is included on wordpress.com sites and can be installed [2] on self-hosted sites. [1] http://jetpack.me/support/carousel/ [2] http://wordpress.org/plugins/jetpack/

The Publicize module of the Jetpack WordPress plugin allows that for a limited set of services: Facebook, Twitter, LinkedIn, Tumblr, Google+, and Path. http://jetpack.me/support/publicize/

> Just realised it has a kickass gallery viewer Actually the kickass gallery viewer works on all WordPress.com blogs regardless of the theme. We call it "Carousel" [1] and it is also available for self-hosted WordPress installs in Jetpack [2] [1] http://en.blog.wordpress.com/2012/07/12/around-the-carousel-again/ [2] http://jetpack.me/2012/07/13/jetpack-1-5-with-carousel/

I wouldn't say "less populated". This phrasing yields vast green pastures and the odd pioneer who could just drive a stake anywhere and claim acres upon an acres for themselves. I don't think that's a correct comparison. The Web isn't a physical commons that suddenly got crowded. It's a mesh of hypertext and interlinked pages that just keeps expanding infinitely in all directions. How information gets linked is a reflection of our collective mental model. The crux then is to control or influence where links are pointing to. Creating a hyperlink is arguably the most powerful thing you can do on the Web. Hence why true walled gardens such Facebook, Twitter, Instagram,... discourage adding links to your content. The shoddy way to add a link in a comment (if possible) is totally intentional. Then there's the fact that in the past decade billions have started using social media to publish their thoughts. But then you have to consider that those same billions never truly left those walled gardens. It's like they entered the theater but keep lingering forever in the foyer. This isn't bad in itself... unless you start to consider that all content is equal and turn this into a zero sum game: you either move towards social media, or you publish your content on your own domain. If you're a small commercial venture, arguably there's little point in investing in a 200k$ website and you're better off starting a FB page. There's nothing wrong with that. Conversely, you might derive a…

Have you seen this? http://jetpack.me/support/json-api/