I'm a trained Design Thinking facilitator and have run many workshops for clients and internal product teams.
I conduct user interviews, do comparative analysis, and constantly test designs for usability and usefulness.
From quick UX prototypes to full fidelity motion design, I use prototyping to get the necessary feedback as fast as possible.
In the IBM Cloud Garage in New York City, I lead Clients through Design Thinking workshops and apply Lean to new applications built with IBM Watson and IBM Blockchain.
As part of IBM Cloud in Austin, I designed security and infrastructure offerings and functionality and helped create both visual and usability patterns for the design system.
I graduated from the Industrial Design program with my Bachelor's in Fine Art from Brigham Young University in Provo, Utah.
While at Fahrenheit Design, I Worked closely with the Dell Enterprise designers, Austin-based startups, and on internal projects.
I was involved in all parts of design process as the only intern on the Whirlpool Advanced Design Team in Chicago.
IBM is brought Bluemix and SoftLayer, its two largest cloud platforms, together to create IBM Cloud. This was a huge endeavor that would stretch over many months. My involvement was in a critical part that needed to get done first, identity migration.
Our team was responsible for the security services offered on the platform (Vulnerability Advisor, Key Protect) in addition to the core capabilities of the platform related to identity and access management.
Users that used both Softlayer and Bluemix had a different identity (and login credentials) for each platform and frequently got them confused.
This caused many users to unecessarily reset their password or contact customer support.
As we conducted user interviews, we realized that the way our users thought about their user identity varied depending on if they started out on one platform or the other. We also learned that the way each user accesses the platform and manages their identity was different. In order to address this, we decided to create separate experiences so that we met each group's expectations.
Once we had identified the problems faced by each of our users I planned and facilitated two workshops with our product manager for the two platform teams. As a team we came up with ideas about how to target groups of users and provide a way fot them to migrate to a new identity that would work for both platforms.
As a design team we used the output from the workshop to start designing workflows and wireframes for the different experiences. We refined these by prototyping them and showing them to users before sharing them with the development team.
We found the most effective format for delivering designs to our teams was in a packet for a giving scenario. Each packet contained a diagram of the workflow, accompanying wireframes, and annotations throughout to describe the intended behavior. Ironically despite this whole initiative being about unification, the engineering teams requested different packets with their corresponding branding.
Several of the experiences had been implemented just before I moved on to a new role. Through these experiences almost 30% of the users would migrate to a new identity.
The biggest problem we ran into was that users would forget that they had migrated to a new ID. Finding for a design solution to that would have been the next project I worked on!
As part of my 3 months design bootcamp, I spent a week focussed on learning about accessibility in digital products. During this week we created a website that distilled important information for designers to design for accessibility. This website was build onto the existing IBM Design Language website.
Most IBM Designers and Developers aren't aware of the way physical disabilities impact a user's inteaction with their interface. How do we help encourage them to consider accessibility across all stages of product development?
We interviewed several designers and developers about their experiences with accessibility and we realized that depending on someone's domain maturity they had different needs. Someone with less maturity may see accessibility as a limiting factor or as an inconvenience. Someone with more maturity understands that meeting accessibility standards can help designers make a product that is easier for everyone to use.
Those who do not see accessibility as a priority are usually lacking empathy for those that accessibility affects most, the disabled. Our solution should help instill empathy for those in need.
There are many designers and developers who are interested in creating accessible software but simply don't know how. Online references are often overwhelming so it was important to make the best practices available to them in a way that is curated to their understanding.
Everyone learns better when they can see examples of theories put into practice. We wanted to include examples in our project so that designer and developers could have a head start and potentially pull useful content from the site.
As a team we only had one week to design and code our vision so we divided into smaller teams based on our research findings. I worked with a couple developers and a designer on the Empathy section. We knew going in that it is difficult to make people to feel empathy. This is especially true for disabilities because many of us have no experience similar to that of those suffering from disabilities. What we came to realize is that by augmenting the computer inputs (mouse, keyboard), we could allow visitors to experience what it is like to use the web with a disability. Based on some early tests we found that users who experienced these simulations were often surprised by the difficulty and became much more supportive of accessibility efforts.
The head of IBM Design Phil Gilbert, highlighted my teams work on empathy simulations during a presentation to the National Council on Disability. The video below is a short animation showing how the parkinson's simulation functioned. In the video you see the user start the simulation and then struggle to press the button in the center of the screen.
IBM OpenPages solutions enable customers to manage risk and compliance initiatives, helping businesses to reduce loss, improve decision-making about resource allocation, and optimize business performance. Governance, Risk Management, and Compliance (GRC) are three pillars that work together to assure that an organization meets its objectives. I worked on a team with a couple developers, visual designer and design researcher. As a team we did not have any previous experience with risk management.
This is a broad term that refers to policies, processes, managerial mechanism, values, and culture of a company. In short, how a company is operated.
Risk management is predicting and managing risks that could hinder the organization to achieve its objectives.
Compliance with the company's policies and procedures, laws and regulations, strong and efficient governance is considered key to an organization's success. Regulations. Standards. Policies. Procedures.
Business owners don't have the time or the expertise to research the GRC reports while they are trying to make decisions. Can we design a way for them to quickly understand, monitor, incorporate risk data into their decision process?
We set out to understand the domain and then to connect with the users who relied on OpenPages to do their job. The OpenPages team was looking to create a proof of concept application that would target the needs of business owners.
Business owners typically work with a risk professional to assess the impact of business decisions on the business' risk exposure, but communication and coordination can be difficult. As a result, many business owners make decisions without the insight that could be gained from GRC data. Part of the problem is that OpenPages applications were built for risk professionals and are difficult for business owners to understand and utilize.
We started the design process by tracking down risk professionals and business owners and interviewing them about their positions. The users we spoke to verified that communication between the risk professionals and business owners was difficult.
Based on this feedback and the research we did initially, we came up with three concepts. Each of concept takes a different approach to the problem and as we tested each one we discovered their strengths and weaknesses.
Our first concept, titled "Librarian," was intended to encourage comparison of risk data to gather s into related metrics. This help some of the navigational problems that we heard about from risk professionals already using OpenPages but wasn't compelling enough to make business owners want to use the product.
The "Risk-o-Meter" concept excelled in many of the ways that our first concept did not. Business Owners loved the idea of an aggregated view of risk that they could check frequently without needing to search for relevant information. They also loved that trends could be visualized. But this concept lacked some of the detail that would be necessary to influence decision making.
"Texting Plant" may be an obscure name, but this concept was also well received. The premise of this concept was to minimize the amount of time that the business owner needed to spend in the application and automate the mundane tasks involved with risk management. But this concept lacked an overall understanding of risk exposure. This turned out to be a major shortfall of this concept.
We pulled the best features of all of our previous concepts into our final, as well as some new insight into the way that business owners would like to view risk data. Business owners love to see the overall risk exposure of their business, but they also love to dissect that number. Risk Category, Line of Business, and Geography are their preferred breakdown of total risk exposure. We chose to make our concept a mobile application to make it always accessible to business owners.
In our application the business owner can view the different breakdowns and when they see something they would like to investigate further they cal select that column and see a further breakdown. They can also view a history of that category's risk exposure, and even compare those levels to the levels of actual loss events.
The product team was very excited by the work we presented. There was still a lot to be done to connect the prototype UI we built into their systems to support live data, but a team was created to pursue further development of this project and they have since released several version to their customers.
Design is a new force at IBM, but it's presence has had a huge impact on the rest of IBM as a company. People are often surprised to hear that IBM is embracing design to transform the culture of the business as a whole. They are especially surprised when they get the chance to visit and see the energy and ﬂair that make up IBM Design and the IBM Studios.
Create an event that is an expression of the emerging design culture at IBM. Allow attendees to experience what we do, how we do it, and who we are.
I was asked to help be part of a planning committee for the first IBM Design Hive, an event that would highlight the culture of the IBM Design studios. As a committee we decided that the event should feature experiences that blended digital and analog technology. This is not only representative of IBM's history as a company, but also a reflection of the strong craft culture of our studio.
We started brainstorming the experiences we wanted to build into the event. From our inspirational images several themes started to emerge. Energetic, Unexpected, Continuous, and Immersive were some of the words that resonated with the vision we had for the event.
We also created a basic style guide that would help us maintain some consistency as we brought in more people to create the different parts of the event. The use of unfinished woods was to reflect the way that IBM's transformation to a modern software company is still unfinished. The colors play off the bee theme and the hand-done type is an unexpected element for those familiar with IBM products.
One of my main contributions to the final event was creating the idea and vision for the "Tweet on a Typewriter" experience. The concept drew from IBM's own history and played of the overall theme of blended analog and digital experiences. I worked with several engineers who took this concept and did the work to retrofit an IBM Selectric typewriter.
I was also responsible for creating signage throughout the event. There were a wide variety of needs from directional signage, to informational displays, and maps and schedules. This role required a lot of collaboration because it affected all of the different groups working on experiences.
I also helped coordinate volunteers that helped construct the venue during the day preceding the event. The largest effort I helped coordinate was the post-it wall construction. It took a team of about 5 almost 6 hours to place over 4,500 post-it notes on the wall! The wall would gradually create an analog heat map as visitors pulled from the wall to leave feedback throughout the event.
The Event took place throughout the first day of SXSW. It featured speakers, interactive displays, live radio broadcast with interviews and music, data driven beer tasting, and an evening party that was featured in many articles as one of the top social events of that weekend!
What I love abobut this project is that we were able to solve a real business problem for our client in only 2 weeks of development.
Gathering, analyzing, and applying employee feedback takes so long the findings are out of date by the time they are received. If management had a better way of collecting employee feedback, they improve retention and company culture.
During our Design Thinking Workshop we identified users, pain points, and brainstormed what a solution would look like. Fifteen people attended the workshop which I facilitated with another designer. We dove into the problem space and helped our sponsor users identify three of biggest pain points that they face. They were: Timely feedback, making feedback actionable for managers, and collecting feedback again to validate you are making progress.
We brainstormed different ideas for addressing these pain points and then voted to determine the priority based on feasibility and importance. After the voting we decided that by combining three of the ideas we could start to address cover all of the pain points.
To envision what a users experience might be once our solution was complete, we did a storyboarding exercise. This helped ensure that we were all in alignment around experience we wanted to deliver.
We hypothesized that if we built an app that enables managers to conduct mini-pulse surveys and see the real-time feedback, the surveys could be more targeted, more employees would participate, and the feedback from the survey would be more actionable. To test this hypothesis we defined our MVP which we would build out and allow the client to pilot test.
A manager could quickly create a question and share a custom link out to the desired employees after a significant event or announcement.The manager could monitor results in real time and even get analysis and insights based on Watson Sentiment and Tone Analysis.
In our MVP, when an employee followed the unique link from their manager they see the question that the manager set and four emoji that represent Ver Sad, Sad, Happy, and Very Happy. The employee selects the one that best represents the way they feel, then they have the option of filling out a follow up question. When they submit their response they see an overview of all the other responses.
Our client was energized by the whole project and was so eager to test out the app that our sponsor sent out a survey to 70,000 employees, and the traffic initially crashed the app! But we quickly got it back online and our sposor described it as "addictive" and "like checking instagram." I am hoping to add a link to a demo version of this app, so check back again soon!
My close friend, a Software Engineer, and I wanted a better system for staying on top of our days and getting insight about our productivity. We couldn't find what we were looking for so we decided to build it. We call it BrainHub.
Despite trying dozens of productivity apps, the best system I had found for keeping up with everything was a paper system called bullet journaling.
But this system takes a lot of time to maintain and forgetting your notebook would throw the whole system off.
Some of the best productivity systems are still paper based. We set out to learn what they get right and make digital personal productivity more sustainable.
I conducted user interviews and created several surveys to find out how people were handling this problem today. I also asked them to imagine an app that solved this problem, and describe what that app would do.
In my initial designs I thought back to my experience using post-it notes and sketched out an interface that mimicked the idea of a digital note for each day. I continued to refine the idea as I understood the interactions that would need to take place and got feedback on the designs from others.
I heard early feedback that entries were hard to tell apart when scanning through the feed. While exploring this problem, I came up with an idea to allow users to choose an emoji for each entry. This quickly turned into one of the most popular aspects of the design!
As the designs took shape, my engineer built the the basic functionality and got it set up with the Apple TestFlight program so that we could all test it on our phones.
There's no substitute for experience. The beta improved the way we managed our days, but it also raised lots of usability questions. Even more importantly, we got to see where and when we were using the application. This led to our decision to make a big change.
Constantly checking your phone at work doesn't give the impression you're being productive. Also, checking your phone makes it easy to be distracted by another notification or app. We decided to pivot from building a mobile app first to a web app meant for a laptop.
Designing for a new platform changes everything! I started a new design process using motion wireframes to get feedback on some of the transitions and interactions in the new desktop designs.
In my mobile designs I had anticipated taps, drags, and presses enabling much of the functionality but these interactions don't translate as well to a laptop. The action menu (shown here) performed the best with our users and will enable us to dynamically change the options depending on the context.
From the beginning, we knew that data would be the key to helping people find the patterns that are difficult to recognize on your own. As we have focussed on enhancing the data captured in BrainHub and we've come to think about it in two categories: Implicit, and Explicit Data.
What days of the week are you the most productive? What things are you likely to procrastinate? Implicit data describes the context of all the actions you take within BrainHub and can help you answer questions like these. We are continuing to refine the implicit data we capture because you cannot recover this if it is not captured.
This data you track intentionally to explore an area of your life. We're adding support for a bunch of different data types (money, time, duration, value, etc) so that you can explore anything from your spending habits, to practice, hygiene, or any number of other areas of your life.
We are currently dogfooding the earliest version of the application and sharing it with some test users. Excited to share more soon!
This project is still in progress. Come back again later to see updates!
All Things X aims to unify the rapidly growing global IBM Studios through the common thread of design driven cultures. The magazine highlights the careers, goals and aspirations of IBMers around the world, celebrating the work and people that contribute to the world on a grand scale.
Celebrate the 55th anniversary of the beginning of the space race, while comparing NASA's process to the iterative process used in software development.
Just before we began working on this article, NASA released thousands of hi-res photographs from the Gemini and Apollo missions. My co-author and I were really inspired by these photographs and decided to use them to tell the story of our article. It took hours to dig through the archives to choose right photos, but doing so enhanced the experience of writing about the events photographed.
Our article would also be following the release of an update to the IBM Design Thinking guidelines. Because our article would be making parallels between modern Design and Development processes and NASA's process, we decided to incorporate reference to the new guidelines into the design of the article itself.
My co-author and I designed and wrote the article at the same time. We did this because we wanted the design and the text to tell the story and to align the design element to what was being written about. As one of the featured articles in the issue, our article was intentionally in a longer format. It took us several iterations to refine text and the designs to complement each other, but the result was a thorough covering of the events that led to the man on the moon along with a vivid journey through the imagery of that moment in history.
Our article was included in the Issue 2 of All Things X -- entitled "Spaces." Over one thousand were distributed to 21 IBM Design Studios all over the globe. Our issue was featured in For Print Only as well as recognized internally at IBM for design excellence.
I am currently getting permission to post the full article online. I will post a link when it is available!
A large insurance provider hired us to help them rethink the way they manage their disaster response teams. This project was my first exposure to the world of real estate insurance. It was a steep learning curve, but I learned to appreciate the impact of the work they do. I also felt lucky to help improve the experience of those effected by natural disasters.
Our client was hearing complaints from disaster victims that their process “takes forever” and “prolongs the pain after a tragedy.”
They came to us to help them achieve their ultimate goal of getting disaster victims their payouts faster so that they can begin the rebuilding process.
In order to achieve this goal, we had to understand the existing process and what was causing the delay in the first place. I started by investigating the process through interviews and creating a service blueprint. This helped visualize the process and align the team.
In addition to documenting the process, we also conduct user interviews to understand our users better. By creating Empathy maps for each of the users we were targeting, we were able to document our understanding of our user's motivations and behaviors.
From interviews with coordinators we discovered that burnout was a big problem. Coordinators don’t know which appraisals were completed until late in the evening. They often stay up late responding to changes and reworking the schedules and routes for the following day. The work is manual, and playing the part of the “middle man” is taxing.
From interviews with appraisers we found that despite the hard work by the coordinators, claimants were frequently late or forgot their appointment entirely. Occasionally the appraisers would be stuck for hours with nothing to do. Since they’re away from home, this lack of efficiency frustrates the appraisers.
The problems we identified inspired a new hypothesis: If we could eliminate the need for coordinators as middle men, then we could help appraisers stay productive and service claimants faster. From a team “Big Ideas” brainstorm, we came up with the idea to create a system that would automatically assign claimants to an Appraiser based on their location.
My initial wireframes explored our big idea taking inspiration from similar eperiences in ride sharing applications.
We shared initial wireframes with the appraisers and coordinators. The appraisers liked the idea of an Uber-like approach to assigning appraisers to claimants, but the coordinators had some significant concerns. Their feedback prompted us to rethink our design.
As our users pointed out, automating the appraisal system based on location would not solve our key problem. In fact, it might exacerbate the problem for those claimants that live far from the place where the appraisers happen to stay.
After the second set of user interviews, we realized that the key to eliminating the need for a middle man was empowering appraisers to manage their own routes.
One of the most important aspects for an appraiser to manage their own route is being able to adapt when claimants forget their appointments or cancel at the last minute.
Our client piloted it with a one field team (~5-8 Field appraisers) who responded to tornado damages in the Midwest. Our client saw a measurable improvement in two key metrics that indicated value for the business and for the users.
In addition to the measurable outcomes, we got great feedback when we interviewed the users involved in the test pilot.
A large US Bank asked us to help their enterprise supply chain team to manage their data center inventory. My team consisted of 8 engineers, a product manager, myself as the designer. Upwards of 20 people involved as stakeholders, experts, or sponsor users.
The Bank can’t accurately predict delivery of an order because the order’s progress through the vendor process is not transparent. The problem ripples through the organization causing unnecessary communication overhead and delaying product development.
I led a design thinking session that was attended by the different members of the enterprise supply chain team. Through the creation of empathy maps, current state journey maps, and a “big ideas” brainstorm, we gathered an in-depth understanding of our users, their pain points, and a conceptual idea for a solution.
Going into the workshop, we had a general idea that there would be 4 unique users experiencing a complex, messy process. Activities like empathy maps helped align the team around the key users and their behaviors and motivations. Defining the As-Is Process (or current state journey), allowed each stakeholder to visualize the end-to-end process experienced by the key users.
Each user struggled with issues that were specific to their role, but they were symptoms of a higher-level problem: Nobody knew what anybody else was doing!
A constant stream of update requests to the supplier, whose day slows down trying to react to them.
At one point during the workshop someone said: “Can’t we have the ‘Domino’s Pizza Tracker’ for our Purchase Orders?” After some laughter an discussion we realized that this idea captured our vision for a potential solution.
The new process we were proposing was a proactive approach to providing updates, facilitated by the supplier.
Working with our product manager, I mapped out the PO process. My goal was to illuminate this process for everyone so each user understood how they fit in.
After many interviews with each of the four users, I finally landed on a flow that met The Supplier’s needs. As it turned out, his problem wasn’t so much that he struggled to fulfill orders, but rather that continually providing status updates to the gazillions of requests he got took up most of his time!
For this piece of the design, I focused specifically on Darryl, the supplier, who is continually bombarded with requests for status updates. His motivation is to spend less time responding to those requests so he can dedicate more time to fulfilling orders.
Our client didn’t have a design system, so part of my work involved developing one for them based on their branding.
As I designed each component, I looked for opportunities for continuity. For example, the order progress indicator on the order overview page visually translates to the larger, more detailed progress indicator on the order detail page.
Here is a breakdown of each section of the order details page. The most common questions our users were looking to answer by using this tool were questions like "Where is my order?" or "When should I expect delivery?" This drove the order of information in each section and the order of each section on the page.
In the first few weeks of testing the application it eliminated status inquiries! In addition to that both the IT Project Manager and the Data Center Manager mentioned that they used the application to plan better.
While this tool was primarily designed for the supplier, his interactions with the tool directly impacted the other three users. Keeping track of everyone’s needs required frequent checkins with each of the other user groups.
As a designer I have always felt the best way to learn a new technique or software was to jump in and start using it. After getting early access to InVision Studio, a motion design tool, I created this project to teach myself the tool and develop my understanding on motion design.
"Crazy things can come true. When I see a rocket lift off, I see a thousand things that could not work, and it's amazing when they do." - Elon Musk about Falcon Heavy
I began with the idea to simply animate the liftoff stage of the Falcon Heavy rocket. But designing the rocket took me back the moment I watched the launch live and I decided to not only animate the liftoff, but all eight stages of the launch. Though challenging, the complexity of these eight steps gave me the opportunity to really explore the tool and its settings.
To further challenge myself with this new tool, I added key details to the rocket, car, and starman. This also really enhanced the experience of viewing the animations. A few of my favorite details in this project were the rocket's plumes, and the car's hub caps.
In addition to walking through the final product, this video condenses all nine hours of design work I did for this project. You will even see my initial preparations for the single stage version before deciding to go ahead and create the full eight stages.
After sharing the video of my project, I got a great response on social media. The CEO of InVision along with many members of the team that created the Studio application responded with very positive reactions, and even reached out to get access to the working file so that they can use it to inform future development. I hope you enjoyed it too!


@import java.time.LocalDate @import football.model.MatchesList @import model.Competition @import pa.FootballMatch @import views.support.`package`.Seq2zipWithRowInfo @import views.support.RowInfo @import java.time.ZonedDateTime @(matchesList: MatchesList, customLink: Option[(String, String)] = None)(implicit request: RequestHeader, context: model.ApplicationContext) @footballMatchDay(date: LocalDate, competitionMatches: List[(Competition, List[FootballMatch])], dateRow: RowInfo) = {


wroc_love.rb 2017 in a nutshell
A bit about me
- I <3 ruby, devops and whiskey
- all in for open-source software
- quality and automation are very important
- i don't have a blog
- i do consulting
comprehensive platform for insightful code analysis
- March 17-19th 2017, Wrocław Poland
- 10 speakers, 10 talks, 2 panels
- after parties ;)
when I was preparing this talk
I realized that I don't like doing this kind of talks
KARAFKA - PLACE WHERE RUBY, RAILS AND KAFKA MEET TOGETHER
Maciej Mensfeld
- kafka - is used for building real-time data pipelines and streaming apps
- karafka - microframework which was designed to simplify Kafka based applications development
- https://kafka.apache.org/
- https://github.com/zendesk/ruby-kafka
- https://github.com/karafka/karafka
MACHINE LEARNING FOR THE RESCUE
Mariusz Gil
Machine learning is not a single run of an algorithm. It's a process.
ML process
- define a problem
- gather your data
- understand your data
- prepare data for ml
- select & run algo(s)
- tune algo(s) parameters
- select final model
- validate final model
list of ruby gems for ML/DS http://gems.sciruby.com
3.2 was released
A bit of numbers
- 3 026 876 bytes of code
- 0.63% monthly growth
- 104594 lines of code
- 75.9% code in Ruby
- 4 guys handling more than 92% of code (last month)
- 1 guy with > 50% of current code base (total) ownership - Sean Schofield
Spree uses Rubocop!
But it doesn't! :(
AccessorMethodName ActionFilter Alias ArrayJoin AsciiComments AsciiIdentifiers Attr BlockNesting CaseEquality CharacterLiteral ClassAndModuleChildren ClassLength ClassVars ColonMethodCall CommentAnnotation CyclomaticComplexity Delegate DeprecatedHashMethods Documentation DoubleNegation EachWithObject EmptyLiteral Encoding EvenOdd FileName FlipFlop SpecialGlobalVars StringLiterals VariableInterpolation TrailingCommaInLiteral
But it doesn't! :(
FormatString GlobalVars GuardClause IfUnlessModifier IfWithSemicolon InlineComment Lambda LambdaCall LineEndConcatenation MethodLength ModuleFunction NegatedIf NegatedWhile Next NilComparison Not NumericLiterals OneLineConditional OpMethod ParameterLists PercentLiteralDelimiters PerlBackrefs Proc RaiseArgs RegexpLiteral SelfAssignment SingleLineBlockParams SingleLineMethods SignalException
But it doesn't! :(
TrailingCommaInArguments TrivialAccessors VariableInterpolation WhenThen WhileUntilModifier WordArray AmbiguousOperator AmbiguousRegexpLiteral AssignmentInCondition ConditionPosition DeprecatedClassMethods ElseLayout HandleExceptions InvalidCharacterLiteral LiteralInCondition LiteralInInterpolation Loop ParenthesesAsGroupedExpression RequireParentheses UnderscorePrefixedVariableName Void
So what would happen with a non-agressive Rubocop config?
(with Rubocop Rspec and Rubocop Rails)
THE OVERNIGHT FAILURE
Sebastian Sogamoso
Responsible Rails - Become the responsible Rails developer
- http://blog.arkency.com/responsible-rails/
- for free with MAKE_RUBY_GREAT_AGAIN code
- don't know if it's good, but it's for free ;)
FAULT TOLERANCE IN RUBY
Hubert Łępicki
Semian
https://github.com/Shopify/semian
- circuit breaker
- ready to use adapters (mysql, redis, net/http)
- fail fast philosophy
- works with Ruby / OS processes (but NOT threads)
- uses Unix IPC to synchronize
- modifies behaviors of third party libs
Celluloid
https://github.com/celluloid/celluloid
- turns objects into actors
- allows linking actors
- allows supervision/restarts
Ruby 3.0.0 - Guilds
http://www.atdot.net/~ko1/activities/2016_rubykaigi.pdf
http://slides.com/hubertlepicki/fault-tolerance-in-ruby
AUTOMATED TYPE CONTRACTS GENERATION FOR RUBY
Valentin Fondaratov
I'm sorry I don't remember what it was about
Fortunately there are slides
https://speakerdeck.com/valich/automated-type-contracts-generation-for-ruby
RUBY vs ELIXIR
BINDINGS IN RUBY - BEHIND THE MAGIC OF BLOCKS
Piotr Szmielew
https://speakerdeck.com/esse/bindings-in-ruby-behind-the-magic-of-blocks
http://charytatywni.allegro.pl/en/listing?sellerId=9300675
THE BABEL FISH IS DATA: A CASE STUDY
Norbert Wójtowicz
It was good so hopefully the video will be up shortly
Clojure and ClojureScript
#clojure and #clojurescript stealing best ideas from other langs
WE ALL BUILD DISTRIBUTED SYSTEMS
Maciej Rząsa
https://speakerdeck.com/mrzasa/we-all-make-distributed-systems-wroc-love-dot-rb-2017
PREDICTING PERFORMANCE CHANGES OF DISTRIBUTED APPLICATIONS
Wojciech Rząsa
https://speakerdeck.com/wrzasa/predicting-performance-changes-of-distributed-applications
PANEL - HOW TO SURVIVE IN THE JAVASCRIPT WORLD AS A RUBY PROGRAMMER AND STAY SANE
CONCURRENTRUBY V1.1.0: NEW FRAMEWORK, NEW WAY OF WRITING CONCURRENT CODE!
Petr Chalupa
http://ruby-concurrency.github.io/concurrent-ruby/Concurrent/Promises.html
Applications close April 3, 2017 at 18:00 (CEST)


please save the date
for The wedding of
Nicholas
AND
Clare
October 14 ● 2017
Indooroopilly Golf Club
Invite to follow
Add to Calendar


Format: EditTextHeight real,
Example: EditTextHeight 0.015,
Purpose: Displays Text bigger/smaller, but drops quality and dismatches the cursor. Better use FrameFont
Used in: EDITBOX, GLUEEDITBOX


SOFABoot provides developers with three ways to publish and reference JVM services
- XML
- Annotation
- Programming API
XML
Service Publish
First, we need to define a Bean:
<bean id="sampleService" class="com.alipay.sofa.runtime.test.service.SampleServiceImpl">
Then, publish the Bean as a SOFA JVM service by using the Spring extension tag provided by SOFA.
<sofa:service interface="com.alipay.sofa.runtime.test.service.SampleService" ref="sampleService">
<sofa:binding.jvm/>
</sofa:service>
In the preceding configuration, the interface parameter indicates the interface for releasing services, and the ref parameter indicates the Bean to be published as a JVM service.
At this point, we have published a JVM service success.
Service Reference
We can also reference a JVM service by using the Spring extension tag provided by SOFA.
<sofa:reference interface="com.alipay.sofa.runtime.test.service.SampleService" id="sampleServiceRef">
<sofa:binding.jvm/>
</sofa:reference>
In the preceding configuration, the interface parameter indicates the service interface, which must be consistent with that configured during the service publish. The meaning of the ID attribute is the same as Spring BeanId. A Spring Bean with the ID sampleServiceRef will be generated from the above configuration. We can inject it anywhere in the Spring context of the current SOFABoot module.
service/reference tag also supports RPC service publish, with related document: RPC Service Publish and Reference
Annotation
Warning
If a service has been annotated with @SofaService, it cannot be published in the mode of XML. Choose one mode to publish the service instead of a mixture of two modes.
In addition to publishing JVM services and reference through XML, SOFABoot also provides Annotation for JVM services publish and reference. To publish JVM services through Annotation, we only need to add an annotation @SofaService to the implementation class, as follows:
@SofaService
public class SampleImpl implements SampleInterface {
public void test() {
}
}
Prompt
@SofaService is used to publish a Spring Bean as a JVM service, which means that although you may not write the configuration of <sofa:service/>, you still need to configure the class annotated with @SofaService as a Spring Bean.
When configuring <sofa:service/> in the XML mode, you have configured an interface for the service. However, when using the @SofaService annotation, you haven’t configured the service interface. This is because when the class annotated with @SofaService has implemented only one interface, the framework directly uses the interface as the service interface. What if the class annotated with @SofaService has implemented multiple interfaces? In this case, you can set the interfaceType field of @SofaService to specify the service interface, as shown below:
@SofaService(interfaceType=SampleInterface.class)
public class SampleImpl implements SampleInterface, Serializable {
public void test() {
}
}
Corresponding to @SofaService, SOFABoot provides @SofaReference to reference a JVM service. Suppose we need to use a JVM service called SampleService in a Spring Bean, we only need to add an annotation of @SofaReference to the field:
public class SampleServiceRef {
@SofaReference
private SampleService sampleService;
}
Similar to @SofaService, you do not have to specify the service interface for @SofaReference. This is because when no service interface is specified for @SofaReference, SOFABoot directly uses the type of the annotated field as the service interface. Alternatively, you can also set the interfaceType property of @SofaReference to specify, as shown below:
public class SampleServiceRef {
@SofaReference(interfaceType=SampleService.class)
private SampleService sampleService;
}
Programming API
SOFABoot provides a mode of programming API for JVM service publish and reference, making it easy to directly publish and reference JVM services in code. Similar to the ApplicationContextAware of Spring, to use the programming API mode, first we need to implement the ClientFactoryAware interface to get the programming component API:
public class ClientFactoryBean implements ClientFactoryAware {
private ClientFactory clientFactory;
@Override
public void setClientFactory(ClientFactory clientFactory) {
this.clientFactory = clientFactory;
}
}
Take SampleService as an example, let’s see how we can use clientFactory to publish JVM services through programming API:
ServiceClient serviceClient = clientFactory.getClient(ServiceClient.class);
ServiceParam serviceParam = new ServiceParam();
serviceParam.setInstance(new SampleServiceImpl());
serviceParam.setInterfaceType(SampleService.class);
serviceClient.service(serviceParam);
In the above code
- Get the ServiceClient object through the clientFactory
- Construct the ServiceParam object, which contains the parameters required for publishing the service. Set the object to be published through setInstance method, and set the service interface through setInterfaceType method.
- Publish a JVM service by calling the service method of ServiceClient
The code for JVM service reference through programming API is similar:
ReferenceClient referenceClient = clientFactory.getClient(ReferenceClient.class);
ReferenceParam<SampleService> referenceParam = new ReferenceParam<SampleService>();
referenceParam.setInterfaceType(SampleService.class);
SampleService proxy = referenceClient.reference(referenceParam);
Similar to publishing a service, to reference a JVM service, simply retrieve the ReferenceClient from the ClientFactory object, construct a ReferenceParam, configure the service interface, and call the reference method of ReferenceClient.
Prompt
The Reference object created by dynamic client is very heavy. Do not create it frequently in actual practice and cache it in advance, otherwise there may be a risk of memory leak.
uniqueId
Sometimes, you may need to publish two services at the same time, which correspond to different implementations. By using the preceding sampleService as an example, you may have two SampleService implementations, both of which need to be published as SOFA JVM Services. By using the XML mode, you can configure as follows:
<sofa:service interface="com.alipay.sofa.runtime.test.service.SampleService" ref="sampleService1">
</sofa:service>
<sofa:service interface="com.alipay.sofa.runtime.test.service.SampleService" ref="sampleService2">
</sofa:service>
The service can be correctly published but its reference is confusing, in which case the following configuration is used:
<sofa:reference interface="com.alipay.sofa.runtime.test.service.SampleService" id="sampleService">
</sofa:reference>
However, you have no idea which JVM service is referenced by the preceding JVM.
To address such issues, SOFA introduces the uniqueId concept, which helps identify service-interface-like JVM services. By introducing the uniqueId to the preceding service publish code, the code is modified as follows:
<sofa:service interface="com.alipay.sofa.runtime.test.service.SampleService" ref="sampleService1" unique-id="ss1">
</sofa:service>
<sofa:service interface="com.alipay.sofa.runtime.test.service.SampleService" ref="sampleService2" unique-id="ss2">
</sofa:service>
Then, to use sampleService1 during service reference, set the unique-id to ss1, as shown in the following example:
<sofa:reference interface="com.alipay.sofa.runtime.test.service.SampleService" id="sampleService" unique-id="ss1">
</sofa:reference>
To use sampleService2, set the unique-id to ss2, as shown below:
<sofa:reference interface="com.alipay.sofa.runtime.test.service.SampleService" id="sampleService" unique-id="ss2">
</sofa:reference>
As mentioned above, uniqueId is used in the XML mode. When we use the Annotation mode to publish or reference JVM services, we can set uniqueID by setting the uniqueID attribute of @SofaService and @SofaReference. When we use the programming API mode to publish or reference JVM services, we can set the uniqueId through setUniqueId of ServiceParam and ReferenceParam.


which timebox and habits techniques did you try? I've never used any timebox techniques consciously, but I feel that the pomodoro technique is something I unconsciously applied to a lot of work I did during my studies, especially when writing especially long papers. Pausing for 10 minutes avery half hour sounds exaactly like my workflow whe doing that kind of tasks. I don't know if it will apply to dev work though! I also tried to establish a meditation habit several times, but it always tapered off at some point. I'll keep trying until I man age to get it, though!
What did you find interesting? The most interesting element I encountered was the "Trigger" concept for creating habit. I think it was the one thing I missed to actually make it work, and the one thing that made things work unconsciously!
What worked for you? A while ago, I managed to create a habit of running with the trigger "Go running immediately after you wake up" a while ago, without being aware of the "trigger" aspect. Very interesting to know that it was this element that made it so effective.
Which will you experiment further with? I will definitely try to get more into the habit of timeboxing tasks with the pomodoro technique, and using the breaks to get into the habit of meditating. I actually have downloaded the Headspace app! Will use it for the first time after I push this blog entry :p


{% if page.description %}
{% endif %}
WIN
£1MILLION
Predictor
Dashboard
Connections
Messages (4)
Predictions
Newsfeed
Leaderboards
Mini-Leagues
Performance
Help
Contact
{{ content }}
Powered by


Description
Rules:
• Prior online registration is required.
• It is a team event. Team size may vary from 10 to 20 members, including models, designers, choreographers, make-up artists, etc.
• Each member of the team is required to carry their ID cards.
• Theme selection is open. All the teams can have a theme of their own choice.
• Props should be arranged by the teams on their own. Use of fire, water, animals or any hazardous material is prohibited.
• Vulgarity of any kind would lead to disqualification of team from the event. Hence if the team feels that any stunt of costume design can be deemed as vulgar, it is strongly advised to consult the organizers than performing it directly on stage.
Judging Criteria:
❖ Theme: Originality, Depiction of Theme, Designing, Use of Props.
❖ Constraint: Uniqueness, Innovation and Improvisation in terms of executing the transformation.
❖ Models: Ramp walk, Stage Presence, Poise, Overall Appearance
❖ Team: Choreography, Music and Narration, Co-ordination, Relevance to the theme and Overall Performance


--- layout: post title: Cool things at the Melbourne Maker Faire tags: - Education - Open Source Software status: publish type: post published: true meta: _edit_last: '451289' jabber_published: '1326515935' _wpas_done_linkedin: '1' email_notification: '1326515943' tagazine-media: a:7:{s:7:"primary";s:0:"";s:6:"images";a:0:{}s:6:"videos";a:0:{}s:11:"image_count";s:1:"0";s:6:"author";s:6:"451289";s:7:"blog_id";s:6:"444144";s:9:"mod_stamp";s:19:"2012-01-14 04:51:28";} _wpas_skip_fb: '1' --- I'm at the Melbourne Maker Faire and a few cool things have caught my eye:


lunar luminance lights his lucent lordly lair.
leaden legs languish lazily as he lay, laconic—
lexical loquaciousness long lost.
his latent lupine lust lignifies and lengthens,
longing lonesomely for his lovely limber lioness.
with lips of luxurious labial liquer,
and licks lapping like lashing lingual lightning,
liquifying his lavish lover, luscious lyrical lubrication.


Nine Inch Nails frontman Trent Reznor unlikely winner of Country Music
by Andrew BlakeNine Inch Nails frontman and Rock and Roll Hall of Fame nominee Trent Reznor on Wednesday became the unlikely recipient of a CMA Award given out by the Country Music Association.
“Old Town Road,” a crossover hit by rapper Lil Nas X and country artist Billy Ray Cyrus, has won the 2019 CMA Award for Musical Event of the Year, the CMA announced on its website.
The chart-topping single includes a sample from a Nine Inch Nails song, “34 Ghosts IV,” resulting in Mr. Reznor and bandmate Atticus Ross each receiving co-producer credits.
Both members of the industrial rock group were recognized for their collaboration on the CMA website ahead of the association’s annual award show airing Wednesday evening.
Mr. Reznor, 54, founded Nine Inch Nails in 1988 and is the group’s only consistent member. The act has received significant accolades in the decades since releasing its debut album the following year, “Pretty Hate Machine,” including earning two Grammy Awards and several nominations to be entered into the Rock and Roll Hall of Fame. The group is currently among the shortlist of acts being considered for induction 2020.
He has largely been recognized in the past for material far outside the realm of country music, however. Both of NIN’s Grammy Awards are for Best Metal Performance, and the group has unsuccessfully been nominated in subsequent years in the categories of Best Hard Rock performance and Best Rock Song, among others.
Mr. Reznor made light of his contribution to “Old Town Road” when the song was nominated for a CMA Award. He reacted at the time by sharing an image on social media that showed the heads of both NIN members juxtaposed on the bodies of an old promotional photo for country act Brooks & Dunn.
“New world, new times…,” Mr. Reznor captioned the image.
Mr. Ross, 51, has collaborated with Mr. Reznor for the past 15 years. They have worked together on a number of NIN albums, in addition to the scores to several major motion pictures.
Sign up for Daily Newsletters
Copyright © 2019 The Washington Times, LLC. Click here for reprint permission.
Please read our comment policy before commenting.


Three days in Krakow
by Monika Suchoszek
Our visit to Krakow started with the guided walking tour in the morning to get a proper introduction of the city and its rich history. We jointed FREE walking TOUR though Krakow’s old town which started between St. Florian´s Gate and Barbican and finished at Wawel castle, located on the top of the hill with the same name (about 2.5 hours tour). Despite the really beautiful, sunny weather after one hour we could already feel that we were in the middle of Polish winter. The tour was really informative, full of interesting facts about the beginning of the city, the period of Swedish invasions and the German occupation of Krakow in World War II.
After quite decent lunch in Chimera salad bar and warm pączek (doughnut), full of energy, we visited Rynek Underground Exhibition located between sukiennice (Cloth Hall) and Mariacki Church (St. Mary’s Basilica). Archaeological works were done between 2005-2010 and revealed ruins of Krakow from even thousand years ago. Inside the museum you can walk between old market streets, watch smith, goldsmith workshops and gathered detailed information about trade routes passing Krakow in Middle ages and connecting the city with the rest of Europe.
Sukiennice (Cloth Hall) is a place were you can buy local souvenirs, most of the are hand made, like amber jewelry, lacework, cloth handicrafts, wood carvings. We also noticed that many of them were actually cheaper here than in souvenir shops at Floriańska street (main shopping street). We also tried very popular in Krakow snack, called obwarzanek, which is a kind of soft pretzel, mostly covered with sesame or poppy.
Since in Krakow we couldn’t find any snow, the next day we headed out to Zakopane, the winter capital of Poland. You can easily take a bus there (2h10min) leaving from the main bus station in Krakow.
After arriving in Zakopane, we first walked in the direction of Gubałówka (1123m) passing huge market with local souvenirs and smoked cheese called oscypek (a local specialty). You should definitely try grilled oscypek with cranberry jam, easy to find on many street stalls, really delicious! First, our idea was to walk to Gubałówka summit (around 45min), however the path was really slippery. Not risking any injuries right before my trip to the Himalayas, we decided to go for a safer option and take a cable car uphill. In this way, after 3.5 minutes of ride, we could admire the panoramic view of Tatras mountains and Zakopane :D I am not used to reach the summit with this little effort ;) There are a few restaurants, food and souvenir stalls, skiing slopes and a small wooden church on the top.
Next, we walked on Krupówki street, the main representative street in Zakopane full of hotels, restaurants and souvenir shops. On small, wooden stalls you can also buy local confitures, honey and syrups made from many different fruits. “Karcma po zbóju” was the place where we had pierogi (dumplings) with meat, one of the most famous polish dishes. After more shopping and a warm tea in one of the restaurants we headed back to Krakow.
On our last day we visited two museums; The Eagle Pharmacy (Tadeusz Pankiewicz’s Pharmacy) and Oskar’s Schindler Factory in Krakow Ghetto. The first one shows all rooms of the former pharmacy and their original roles. It is full of hidden details about how people survived life in ghetto, which medication was available at that time and which was the most popular. The book, written by the owner of this pharmacy, “The Cracow Ghetto Pharmacy” describes tragic events which occurred in the Krakow ghetto and was published just after the war. There are movies to watch, photos to touch and documents to read, no-one would be bored here!
The second museum describes Kraków under Nazi Occupation 1939-1945 and is located in the former administrative building of Oskar Schindler’s Enamel Factory at 4 Lipowa Street. Very interactive exhibition full of individual people’s dramas and stories from everyday life during Second World War. The story of Oskar Schindler who saved the lives of over a thousand people was shown in Steven Spielberg’s film Schindler’s List. Very touching exhibition, highly recommended to visit however it can get really crowded inside (necessary to book the ticket online). It took us almost two hours to visit the museum but I am pretty sure some people can spend here twice this time, walking through 45 exhibition rooms and reading endless facts about Krakow’s history.
In the afternoon we headed to Kazimierz, a place where Jewish culture was flourishing for over 500 years until 1941 when Jewish people were relocated to ghetto. You can still visit a few synagogues including The Old Synagogue where you can get more information about the most important holidays of the Jewish calendar the traditional man’s and woman’s costume. Nowadays, Kazimierz is full of atmospheric cafes and art galleries. Don’t miss a chance to try some Polish food, the restaurant “Marchewka z Groszkiem” will give you many options, too many :p Tasty food at a great price!
Souvenirs to buy:
- furs
- amber jewellery
- lacework
- cloth handicrafts
- wood carvings
- accesories with polish folk patterns (umbrella, glasses case, apron, pillow case)
- many people will be really happy to get ptasie mleczko (look section below) from Wawel or kabanosy (long thin dry sausage made usually of pork) as a souvenir ;)
Food to try:
- Pierogi - dumplings, hearty (meat, cabbage and mushrooms, Russian) or sweet version (sweet cottage cheese, apples, strawberries)
- Golonka - knuckle of pork usually with beer sauce
- Zrazy - traditional Polish beef reulade
- Gołąbki - stuffed cabbage rolls
- Bigos - stew contained sauerkraut, meat, sausage, mushrooms
- Barszcz - beetroot soup, could be served with dumplings
- Rosół - chicken brot
- Żurek - traditional Polish fermented sour soup with egg or white sausage
- Placki ziemniaczane - potatoe pancakes, very often served with pork stew
- Kompot - boiled fruit drink, very common to drink with dinner
Sweet treats:
- Pączek - Szewska street, 25 (small window with doughnuts and other sweet treats), 3.5zl
- Ptasie mleczko (Wedel company) - soft chocolate covered candy, many flavours
- Krówki - Polish fudge
- Prince Polo - Polish chocolate bar
- Obwarzanek - 1.60-2zl
Practical info:
- Rynek underground exhibition - 19zl admission fee
- Bus to Zakopane - 40zl, return ticket, few different bus companies but the same price, many connections during the day, better buy tickets one day in advance at the main bus station (Bosacka 18 street)
- Gubałówka cable car - 23zl, return ticket
- Memory trail ticket - 28zl, combined ticket to The Eagle Pharmacy, Oskar Schindler’s factory and Pomorska street museum (not visited by us)
- The Old Synagogue - 10zl, admission fee
- Train from Kraków Główny to Airport Balice - 9zl one way
Subscribe via RSS


{% extends "layout.html" %} {% block page_title %} Your details are saved {% endblock %} {% block content %} {% include "../includes/phase_banner_beta.html" %} We have saved your answers When you are ready to carry on with your application, request a new link You need to complete the rest of the application by: 25 November 2016 {% include "../includes/help.html" %} {% endblock %}
When you are ready to carry on with your application, request a new link
You need to complete the rest of the application by:
25 November 2016


{% extends 'saved_base.html' %} {% load socialaccount %} {% block content %}
{{ issue.description }}
More InfoYou currently do not have any saved issues, {{ user.first_name }}! Click here to go to the issues page to browse issues you are interested in saving!
{% endif %} {% endblock %}


--- layout: page title: Tileables ---
I created Tileables a while back to fill a personal need and to give something back. With needs changing and time limited, I’m putting the project on pause and archiving the existing packs here. The original downloads are still complete, containing both PNG and PAT formats to use as you’d like. If you need something a bit more custom, feel free to get in touch!
The very first pack released! It's a collection of 12 line patterns in varying styles and orientations. These patterns work really well when layered on top of some of our other textures.
DownloadThe paper pack contains 24 mixed textures and spans a variety of paper types. From plain and creased to textured parchment types. If you're looking to add a subtle bit of depth to a background without it being too much, the paper patterns are for you.
DownloadA mixture of 20 rust and decay textures, including different surfaces and levels of detail makes these textures perfect for creating a grunge or urban background. Used carefully, they can easily blend into other backgrounds for a more subtle look.
Download20 fabric based textures which cover a wide range of materials from cotton to leather and everything in between. There are varying levels of detail in each one, making this pack a versatile one which is suited to a lot of different applications.
Download20 different and unique wooden textures and patterns. This pack covers various different types of wood from planks and pieces to more abstract details and close ups. Subtlety is key with these to avoid the old photo-realistic cliché wood look!
DownloadOne of the most requested pack types I got over email was to create some grids and so here you go! There's 35 individual grid patterns in a variety of sizes, widths and styles. From small 4px squares with a 1px stroke, all the way up to 50px squares with 3px strokes. There's also dotted/dashed styles included for complete customization. These patterns work best when combined with natural textures and at a low opacity.
DownloadI’ve wanted to answer the requests for a nature-based pack for a while and here it is! Subtlety is a must with this pack — the textures are very contrasting and shouldn’t be used without filters!
Download


Register TasKsaT
Account
Follow Migration
Wizard
Enjoy the results
migrations performed
Software Migration cloud based, accurate and secure data transfer
requires no technical skills and no software to install
a team of qualified tech gurus at your disposal
View all testimonials
07/03
2014
The Evolution of CMS Platform: From Caveman to Homo Sapiens
The history of humanity has been starting counting from primitivity and simplicity to complexity, duality, and multifacetedness. While tracing back to the big bang of web technologies, content management systems (CMS) began their starting point from hard coding to comprehensive usability and intuitive operations
05/03
2014
Quick Wizard: Website Migration Has Never Been Faster
The history of humanity has been starting counting from primitivity and simplicity to complexity, duality, and multifacetedness. While tracing back to the big bang of web technologies, content management systems (CMS) began their starting point from hard coding to comprehensive usability and intuitive operations
Subscribe for updates. We are constantly adding new Task Management Software.


Title for our form
A short explanation for our form
Enter your name
Enter email
Enter number
One
Two
Three
Four
Five
Six
Additional comments


Dead Code Elimination Variants¶
-dce (Dead Code Elimination)¶
Most aggressive dead code elimination algorithm. This searches for dead instructions, then rechecks after eliminations have occurred. This allows removal of functions such as
void A() {
B();
}
void B() {
return;
}
int main() {
return 0;
}
Not only function A, but then function B in the same pass (whereas -die would only be able to detect function A)
-deadargelim (Dead Argument Elimination)¶
Removes arguments which are obviously unused. Does further removal of arguments which are simply forwarded to other unused arguments.
-deadtypeelim (Dead Type Elimination)¶
(IN PROGRESS)
-die (Dead Instruction Elimination)¶
Obvious removal of dead code. See -dce above.
-dse (Dead Store Elimination)¶
(IN PROGRESS)


new ChartStyles(configuration)
Constructs a new ChartStyles object
Parameters:
| Name | Type | Description |
|---|---|---|
configuration |
ChartConfiguration | The ChartConfiguration object that is being used to configure the Chart |
Members
-
<static> formatters :Object
-
A collection of formatters used to format data before it is displayed
Type:
- Object
-
filters :Object
-
An array of functions that return useful filter functions, to help with conditional styling
Type:
- Object
Methods
-
<static> getDefaultStylesForPlot(plot)
-
Get a fresh copy of default styles for the plot. Styles will be returned if the plot is of type Plottable.Plots.Scatter, Plottable.Plots.Line, or Plottable.Plots.ClusteredBar
Parameters:
Name Type Description plot
Plottable.Plots.XYPlot The plot that the styles will be used for. Different styles are returned depending on the type of the plot.
Returns:
- Type
- Object
-
addToSelection(selection)
-
Add styling information to the D3 selection passed in This includes that gradient used behind the unit label in the y axis
Parameters:
Name Type Description selection
d3.Selection The d3 selection that the styles should be added to.
-
applyFilters(filters, d)
-
Check if the datum meets the conditions of all filters in the array
Parameters:
Name Type Description filters
Array The array of filters to check against.
d
Object The datum to check against the filters
Returns:
- Returns true only if the datum matches all filters in the array
- Type
- boolean
-
assignAttributesToPlot(styles, plot)
-
Associate the styles with the data points that match their filters using the plot's Plottable.js accessors
Parameters:
Name Type Description styles
Array The styles to associate to the plot
plot
Plottable.Plots.XYPlot The plot
-
getAttributeValueAccessor(attributeStyles, defaultAccessor)
-
Returns an attribute accessor function based on the attribute styles passed in. If none of the filters in the styles match, the default accessor is used.
Parameters:
Name Type Description attributeStyles
Array An array of styles with filters to check data against
defaultAccessor
function The Accessor to use if a datum is not matched by the filters on which the styles are conditioned
Returns:
- The function that will be used to access an attribute value contained in the styles parameter
- Type
- function
-
getConfiguredDefaultStylesForPlot(plot)
-
Get the combined default and configured styles for a given plot. Configured styles take priority over defaults
Parameters:
Name Type Description plot
Plottable.Plots.XYPlot The plot for which styles will be returned
Returns:
- The combined styles
- Type
- Array
-
getConfiguredStylesForPlot(plot)
-
Get the style specified in the configuration passed in at construction Filters that match the measures containing each style are added to the returned styles
Parameters:
Name Type Description plot
Plottable.Plots.XYPlot The plot that the styles are for
Returns:
- The styles in the configuration that apply to the type of plot passed in
- Type
- Array
-
getFilteredProperty(d, propertyName, propertiesWithFilters)
-
Get the value of the property by checking the point against the filters Returns null if there is no match.
Parameters:
Name Type Description d
Object The datum to check against the filters
propertyName
String The name of the property to look for
propertiesWithFilters
Array An array of objects, each containing a 'filters' key and a key with the name specified by the propertyName parameter
Returns:
- The value found at the propertyName if the datum matches the filters associated with that property name, or null
- Type
- *
-
getStylesForPlot(plot)
-
Returns the styles that have been set for the particular plot instance passed in If the returned styles are subsequently edited, they must be passed to setStylesForPlot() to affect the chart
Parameters:
Name Type Description plot
Plottable.Plots.XYPlot Get the styles associated with this plot instance
Returns:
- The styles for the plot specified in the plot parameter
- Type
- Array
-
getStylesKeyedByAttributeName(styles)
-
Re-index the style info by the attribute to assess attribute priority more easily
Parameters:
Name Type Description styles
Array The styles to re-organize
Returns:
- The styles re-organized as an object with keys for each attribute represented in the styles parameter
- Type
- Object
-
resolveAttributeValue(attributeStyles, d)
-
Resolves the attribute based on filters
Parameters:
Name Type Description attributeStyles
Array An array of style information. Each entry looks something like { filters:[], value:{any} }
d
Object The datum to check against the filters associated with each value
Returns:
- Type
- *
-
resolveStyleNameForDatumInPlot(d, plot)
-
Get the name of the style that a datum is rendered with, based on its filters
Parameters:
Name Type Description d
The datum
plot
The plot with the styles used for rendering
Returns:
- Type
- *
-
setStylesForPlot(styles, plot)
-
Set the styles that should be used for the plot instance
Parameters:
Name Type Description styles
Array The styles to use for the plot
plot
Plottable.Plots.XYPlot The plot that should get the styles
Example
// an array of style information that can be passed in as the style parameter [ { name: 'red-area', filters: [ chartStyles.filters.above(120) ], attributes: { fill: 'red', stroke: 'red' } }, { name: 'orange-area', filters: [ chartStyles.filters.above(100), chartStyles.filters.below(120) ], attributes: { fill: 'orange', stroke: 'orange' } } ]


Concurrent appenders
Mostly compatible replacement appenders for the existing Log4J appenders
which have a potential for deadlock when used in certain ways. The locking design allows
for multiple threads to execute {@link org.apache.log4j.Appender#doAppend()}
simultaneously.
Locking is done using a {@link org.apache.log4j.concurrent.ReadWriteLock} interface
instead of synchronized
blocks.
The {@link org.apache.log4j.concurrent.ConcurrentAppender} derived appenders are almost identical in code to ones found in the parent package, except in places where locking is used.
Users wishing to create their own concurrent appender should follow the source for {@link org.apache.log4j.concurrent.WriterAppender}, which demonstrates how to properly guard critical sections.


echoframework
/
org.echo.mobile.framework.model.operations
/
OperationType
/
ACCOUNT_ADDRESS_CREATE_OPERATION
ACCOUNT_ADDRESS_CREATE_OPERATION
ACCOUNT_ADDRESS_CREATE_OPERATION


%inherit file="base.html"/>
## Current tab for navigation
<%!
tab = "tos"
%>
## SEO Stuff
<%block name="title">Ultros | Terms of Service%block>
<%block name="description">What we collect and what we expect of you%block>
<%block name="og_title">Ultros | Terms of Service%block>
<%block name="og_description">What we collect and what we expect of you%block>


link to Passwords and Hashes > Password Dumping > Windows > DC Replication > Remotely Using Samba-Tools > Hashes After Join DC >
samba-pwdump.py


Hey there. I am Jimmy.
A software developer interested in security, 3D graphics, IoT, and programming languages


- UAction - Class in ure.actors.actions
-
UAction subclasses implement actions which Actors can perform to do arbitrary things in the
game world which take up game time, may be prevented by other Actors or the world, cause events,
and so on.
- UAction() - Constructor for class ure.actors.actions.UAction
-
- UAction(UActor) - Constructor for class ure.actors.actions.UAction
-
Override the constructor to set all parameters of your action when created.
- UActionDrop - Class in ure.actors.actions
-
Actor drops thing from her inventory, into her cell or a container.
- UActionDrop(UActor, UThing) - Constructor for class ure.actors.actions.UActionDrop
-
- UActionDrop(UActor, UThing, UContainer) - Constructor for class ure.actors.actions.UActionDrop
-
- UActionEmote - Class in ure.actors.actions
-
Actor makes an emotive text noise.
- UActionEmote(UActor, String) - Constructor for class ure.actors.actions.UActionEmote
-
- UActionGet - Class in ure.actors.actions
-
Actor tries to pick up the thing, from the ground or a container.
- UActionGet(UActor) - Constructor for class ure.actors.actions.UActionGet
-
- UActionGet(UActor, UThing) - Constructor for class ure.actors.actions.UActionGet
-
- UActionInteract - Class in ure.actors.actions
-
Actor interacts with an interactable terrain, thing, or actor.
- UActionInteract(UActor, Interactable) - Constructor for class ure.actors.actions.UActionInteract
-
- UActionPass - Class in ure.actors.actions
-
Actor does nothing for one action-time unit.
- UActionPass(UActor) - Constructor for class ure.actors.actions.UActionPass
-
- UActionWalk - Class in ure.actors.actions
-
Actor tries to walk to a new cell from their current cell.
- UActionWalk(UActor, int, int) - Constructor for class ure.actors.actions.UActionWalk
-
- UActor - Class in ure.actors
-
UActor represents a UThing which can perform actions.
- UActor() - Constructor for class ure.actors.UActor
-
- UActorCzar - Class in ure.actors
-
- UActorCzar() - Constructor for class ure.actors.UActorCzar
-
- UAnimator - Interface in ure
-
- UArea - Class in ure.areas
-
UArea implements a self-contained 2D map of roguelike playfield cells.
- UArea(int, int, UTerrainCzar, String) - Constructor for class ure.areas.UArea
-
- UArea(String, UTerrainCzar) - Constructor for class ure.areas.UArea
-
- UArea.Listener - Interface in ure.areas
-
- UBehavior - Class in ure.actors.behaviors
-
UBehavior implements a source of actions for an NPC actor to perform, to emulate a behavior or achieve
a goal.
- UBehavior() - Constructor for class ure.actors.behaviors.UBehavior
-
- UBehaviorWander - Class in ure.actors.behaviors
-
Wander aimlessly.
- UBehaviorWander() - Constructor for class ure.actors.behaviors.UBehaviorWander
-
- UCamera - Class in ure.ui
-
A view pane into a UREArea
- UCamera(URenderer, int, int, int, int) - Constructor for class ure.ui.UCamera
-
- UCartographer - Class in ure.areas
-
UCartographer implements a central authority for determining where inter-area exits go.
- UCartographer() - Constructor for class ure.areas.UCartographer
-
- UCell - Class in ure.areas
-
UCell represents a single XY cell of an area.
- UCell(UArea, int, int, UTerrain) - Constructor for class ure.areas.UCell
-
- UCollection - Class in ure.things
-
An inventory of things in a location (either a cell, or another thing or actor).
- UCollection(UContainer) - Constructor for class ure.things.UCollection
-
- UColor - Class in ure.math
-
UColor implements a mutable RGBA color with color and light mixing.
- UColor(float, float, float) - Constructor for class ure.math.UColor
-
- UColor(int, int, int) - Constructor for class ure.math.UColor
-
- UColor(UColor) - Constructor for class ure.math.UColor
-
- UCommand - Class in ure.commands
-
UCommand represents a player-initiated command, which may or may not cause a game action or a UI popup.
- UCommand() - Constructor for class ure.commands.UCommand
-
Your subclass should super() down to this constructor if you override.
- UCommander - Class in ure
-
Receive input and dispatch game commands or UI controls.
- UCommander() - Constructor for class ure.UCommander
-
- UCommandMove - Class in ure.commands
-
- UCommandMove(int, int, boolean) - Constructor for class ure.commands.UCommandMove
-
- UContainer - Interface in ure.things
-
- ULandscaper - Class in ure.areas
-
ULandscaper is a grab bag of tools for creating and populating UAreas.
- ULandscaper(UTerrainCzar, UThingCzar) - Constructor for class ure.areas.ULandscaper
-
- ULight - Class in ure.ui
-
ULight represents a light source placed in an area cell.
- ULight(int[], int, int) - Constructor for class ure.ui.ULight
-
- ULight(UColor, int, int) - Constructor for class ure.ui.ULight
-
- ULightcell - Class in ure.ui
-
ULightcell represents a single xy grid cell of a Camera.
- ULightcell(UCamera) - Constructor for class ure.ui.ULightcell
-
- UModal - Class in ure.ui.modals
-
UModal intercepts player commands and (probably) draws UI in response, and returns a value to
a callback when it wants to (i.e.
- UModal(HearModal, String) - Constructor for class ure.ui.modals.UModal
-
- UModalDirection - Class in ure.ui.modals
-
- UModalDirection(String, boolean, HearModalDirection, String) - Constructor for class ure.ui.modals.UModalDirection
-
- UNPC - Class in ure.actors
-
UNPC implements a non-player Actor with behaviors which initiate actions.
- UNPC() - Constructor for class ure.actors.UNPC
-
- unregisterActor(UActor) - Method in class ure.UCommander
-
- unregisterTimeListener(UTimeListener) - Method in class ure.UCommander
-
- UParticle - Class in ure.ui
-
- UParticle(UArea, int, int, int) - Constructor for class ure.ui.UParticle
-
- UPath - Class in ure.math
-
UPath implements A* pathfinding.
- UPath() - Constructor for class ure.math.UPath
-
- UPlayer - Class in ure.actors
-
UPlayer implements a UActor whose actions are initiated by user input.
- UPlayer(String, char, UColor, boolean, UColor, int, int) - Constructor for class ure.actors.UPlayer
-
- ure - package ure
-
URE is the UnRoguelike Engine, a game engine for creating roguelike games.
- ure.actors.actions - package ure.actors.actions
-
Actions represent actions creatures can perform to affect the world, and are passed around as events
to represent the occurence of those actions.
- ure.actors - package ure.actors
-
Actors are Things which can perform actions, move around, and affect the world directly.
- ure.areas - package ure.areas
-
Areas are self contained contiguous 2D grids of Cells, representing a game playfield.
- ure.actors.behaviors - package ure.actors.behaviors
-
Behaviors are members of NPCs which emit streams of Actions.
- ure.commands - package ure.commands
-
Commands represent a single player-initiated unambiguous command with no parameters.
- ure.sys.dagger - package ure.sys.dagger
-
Dagger is a library which provides dependency injection.
- ure.examplegame - package ure.examplegame
-
ExampleGame is a simple nonsense roguelike which exists to illustrate the features of URE.
- ure.math - package ure.math
-
Math packages implement data structures and algorithms useful for roguelikes.
- ure.render - package ure.render
-
URenderer is an interface representing the ability to draw a Camera (and other UI objects) in a
consistent visual style.
- ure.terrain - package ure.terrain
-
Terrain represents an instance of a terrain type in a Cell of an Area.
- ure.things - package ure.things
-
Thing represents a movable physical entity in the world.
- ure.ui - package ure.ui
-
- ure.ui.modals - package ure.ui.modals
-
- URenderer - Interface in ure.render
-
- URenderer.KeyListener - Interface in ure.render
-
- URendererOGL - Class in ure.render
-
- URendererOGL() - Constructor for class ure.render.URendererOGL
-
- UREStatusPanel - Class in ure.ui
-
- UREStatusPanel(int, int, int, int, int, int, UColor, UColor, UColor) - Constructor for class ure.ui.UREStatusPanel
-
- UScrollPanel - Class in ure.ui
-
- UScrollPanel(int, int, int, int, int, int, UColor, UColor, UColor) - Constructor for class ure.ui.UScrollPanel
-
- useTerrain(UTerrain) - Method in class ure.areas.UCell
-
Take a terrain object and make it our terrain.
- USimplexNoise - Class in ure.math
-
USimplexNoise implements a simplex noise generator, similar to Perlin noise.
- USimplexNoise() - Constructor for class ure.math.USimplexNoise
-
- USimplexNoise(long) - Constructor for class ure.math.USimplexNoise
-
- USimplexNoise(short[]) - Constructor for class ure.math.USimplexNoise
-
- USpeaker - Class in ure.ui
-
A singleton to play background music and sound effects
- USpeaker() - Constructor for class ure.ui.USpeaker
-
- UTerrain - Interface in ure.terrain
-
UTerrain defines all the public methods of terrain.
- UTerrainCzar - Class in ure.terrain
-
Load and manage all the terrain types and dole them out as needed.
- UTerrainCzar() - Constructor for class ure.terrain.UTerrainCzar
-
- UTerrainCzar(Class<TerrainDeco>) - Constructor for class ure.terrain.UTerrainCzar
-
- UTerrainCzar(String, Class<TerrainDeco>) - Constructor for class ure.terrain.UTerrainCzar
-
When creating your TerrainCzar, pass in your TerrainDeco class if you have one to extend
functionality of all Terrain.
- UThing - Interface in ure.things
-
- UThingCzar - Class in ure.things
-
- UThingCzar() - Constructor for class ure.things.UThingCzar
-
- UTimeListener - Interface in ure
-


INSTRUCTIONS: Delete old plugin version and install new from
ZIP file to update plugin.
Plugins folder: /wp-content/plugins/
*.* - mean ALL files with ANY types inside specified directory
*.php - mean ALL files with .php type inside specified directory


'Amazing' - high-profile support for Nottingham Forest's City Ground plans
Excitement is building as the Reds prepare to unleash their bright new vision for the City Ground
by Barry CooperProposals to redevelopment Nottingham Forest’s City Ground are ‘amazing’ according to one of the Reds’ most high profile fans.
England cricketer Stuart Broad, currently out in New Zealand preparing for the first Test match in Mount Maunganui, believes the grand plans to build a new Peter Taylor Stand as part of a wider regeneration project are worthy of the Premier League – a level the Reds haven’t starred at in two-decades.
Forest’s City Ground stadium was last redeveloped in 1994 when the new Trent End was built in time for the Reds to host games at Euro 96.
“Looks amazing, would suit the Premier League,” Forest supporter Broad wrote on Twitter, taking time out from his preparations for Day One at the Bay Oval.
View gallery
The £100m project will see capacity increased from around 30,000 to 38,000 once the whole project has been completed, with improvements being made to other stands around the City Ground which will see a new club shop, museum, corporate and media facilities included.
It’s hoped that work will begin early next year with seats available in the new Peter Taylor Stand by the end of 2020, and the club are keen on fans having their say on the grand plans.


Your Contacts{{resource.name}}{{resource.phone}}{{resource.body}}
There was a problem loading the data. Possibly the server is down or perhaps there are network
issues.
Please wait a bit and try again or start the server.
Contact NumbersIn times of need you can refer to these phone numbers
to have support. It's always okay to have someone to talk to


Values
November, 2nd of 2014 by Jorge Rubio C.
On this week's blog post I will share with you certain values that have been important for me throughout my life. One way or another this values represent my biggest struggles but also my greatest accomplishments
Adventure, Challenge, Growth, Openness and Persistence.
I put them together because they represent, in one way or another, the challenge of getting out of my comfort zone. To push myself out there and do something that is, new and hard for me to do. Most of the time, this leads to a growth experience that takes persistence but that also has ended in some of the happiest and most satisfactory moments of my life.
Using this scale, do I try to live up to this values?
Disagree 1 ----- 2 ----- 3 ----- 4 ----- 5 Agree
Adventure 3.
Challenge 3.
Growth 3.
Openness 3.
Persistence 3.
As I said, this is a struggle for me. I go through this cycle over and over again. I always find a comfort zone and I always push myself out from it to find something new, something that challenges me to be what I haven't been able to be before, to be a better person, to be a happier person.
What was the last topic that someone asked for your advice on?
People don't use to ask me for advice directly, normally I have conversations with people and they seem to feel comfortable enough to tell me about their problems. I listen and bounce ideas to them and try to get them to see other possibilities and points of view. I would say that a regular subject is human relationships in general.
Values and Stereotype threat
I think that, whether you recognize that you are feeling stereotype threat or not, your values are a good place to set a stance and face whatever you have in front.
Something that always helps me when I'm feeling down is to interact with people, to try to get out of my problems and see that there is so much more in this life that one particular situation or problem.


{% trans %}Hello! Welcome to the world of Nekoyume. Please set your own private key and input that in the form below so that you can start game right know. Private key is a password that identify you. Please make this unique.{% endtrans %}
{% if request.args.get('error') == 'invalid-private-key' %}{% trans %}Please enter a valid private key of 64 hexadecimal digits (it can be optionally prefixed with 0x).{% endtrans %}
{% endif %}


Privacy Policy
Effective May 15th 20181. We want you to understand how and why Utopian Company SRLs, registered in Italy, with head office in Via A. Manzoni 50, Rieti (RI), 02100, VAT #: IT01174530574 (“Utopian,” “we” or “us”) collects, uses, and shares information about you when you access and use Utopians’s websites, mobile apps, widgets, and other online products and services (collectively, the "Services") or when you otherwise interact with us.
Information You Provide to Us
2. We collect information you provide directly to us when you use our Services. Depending on which Service you use, we may collect different information about you.
This includes:
Information Regarding Your Use of the Services
3. We collect the content and other information you provide when you use our Services. This includes information used to create your account (e.g., a username, an email address, phone number), account preferences, and the content of information you post to the Services (e.g., text, photos, videos, links).
Transactional Information
4. If you purchase products or services from us (e.g., Steem Power), we will collect certain information from you, including your name, address, email address, and information about the product or service you are purchasing. Payments are processed by third-party payment processors (e.g., Stripe and PayPal), so please refer to the applicable processor’s terms and privacy policy for more information about how payment information is processed and stored.
Other Information
5. You may choose to provide other information directly to us. For example, we may collect information when you fill out a form, participate in contests, sweepstakes or promotions, apply for a job, communicate with us via third-party sites and services, request customer support or otherwise communicate with us.
Information We Collect Automatically
6. When you access or use our Services, we may also automatically collect information about you. This includes:
Log and Usage Data
7. We may log information when you access and use the Services. This may include your IP address, user-agent string, browser type, operating system, referral URLs, device information (e.g., device IDs), pages visited, links clicked, user interactions (e.g., voting data), the requested URL, hardware settings, and search terms.
Information Collected from Cookies
8. We may receive information from cookies, which are pieces of data your browser stores and sends back to us when making requests. We use this information to improve your experience, understand user activity, and improve the quality of our Services. For example, we store and retrieve information about your preferred language and other settings. On how you can disable cookies, please see “Your Choices” below. For more information about cookies read our cookie policy section https://utopian.io/cookies
Location Information
9. With your consent, we may collect information about the specific location of your mobile device (for example, by using GPS or Bluetooth). You can revoke this consent at any time by changing the preferences on your device, but doing so may affect your ability to use all of the features and functionality of our Services.
Social Sharing
10. We may offer social sharing features or other integrated tools that let you share content or actions you take on our Services with other media. Your use of these features enables the sharing of certain information with your friends or the public, depending on the settings you establish with the third party that provides the social sharing feature. For more information about the purpose and scope of data collection and processing in connection with social sharing features, please visit the privacy policies of the third parties that provide these social sharing features (e.g., Tumblr, Facebook, Reddit, Pinterest, and Twitter).
How We Use Information About You
11. We use information about you to:
-
Provide, maintain, and improve the Services;
-
Help protect the safety of Utopian and our users, which includes blocking suspected spammers, addressing abuse, and enforcing the Utopian user agreement and the Terms of Service;
-
Send you technical notices, updates, security alerts, invoices and other support and administrative messages;
-
Provide customer service;
-
Communicate with you about products, services, offers, promotions, and events, and provide other news and information we think will be of interest to you (for information about how to opt out of these communications, see “Your Choices” below);
-
Monitor and analyze trends, usage, and activities in connection with our Services;
-
Personalize the Services and provide advertisements, content and features that match user profiles or interests.
How We Share Information
12. When you use the Services, certain information may be shared with other users and the public. For example:
-
When you submit a post or comment to the Services, visitors to and users of our Services will be able to see the content of your posts and comments, the username associated with your posts or comments, and the date and time you originally submitted the post or comment. Although some parts of the Services may be private or quarantined, they may become public and you should take that into consideration before posting to the Services.
-
When other users view your profile, they will be able to see information about your activities on the Services, such as your username, prior posts and comments, Steem Power, and how long you have been a member of the Services.
13. Please note that, even when you delete your account, the posts, comments and messages you submit through the Services may still be viewable or available on our servers. For more information, see “Your Choices” below.
14. We will not share, sell, or give away any of our users’ personal information to third parties, unless one of the following circumstances applies:
-
Except as it relates to advertisers and our ad partners, we may share information with vendors, consultants, and other service providers who need access to such information to carry out work for us;
-
If you participate in contests, sweepstakes, promotions, special offers, or other events or activities in connection with our Services, we may share information with entities that partner with us to provide these offerings;
-
We may share information (and will attempt to provide you with prior notice, to the extent legally permissible) in response to a request for information if we believe disclosure is in accordance with, or required by, any applicable law, regulation, legal process or governmental request;
-
We may share information in response to an emergency if we believe it's necessary to prevent imminent and serious bodily harm to a person;
-
We may share information if we believe your actions are inconsistent with our user agreements, or other Utopian policies, or to protect the rights, property, and safety of ourselves and others;
-
We may share information between and among Utopian, and its current and future parents, affiliates, subsidiaries, and other companies under common control and ownership; and
-
We may share information with your consent or at your direction.
15. We may share aggregated or de-identified information, which cannot reasonably be used to identify you.
Ads and Analytics Partners
16. We may partner with third-party advertisers, ad networks, and analytics providers to deliver advertising and content targeted to your interests and to better understand your use of the Services. These third parties may collect information sent by your computer, browser, or mobile device in response to a request for content, such as unique identifiers, your IP address, or other information about your computer or device. For example:
Advertisers and Ad Networks
17. Our ad partners and network may use cookies and use related technologies to collect information when ads are delivered to you on our Services, but Utopian does not link to or provide your actual Utopian account details to these advertising partners. This means that Utopian does not share your individual account browsing habits with advertisers. Utopian cannot see advertisers’ cookies and advertisers will not see Utopian cookies.
Analytics Partners
18. We use analytics partners (such as Google Analytics) to help analyze usage and traffic for our Services. As an example, we may use analytics partners to analyze and measure, in the aggregate, the number of unique visitors to our Services.
19. For more information about how you may control the collection and/or use of information for advertising and analytics purposes, please see “Your Choices.”
Security
20. We take reasonable measures to help protect information about you from loss, theft, misuse and unauthorized access, disclosure, alteration, and destruction.
Children under 18
21. Although we welcome users from all walks of life, Utopian is not intended or directed at individuals under the age of 18. Therefore, individuals under the age of 18 may not create an account or otherwise access or use the Services.
Your Choices
22. As a Utopian user, you have choices about how to protect and limit the collection, use, and disclosure of, information about you. This includes:
Preferences
23. We may provide you with tools and preference settings that allow you to access, correct, delete, and modify information associated with your account.
Account Information
24. You may delete your account information at any time by logging into your account and following the steps under “Preferences.” When you delete your account, your profile is no longer visible to other users and disassociated from content you posted under that account. Please note, however, that the posts, comments, and messages you submitted prior to deleting your account will still be visible to others, unless you delete such content. We may also retain certain information about you as required by law or for legitimate business purposes after you delete your account. Any information that has been published to the Steem blockchain will also remain indefinitely.
Cookies
25. Most web browsers are set to accept cookies by default. If you prefer, you can usually choose to set your browser to remove or reject first- and third-party cookies. Please note that if you choose to remove or reject cookies, this could affect the availability and functionality of our Services. For more information about cookies read our cookie policy section https://utopian.io/cookies
Third-Party Advertising and Analytics
26. Some analytics providers may provide specific opt-out mechanisms (e.g. Google Analytics Opt-out), and we will provide, as needed, additional tools and third-party services that allow you to better understand cookies and how you can opt-out. You have the ability to opt out of having your web browsing information used for behavioral advertising purposes. For more information about behavioral advertising, or to opt out, please visit www.aboutads.info/choices.
Do Not Track
27. Do Not Track (“DNT”) is a privacy preference that you can set in most web browsers. We support DNT in our Services. There is no accepted standard on how to respond to web browsers’ DNT signals. When you have DNT enabled, we may still use information collected for analytics and measurement purposes or to otherwise provide our Services (e.g., Utopian.io buttons), but we will not load any third-party trackers. You may, however, opt out of having information about you collected and used for behavioral advertising purposes, as described above.
Promotional Communications
28. You may opt out of receiving promotional communications from us by following the instructions in those communications. If you opt out, we may still send you non-promotional communications, such as information about your account or your use of our Services.
Mobile Notifications
29. With your consent, we may send promotional and non-promotional push notifications or alerts to your mobile device. You can deactivate these messages at any time by changing the notification settings on your mobile device.
International Data Transfers
30. We are based in the Italy and the information we collect is governed by Italy law. By accessing or using the Services or otherwise providing information to us, you consent to the processing, transfer and storage of information in and to Italy and other countries, where you may not have the same rights as you do under local law.
Changes
31. We may change this Privacy Policy from time to time. If we do, we will let you know by revising the date at the top of the policy. If we make a change to this policy that, in our sole discretion, is material, we will provide you with additional notice (such as adding a statement to steemouncements, the front page of the Services or sending you a notification). We encourage you to review the Privacy Policy whenever you access or use our Services or otherwise interact with us to stay informed about our information practices and the ways you can help protect your privacy. If you continue to use our Services after Privacy Policy changes go into effect, you consent to the revised policy.
Contact Us
32. If you have any questions about this Privacy Policy, please email privacy@utopian.io


Requirements:
- JRE 7 or above
- mysql 5.1, 5.5, 5.6
- kafka 0.8.2 or greater
Unsupported configurations
- Mysql 5.7 is untested with Maxwell. GTID replication is known to not function.
- Maxwell is incompatible with PARTITION tables, as it is unable to parse the SQL.
binlog_row_image=MINIMAL
As of 0.16.2, Maxwell supports binlog_row_image=MINIMAL, but it may not be what you want. It will differ from normal Maxwell operation in that:
- INSERT statements will no longer output a column's default value
- UPDATE statements will be incomplete; Maxwell outputs as much of the row as given in the binlogs,
but
data
will only include what is needed to perform the update (generally, id columns and changed columns). Theold
section may or may not be included, depending on the nature of the update. - DELETE statements will be incomplete; generally they will only include the primary key.
Master recovery
Currently Maxwell is not very smart about master recovery or detecting a promoted slave; if it determines that the server_id has changed between runs, Maxwell will simply delete its old schema cache and binlog position and start again. We plan on improving master recovery in future releases.
If you know the starting position of your new master, you can start the new Maxwell process with the
--init_position
flag, which will ensure that no gap appears in a master failover.


You don't have administrator permissions to do what you just tried to do. Contact Administrator About This Head Back to the Tree