Help
RSS
API
Feed
Maltego
Contact
Domain > blog.radiant3.ca.s3-website-us-east-1.amazonaws.com
×
More information on this domain is in
AlienVault OTX
Is this malicious?
Yes
No
DNS Resolutions
Date
IP Address
2020-11-24
52.217.96.107
(
ClassC
)
2024-06-12
52.216.104.10
(
ClassC
)
Port 80
HTTP/1.1 200 OKx-amz-id-2: K3ztI5H0FooPdczQLzypXk7I9GQKFQHaeZqTVuWJEpzN7FMAiEVrFJyO606di5oE9KogRiQoCyUx-amz-request-id: P0Q6JD0RTRZETH5EDate: Wed, 12 Jun 2024 23:18:31 GMTx-amz-meta-s3cmd-attrs: atime:1534525072/ctime:1534525072/gid:20/gname:staff/md5:edc64541cbf4068d5fae3f0da5ef60a9/mode:33188/mtime:1534525072/uid:501/uname:davidmarquisCache-Control: max-age86400Last-Modified: Fri, 17 Aug 2018 16:57:59 GMTETag: edc64541cbf4068d5fae3f0da5ef60a9Content-Type: text/htmlServer: AmazonS3Content-Length: 16227 !DOCTYPE html>html langen>head> meta namegenerator contentHugo 0.47 /> base hrefhttp://blog.radiant3.ca/> meta charsetUTF-8> meta nameviewport contentwidthdevice-width, initial-scale1.0> meta http-equivX-UA-Compatible contentIEedge> title>Radiant3 Blog | Radiant3 Blog/title> meta nameauthor contentDavid Marquis> link relstylesheet hrefcss/style-c60d4803cb.css> link relstylesheet href//cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css/> link hrefhttp://blog.radiant3.ca/index.xml relalternate typeapplication/rss+xml titleRadiant3 Blog /> link hrefhttp://blog.radiant3.ca/index.xml relfeed typeapplication/rss+xml titleRadiant3 Blog /> meta propertyog:title contentRadiant3 Blog /> meta propertyog:url contenthttp://blog.radiant3.ca/ /> meta propertyog:image content//www.radiant3.ca/images/logo-square.png /> meta propertyog:image:type contentimage/png /> meta propertyog:type contentwebsite /> link relcanonical hrefhttp://blog.radiant3.ca/ /> link relapple-touch-icon hrefapple-touch-icon.png> /head>body classhome>header> div classcontainer> a classbrand hrefhttp://blog.radiant3.ca/> img classdesktop src/images/logo.png/> img classmobile src/images/logo-mobile.png/> /a> nav classnavbar> ul> li>a href/>Articles/a>/li> li>a href/page/about/>About/a>/li> li classicon>a hrefhttps://github.com/davidmarquis titleGitHub profile>i classfa fa-github>/i>/a>/li> li classicon>a hrefhttp://stackoverflow.com/story/davidmarquis titleStackOverflow profile>i classfa fa-stack-overflow>/i>/a>/li> li classicon>a hrefhttps://ca.linkedin.com/in/davidmarquis titleLinkedIn profile>i classfa fa-linkedin>/i>/a>/li> /ul> /nav> /div>/header>div idcontents> div classcontainer> main> h6>Recent Articles/h6> article classsummary> h3>a hrefhttp://blog.radiant3.ca/2016/11/22/angular2-lazy-load-images-with-blazy/>Angular 2: Lazy-loading images using bLazy.js/a>/h3> time>Nov 22, 2016/time> div> I recently had the need to integrate bLazy in an Angular 2 project. This is a pure Javascript library so the integration was straightforward but it does have a few drawbacks to be aware of, especially due to the way Angular renders elements.The trick was wrapping bLazy initialization inside a setTimeout() which seems to be the only way for bLazy to properly set itself up.Here’s the code: a hrefhttp://blog.radiant3.ca/2016/11/22/angular2-lazy-load-images-with-blazy/>Read more.../a> /div>/article> article classsummary> h3>a hrefhttp://blog.radiant3.ca/2016/11/21/angular2-directive-responsive-conditional-output-using-css-media-query/>Angular 2: Structural directive for responsive conditional output using a CSS media query/a>/h3> time>Nov 21, 2016/time> div> Media queries are useful to adapt the way elements on a page are displayed, or even show/hide elements based on the viewport size.When working with Angular 2, there might be times where you not only want to conditionally show or hide an element depending on the viewport size, but you also need to make sure that your component does not even get instantiated when the app is run on a mobile or desktop. a hrefhttp://blog.radiant3.ca/2016/11/21/angular2-directive-responsive-conditional-output-using-css-media-query/>Read more.../a> /div>/article> article classsummary> h3>a hrefhttp://blog.radiant3.ca/2016/11/21/new-home-for-this-blog/>A new home for this blog/a>/h3> time>Nov 21, 2016/time> div> If you were following me on my old blog (davidmarquis.wordpress.com), you’ll notice that everything is now being redirected here. A new cleaner and simpler skin for the blog but with the same content as before.I know a few of you were following me on news readers (i.e. Feedly). Although new articles should continue to work as before, I strongly suggest you remove the old blog (called “Remember to Breathe”) from your sources and add blog. a hrefhttp://blog.radiant3.ca/2016/11/21/new-home-for-this-blog/>Read more.../a> /div>/article> article classsummary> h3>a hrefhttp://blog.radiant3.ca/2013/09/17/a-few-puppet-best-practices/>A few Puppet best practices/a>/h3> time>Sep 17, 2013/time> div> Puppet, the popular configuration management tool, can get tricky at times. After a few months of using Puppet to manage our servers at work, a few practices have emerged as good, recommendable practices. I wanted to share a few of them with the rest of the world here so that beginners get a head start but also to get a good base for discussion with more seasoned Puppet users. a hrefhttp://blog.radiant3.ca/2013/09/17/a-few-puppet-best-practices/>Read more.../a> /div>/article> article classsummary> h3>a hrefhttp://blog.radiant3.ca/2013/08/25/testing-your-puppet-manifests-using-vagrant/>Testing your Puppet manifests using Vagrant/a>/h3> time>Aug 25, 2013/time> div> We’ve recently started using Puppet to provision our servers really seriously at work. All of our new servers are systematically provisioned using Puppet, and we now have a rule that nothing on servers can be changed by hand, every single bit needs to be managed by Puppet.Managing servers using Puppet is extremely useful and powerful, but you also need to know what you’re doing because a small untested change in your Puppet manifests could introduce instability (or worse! a hrefhttp://blog.radiant3.ca/2013/08/25/testing-your-puppet-manifests-using-vagrant/>Read more.../a> /div>/article> article classsummary> h3>a hrefhttp://blog.radiant3.ca/2013/03/28/tip-adding-a-local-http-proxy-when-using-yeoman-1-0-with-grunt-and-livereload/>Tip: Adding a local HTTP proxy when using Yeoman 1.0 with Grunt and Livereload/a>/h3> time>Mar 28, 2013/time> div> UPDATE Grunt and the plugins ecosystem is moving quite fast, and thus this post is a bit outdated now. Although the concepts still apply, Livereload is now embedded in the “watch” plugin and the way to configure the “connect-proxy” plugin to achieve a local proxy to your Web app has changed quite a bit. Documentation has also improved so kudos to the Grunt community! Yeoman is a Javascript code generation and application bootstrapping framework that integrates many extremely cool, bleeding edge technologies for streamlining frontend rich Javascript application development. a hrefhttp://blog.radiant3.ca/2013/03/28/tip-adding-a-local-http-proxy-when-using-yeoman-1-0-with-grunt-and-livereload/>Read more.../a> /div>/article> article classsummary> h3>a hrefhttp://blog.radiant3.ca/2013/01/03/reliable-delivery-message-queues-with-redis/>Reliable Delivery Pub/Sub Message Queues with Redis/a>/h3> time>Jan 03, 2013/time> div> UPDATE I have open-sourced a Java implementation of the below principles called “RedisQ”. Enjoy! Redis is a high performance key-value datastore that differs from other key-value solutions in the way it handles values. Instead of just storing values as simple strings, it recognizes multiple specific data types such as Lists, Sets, Hashes (maps), Strings or Numbers. Each data type has its own set of features to manipulate the data it contains in an atomic manner, making it an ideal tool for highly distributed system where concurrency is a potential issue. a hrefhttp://blog.radiant3.ca/2013/01/03/reliable-delivery-message-queues-with-redis/>Read more.../a> /div>/article> article classsummary> h3>a hrefhttp://blog.radiant3.ca/2011/12/03/small-team-multiple-projects-agile-planning/>Small team, multiple projects: an Agile approach to planning/a>/h3> time>Dec 03, 2011/time> div> Context: you have a small team of 5 people, evolving in a highly dynamic environment with small projects (2-4 weeks, sometimes less, sometimes more) coming all over the place for the team to realize. This is a very usual pattern observed in agencies, or smaller teams dedicated to professional services (services to clients).How do you approach people planning (a.k.a “resource planning”, although I won’t hide my aversion for the term “resource” when referring to a person) in that kind of context? a hrefhttp://blog.radiant3.ca/2011/12/03/small-team-multiple-projects-agile-planning/>Read more.../a> /div>/article> article classsummary> h3>a hrefhttp://blog.radiant3.ca/2011/10/19/easier-builders-in-java/>Easier builders in Java/a>/h3> time>Oct 19, 2011/time> div> Anyone that has used the builder pattern for building simple Pojo-style Java classes is probably aware that writing these builder classes quickly becomes quite unpleasant and definitely not fun. You quickly realize that your builders often mimic the structure of your Pojo’s setters, finding yourself almost duplicating half of Pojo’s code for the sake of the pattern.Following a recent post from Eric Mignot and a few prior reflections I had on optimizing the process of writing these builders, I have come up with a solution that will, I hope, greatly simplify trivial cases (that is, building simple pojos) and, eventually, as the tool evolves, allow for slightly more complex cases to be covered. a hrefhttp://blog.radiant3.ca/2011/10/19/easier-builders-in-java/>Read more.../a> /div>/article> article classsummary> h3>a hrefhttp://blog.radiant3.ca/2011/10/07/delivering-software-more-efficiently/>Delivering software more efficiently/a>/h3> time>Oct 07, 2011/time> div> Organizations today are always looking for ways to improve how they build software. To stay competitive on fast-paced markets, they have to optimize the delivery pipeline to bring features from ideation to market more rapidly. Many rightfully seek solutions by adopting agile or lean practices. To be fully effective, these methodologies also need to be supported by rigorous engineering practices such as those brought forward by Extreme Programming. Executed correctly, these are all very good ways of optimizing the way you and your team build your software. a hrefhttp://blog.radiant3.ca/2011/10/07/delivering-software-more-efficiently/>Read more.../a> /div>/article> div classpagination>Page 1 of 2 a href/page/2/>Next Page/a>/div> /main> aside> section classfeatured> h6> Featured Articles /h6> ul> li>a hrefhttp://blog.radiant3.ca/2013/09/17/a-few-puppet-best-practices/>A few Puppet best practices/a>/li> li>a hrefhttp://blog.radiant3.ca/2013/01/03/reliable-delivery-message-queues-with-redis/>Reliable Delivery Pub/Sub Message Queues with Redis/a>/li> li>a hrefhttp://blog.radiant3.ca/2011/12/03/small-team-multiple-projects-agile-planning/>Small team, multiple projects: an Agile approach to planning/a>/li> /ul>/section> section classtags> h6> Articles by Tags /h6> div classtagcloud> a hrefhttp://blog.radiant3.ca/tags/agile>agile/a> a hrefhttp://blog.radiant3.ca/tags/android>android/a> a hrefhttp://blog.radiant3.ca/tags/angular2>angular2/a> a hrefhttp://blog.radiant3.ca/tags/angularjs>angularjs/a> a hrefhttp://blog.radiant3.ca/tags/devops>devops/a> a hrefhttp://blog.radiant3.ca/tags/frontend>frontend/a> a hrefhttp://blog.radiant3.ca/tags/grails>grails/a> a hrefhttp://blog.radiant3.ca/tags/grunt>grunt/a> a hrefhttp://blog.radiant3.ca/tags/hibernate>hibernate/a> a hrefhttp://blog.radiant3.ca/tags/java>java/a> a hrefhttp://blog.radiant3.ca/tags/javascript>javascript/a> a hrefhttp://blog.radiant3.ca/tags/management>management/a> a hrefhttp://blog.radiant3.ca/tags/maven>maven/a> a hrefhttp://blog.radiant3.ca/tags/mobile>mobile/a> a hrefhttp://blog.radiant3.ca/tags/mq>mq/a> a hrefhttp://blog.radiant3.ca/tags/puppet>puppet/a> a hrefhttp://blog.radiant3.ca/tags/redis>redis/a> a hrefhttp://blog.radiant3.ca/tags/spring>spring/a> a hrefhttp://blog.radiant3.ca/tags/testing>testing/a> a hrefhttp://blog.radiant3.ca/tags/vagrant>vagrant/a> /div>/section>/aside> /div>/div>div classcontainer> footer> div classrow> div classthree columns> h6>Contents/h6> ul> li>a href/>Articles/a>/li> li>a href/page/about/>About/a>/li> /ul> /div> div classthree columns> h6>Get In Touch/h6> ul> li classicon>a hrefhttps://github.com/davidmarquis>i classfa fa-github>/i> GitHub/a>/li> li classicon>a hrefhttps://ca.linkedin.com/in/davidmarquis>i classfa fa-linkedin>/i> LinkedIn/a>/li> li classicon>a hrefmailto:david@radiant3.ca>i classfa fa-envelope>/i> Email/a>/li> /ul> /div> div classsix columns> h6>Latest Posts/h6> ul> li>a hrefhttp://blog.radiant3.ca/2016/11/22/angular2-lazy-load-images-with-blazy/>Angular 2: Lazy-loading images using bLazy.js/a>/li> li>a hrefhttp://blog.radiant3.ca/2016/11/21/angular2-directive-responsive-conditional-output-using-css-media-query/>Angular 2: Structural directive for responsive conditional output using a CSS media query/a>/li> li>a hrefhttp://blog.radiant3.ca/2016/11/21/new-home-for-this-blog/>A new home for this blog/a>/li> li>a hrefhttp://blog.radiant3.ca/2013/09/17/a-few-puppet-best-practices/>A few Puppet best practices/a>/li> li>a hrefhttp://blog.radiant3.ca/2013/08/25/testing-your-puppet-manifests-using-vagrant/>Testing your Puppet manifests using Vagrant/a>/li> /ul> /div> /div> p classcopyright>© 2018 a hrefhttp://radiant3.ca>Radiant3 inc./a>/p> /footer>/div>script srchttps://code.jquery.com/jquery-3.1.1.min.js integritysha256-hVVnYaiADRTO2PzUGmuLJr8BLUSjGIZsDYGmIJLv2b8 crossoriginanonymous>/script>script typeapplication/javascript src/js/lity-842cf86018.js >/script>script typeapplication/javascript>var doNotTrack false;if (!doNotTrack) { (function(i,s,o,g,r,a,m){iGoogleAnalyticsObjectr;irir||function(){ (ir.qir.q||).push(arguments)},ir.l1*new Date();as.createElement(o), ms.getElementsByTagName(o)0;a.async1;a.srcg;m.parentNode.insertBefore(a,m) })(window,document,script,https://www.google-analytics.com/analytics.js,ga); ga(create, UA-79178249-2, auto); ga(send, pageview);}/script>/body>/html>
View on OTX
|
View on ThreatMiner
Please enable JavaScript to view the
comments powered by Disqus.
Data with thanks to
AlienVault OTX
,
VirusTotal
,
Malwr
and
others
. [
Sitemap
]