text:
Awww ain't he cute. You just want to snuggle up with him and never let go.
Mike ain't so bad either. In-between walking Darcey, Mike finds the time to run start up creative agency, Shape History.
He chats to Robert about why creating content that will change the world is important to him, how he crowd funded short film Credence, and his dedication to finding new ways to encourage others to reach their potential.
Listen and subscribe on Apple Podcasts or via the player below:


text:
There are many personal injury lawsuits today. Nonetheless, it is often difficult to determine whether or not you should move forward and file a claim. This article has many great tips for success.
Never forget to include any lost income or wages into your personal injury lawsuit. How much work have you missed? Is there a bonus you didn't get? If you were not able to attend your classes, you may be able to get a settlement to make up for that loss.
Personal injury is a field that is difficult to have a case in. This means that you should hire a lawyer that knows what they're doing. Look for someone who has won many trials in this field, ensuring that your case will be handled with the right tricks of the trade by him.
Do a thorough search online to find a great personal injury lawyer. This can help you make a heady decision during your search. Look for people who have practiced for several years and who have won a number of cases.
Talk face to face with your prospective lawyers before you hire one. Take advantage of free consultations to help you choose the right lawyer. Use the initial consultation to learn all about the attorney's fees.
Be sure to take lots of pictures and take notes at the scene of your injury. These will go far to support your case. You should have a family member or friend take the pictures if you're not able to do so. This should be done as quickly after the injury as possible for the most accurate photos.
Remember that any lawyer, no matter how qualified, works in your employ. You deserve to be treated with the utmost respect in any case, and your lawyer should make you the number-one priority. If a lawyer fails to treat you properly or pays you little attention, think about getting someone else. If you have trouble reaching your attorney, you might want to look for a new one.
If you have a personal injury lawsuit, you have to see your doctor at all appointments and keep excellent written records. If you are to get a settlement, you must prove that you have not only been injured but that you are being treated so you can recover. If you do not, it may look like you are lying or trying to manipulate the courts.
Find a lawyer with a lot of experience in the field that you need. This common sense advice is often overlooked. This is actually not the case, as law can be very complex. Otherwise, you'll handicap your case.
When you are injured, inform all of the necessary parties about your mishap. You need to tell your supervisor right away if you're hurt on the job. If there's an injury due to car accident, call an ambulance and the police as soon as you can.
These tips will help you prepare yourself before presenting your case in court. Apply the tips to your own situation to see if you can really bring a suit that will result in your victory. With this information in hand, you are able to get the ball rolling.

subset: commoncrawl


text:
Gulab the gardener gathers a big bunch of magnolias for his wife. But on the way home he gives one to the girl with ribbons, one to Tsering and her baby, one to the engine driver… The hill town of Shimla comes alive in the pahari miniature style.
The smart lion thinks he can use the fox to bring him food every day. But the fox is smarter! A familiar fable with an environmental angle. The energetic illustrations draw from Gond art.


text:
I would like to get a little personal with you. This is not something I like talking about normally. Not out of fear. Or regret (maybe partially regret). But this comes out of sheer embarrassment. I hit prime elementary school/ almost middle school in the mid 2000s. The coolest of the cool were doing something. Justin Timberlake for instance (along with the infamous denim suit). Blonde. Highlights. Yeah. I did it. I was hot stuff (I still am). Looking back, it isn't nearly as cool now. Just remember, blonde highlights stuck out in my bright hair.
"This little light of mine. I'm gonna let it shine." Given this song is "churchy" and has nothing to do with highlighting your hair. But all of us churched folk have probably heard this. Hid it under a bushel? NAH! Let it shine. Let it shine. Let it shine! In John 9:5 Jesus Himself says "As long as I am in the world, I am the light of the world." What does light do? It drives out darkness. In a dark room, a single candle can emit enough light to allow you to see. When you camp you light a match to start a fire, to stay warm and see (Light a Match, Start a Fire…get it?). Often we apply letting our light shine to ourselves, when in reality this should be something applied to an entire group…maybe like, the Church? I'll look to keep our trend of Church in motion. Check out Ephesians 5:8-10:
"For you were once darkness, but now you are light in the Lord. Walk as children of light — for the fruit of the light results in all goodness, righteousness, and truth — discerning what is pleasing to the Lord."
So as humans, sinful beings working to achieve our own glory, we in ourselves are in darkness. We have no truth of the Father in our hearts, and seek our own pleasure and "dreams". When we understand/accept/follow Christ (the light of the world) we find our path into light. We receive "goodness, righteousness, and truth" from becoming "the light of the Lord." We understand what it means to live like Christ. We take the role of Christ in flesh on earth, bringing light to a dark world (pastors say that a lot). So individually, our call to let our let shine is nothing to take lightly (not a pun, just a happy accident). But if you are light, and I am light, and every individual believer is a light, how bright the Church should be! If you're watching a football game, arena lights would make everything easier to see rather than a flashlight (more light makes everything brighter.)
Look at another verse, friends:
"and if you offer yourself to the hungry, and satisfy the afflicted one, then your light will shine in the darkness, and your night will be like noonday." Isaiah 58:10
What does it mean to be the light? What does it mean to be like Jesus, as a community (Church=community)? Isaiah 58 helps. Serve. Help. Love. When we feed the hungry, and comfort the afflicted one. Who are the hungry, afflicted, etc etc etc? The less fortunate. The oppressed. The hopeless. The homeless. The least of these (Matt 25:40.) Love these people. Fight for those who can't. Give to those who do not have. Strengthen the weak. Feed the hungry. Black Lives Matter. Blue Lives Matter. Childrens' lives matter. Elderly lives matter. We see people hurting. We see people thirsting for understanding and empathy. We see a hunger for equality. To say one cause is "unjustifiable" is complete negligence to people's needs. Like I've said before not every group or person is right all the times. Neither am I. But Jesus is. Light is Truth. Light is Compassion. When we walk in light, we drive out darkness. Our light will shine in darkness and night will be like noon. We are obligated to walk in light. If we "follow Jesus" we walk in light.
The Church must be light, even in a world where electricity seems rare.
Light drives out darkness. Love drives out hate.
Be like Jesus. Embrace your light. Eat some pie.
@samuel_owen05 Twitter/Insta


text:
Qualities to look for in a good freelance web designer / developer
Posted in Freelancing on Tuesday, 27th September 2011 at 1:11PM
I recently wrote an article entitled 'Agency vs Freelancer. Choosing the right person(s) for your new website' which compared the pros and cons of using either an agency or freelancer to build your new website. In this article I want to examine in greater depth some of the qualities to look for when hiring a freelance web designer. Finding a suitable freelancer can be a bit of a minefield so it really is worth taking careful consideration when trying to select the right person for the job.
The skills for the job
When using a solo freelancer it would unrealistic to expect them to be an expert in every area of the web development process but you should ensure they are competent (if not exceptional) at the core skills needed to get your website from initial proposal through to sign off and launch.
a) Wireframing and pre-design planning
Are they able to demonstrate good planning skills and an understanding of the benefits of wireframing and thorough project preparation? If they do not exhibit examples of wireframes and initial design sketches on their portfolio site, ask them to show you some examples from previous projects to confirm that they do take this stage seriously. Whilst there is often a temptation to dive head first into web design projects this can often result in crossed wires between developer and client in later stages when their vision of your site doesn't resemble yours.
b) Design skills
Your freelancer may be a coding genius but if their design skills are lacking the site will inevitably suffer as a result. Try visiting a site they have built recently. Do you find it easy and intuitive to navigate or do you find yourself getting frustrated and confused? Does the design feel as if it is has had the care and attention paid to the details that would make your site stand head and shoulders above the competition? Look for subtle gradients and fine borders - the sorts of artistic details that show they have really thought about not just the obvious design decisions but also those that may well go largely undetected or add to the site's visual quality in nuanced ways.
c) Front-end coding skills and W3C standards
It can be difficult to tell if a website has been well coded just by looking at it, especially if you don't know the tell tale signs. A badly coded website is likely to load slowly, it will be harder for people with disabilities to access using their assistive software and it will inevitably score badly from a search engine optimisation perspective (SEO). Whilst some symptoms of a badly coded site can be obvious such as page layouts that break in certain web browsers or web pages that take a long time to load, there are a couple of other ways to get a rough idea of whether the developer is following best practice.
Most competent web developers will try to code their sites in-line with W3C web standards. This is a set of standards put together by a body called the World Wide Web Consortium (WC3) to try and encourage well coded websites. They have an online validation tool which can check over a web page for errors at http://validator.w3.org/. The validator will tell you how many errors there are on a specific web page and provide details of the problems. Do not be alarmed to find a few errors on a page as it is often the case that in order to complete a certain task, validation just isn't possible, with no detrimental effect on the end result. Even sites such as google.com display numerous errors. However, I would start to question a developers coding practice if the errors are excessive (50+) and you shouldn't be afraid to ask a freelancer tendering for your project to explain why a site that they have coded couldn't be built to web standards.
c) Server side programming
For more advanced projects it is possible that you will need the skills of a server side developer who will be able to build a site that goes beyond a straight forward content managed site or e-commerce solution. Whilst there are several packages such as ExpressionEngine that allow a certain level of sophistication, if you intend to set up the next Facebook then you are going to need someone with server side development skills. In my experience most really good designers and front-end coders don't tend to be experts in server side languages and if they are, they are likely to be very expensive to employ. For a project of this scale you may wish to consider either turning to an agency or employing the skills of more than one freelancer and playing to their strengths.
If budget is an issue then it may be worth considering scaling back you initial plans and allowing a pre-built package such as ExpressionEngine or Wordpress to dictate some of the functionality and work flows. You may be surprised at just how flexible and powerful some of these packages can be and they are an awful lot cheaper than paying a developer for 6 months of their time. Most good web designers will be very familiar with at least one of these systems and should be able to customise them to within an acceptable distance of your original ideas.
SEO (search engine optimisation)
If your chosen freelancer promises that you will be top of Google within a week of your new site's launch then I would suggest they either know something the rest of the world doesn't or they are lying. If they are able to carry out parts a, b and c to an exceptionally high standard and you are able to provide excellent quality content for your new site then you are halfway there as search engines are basically just looking for sites that are well built and that offer relevant, high quality content to their users. So don't get too hung up on whether someone claims to be an 'SEO expert' but instead focus on their abilities to design and code properly then be prepared to put in some effort yourself to promote and maintain the quality of your website or blog.
How much should my new website cost?
How much you should expect to pay a freelancer for your next website is a hard question to answer seeing as the range of rates and skill-sets is so varied. A 2009 blog entry attempted to gage the prices freelancers charged for different types of sites by means of a survey. Out of the 220 submissions, the average price for a basic CMS site was £1310 but the difference between the lowest and highest costs was stark, ranging from £85 to over £9000! Some of this discrepancy could be attributed to geographical considerations and it was far from scientific, but the fact remains that you will be able to find a quote for £200 if you search long and hard enough so why would you ever want to pay any more?
I would suggest that a very cheap site is likely to be based around a template so you are not going to achieve a result that is carefully tailored to your exact needs. At these sorts of prices it is unlikely that a proper level of support could be provided and I should imagine that everything would be geared towards getting the job out the door as fast as humanly possible. Making sure that every detail is just right takes a lot of time and whilst it isn't possible to achieve this cheaply you can still find individuals that are willing to go the extra mile at a reasonable rate. I would recommend steering away from the cheapest quotations instead looking for ones that seem like good value based on the quality of their portfolio and the experiences of their existing clients.
Good communication skills.
In an agency the account handlers act as the middle man between the developer and the client which usually means emails and phone calls are answered quickly and by someone who is able to communicate clearly and concisely what it is the client requires from the developers and vice versa. Unfortunately, one reason a lot of freelancers go it alone is to get away from other people and they can see emails and phone calls as an uninvited interruption to their otherwise reclusive lifestyle.
When choosing your freelancer, make sure they reply to your initial emails quickly and that their replies extend further than just a brief comment intended to bat you away. A freelancer worth employing should show a genuine interest in both your business and your proposed project from the outset and be keen to explore exactly what it is he or she can bring to the table. It is also a good idea to have at least one phone conversation with them to make sure that they are someone you feel you could work with, you can tell a lot about someone's depth of knowledge from talking to them directly without giving them the chance to manicure a carefully worded email.
Using freelancers from certain geographical locations such as India or Eastern Europe can be one way to keep costs down as they can afford to charge less for their services thanks to lower living costs. Having used these services myself in the past I can testify that the service they provide can be very good, especially for straight PSD to HTML conversions and simple, budget brochure sites.
For more complicated sites you are probably better off sticking to someone who speaks your own language and who knows the audience that you hope to be catering for. It can also be harder to follow up any issues you might have if your freelancer lives half way around the world.
In my opinion, the best way to select a freelancer is through a recommendation from someone you trust, however if this isn't possible then there is nothing to stop you asking potential candidates for a reference from a previous client.
If a freelancer's previous clients are grateful for the exceptional levels of service and quality they received then they are likely to be happy to either email or speak to you directly in order to convey this. If possible, try selecting a client from their portfolio yourself to avoid them picking their only satisfied customer or their mum!


text:
AMEXICO is the common acronym for the Amtrak Executive Commando, a top-secret intelligence and special forces organisation working at the highest levels of the Amtrak Federation. It is directly answerable to the President-General and less than a dozen members even of the First Family know of its existence.
AMEXICO's operations sometimes call upon resources and assistance from Trail-Blazer and other military forces, in which case its operatives pose as combat-trained members of AMEX. However, rumours of a 'special' organisation with tremendous resources have spread throughout the Federation and beyond, with even renegades wary of new members who might be special operatives looking to wipe them out. Renegades refer to such agents as 'Feds'.
AMEXICO is commanded by a member of the First Family, currently Commander Ben Karlstrom Jefferson, who is closely allied to the P-G. AMEXICO heads enjoy almost unrestricted access to the P-G since their operations are usually run at the P-G's personal order. As a result, the post of AMEXICO commander is an extremely powerful and influential one, arguably outstripping that of the 'official' second-highest rank in the Federation, that of States-General of Texas.
AMEXICO is based at the White House but its operatives are trained at a facility called Rio Lobo, which is linked to the White House by its own private shuttle. AMEXICO operatives are picked for their supreme self-assurance and ability to operate alone for extended periods in the field. AMEXICO operatives are trained in unarmed and armed combat and the use of equipment usually far more sophisticated than that which is used by front-line troop, such as easily-hidden radios and surveillence packages.
Some AMEXICO agents serve within the Federation and First Family, ensuring that conspiracies agains the P-G are stopped in their tracks and ensuring the continuted loyalty of the populace to the First Family. However, their main field of operations is fieldwork, usually behind-the-lines in Ne-Issan (where AMEXICO agents pose as renegade or, with certain cosmetic alterations, Mute slaves serving the Iron Masters and gathering vital intelligence) or among renegade groups on the Great Plains, gathering information from the Mutes via bartering and trade. Attempts by AMEXICO to place agents within the Plainfolk clans themselves have proven unsuccessful so far, since Mutes are born into their clans and, until recently, never adopted outsiders into their ranks. However, following the Battle of the Trading Post when many clans were almost annihilated and others agreed to take in the survivors, a window has opened which AMEXICO could possibly exploit.
AMEXICO has its own air force for agent insertion and retrieval, surveillance and combat operations, informally called Air-Mexico. They colloquially refer to themselves as 'Mexicans'.
AMEXICO agents are identified by code-names such as 'Hang-Fire' or 'High Sierra'. They are not permitted to use their real names under any circumstances. AMEXICO agents can identify themselves to other agents by the use of a short-range radio ID transceiver implanted in the ear, or by whistling the tune South of the Border (with the first agent saying, "South of the border," and the second, "Down Mexico way," if he wishes to identify himself), which is taught to AMEXICO agents exclusively. AMEXICO agents are frequently following their own missions and are not required to help another agent if it means compromising their own, unrelated operations.


text:
10-man Latics defeat Whites.
Sky Bet Championship
Leeds United 1 (Bamford 17)
Wigan Athletic 2 (Massey 44, 62)
Leeds: Casilla, Ayling, Berardi, Jansson, Alioski, Phillips (Forshaw 45), Klich (Clarke 70), Roberts, Hernandez, Harrison, Bamford (Roofe 45). Subs: Peacock-Farrell, Dallas, Davis, Shackleton.
Wigan: Walton, Byrne, Robinson, Morsy, Massey (Powell 75), James (Garner 90), Naismith, Kipre, Dunkley, Clarke (Olsson 67), Evans. Subs: Evans, Gibson, Windass, Roberts.
Booked: Ayling, Berardi, Klich (Leeds), Walton, Evans, Powell (Wigan)
Sent off: Kipre (Wigan)
Referee: S. Duncan
Venue: Elland Road
Attendance: 34,758 (743 Wigan)
Two goals from Gavin Massey, saw 10-man Wigan Athletic defeat Leeds United 2-1 at Elland Road, denting the hopes of a Whites promotion.
Leeds had a great chance inside three minutes, Jack Harrison got to the byline and his cross just evaded the oncoming Patrick Bamford, it did fall to Pablo Hernandez though, who saw his strike superbly blocked by a combination of Cedric Kipre and goalkeeper Christian Walton.
Wigan went close through forward Leon Clarke, he headed just wide, following a decent cross from Antonee Robinson.
Leeds won a penalty in the 14th minute, when Kipre handled on the line to prevent Bamford from scoring. The Wigan defender was given a straight red card, but Pablo Hernandez saw his penalty hit the post, before Harrison saw a strike from the edge of the box go wide.
However, a minute after the penalty miss, Leeds took the lead. Bamford superbly controlled the ball with his chest, before firing across goal into the far corner with a fine finish.
Wigan had a great chance to level in the 23rd minute, a back-pass allowed Clarke in, he rounded Casilla who came out a long way, but his chipped effort was off target, with the Leeds defence racing back.
Pablo Hernandez then showed great skill, including a nutmeg to break into the Wigan box, but he saw his effort well blocked.
Pontus Jansson saw a header saved at a corner, before Bamford played Hernandez into the Wigan box, but nobody could get on the end of his cut back.
With four minutes of the first half remaining, Tyler Roberts went close from a corner, his shot was headed off the line by Wigan's Kal Naismith.
Wigan however levelled just before the break, Lee Evans played in Massey and he fired home.
Half time: Leeds United 1-1 Wigan Athletic
Marcelo Bielsa made two changes at the break, with Adam Forshaw and Kemar Roofe replacing Kalvin Phillips and Tyler Roberts.
Hernandez had the first opportunity of the second half, pulling an effort wide from the edge of the box.
Luke Ayling then saw a strike blocked, before Kemar Roofe was denied from close range after being found by Mateusz Klich.
Klich then struck a half volley from 20 yards, with his rising strike almost finding the top corner.
However, Wigan extended their lead in the 62nd minute, Nathan Byrne's cross was headed back across goal by Clarke for Massey to head home his second.
Hernandez then had two attempts, at goal, first he was denied by Walton, before striking over.
Reece James almost extended Wigan's lead in the 72nd minute, with his free-kick striking the crossbar.
Alioski then tried his luck from range forcing Walton to parry, before at the other end, James drove forward before striking wide.
Walton made a great save to deny Hernandez from the edge of the box, with the Whites throwing the kitchen sink at the Latics to no avail, as the visitors held on boosting their survival hopes and denting Leeds United's automatic promotion hopes.
Full time:


text:
Italian Tourist Raped In Mumbai, And We Are Still Claiming India Is Not An Unsafe Country!
Recently, a survey revealed that India was the world's most dangerous country for women. Of course, the government dismissed it, claiming that it was all opinion and didn't have any backing in data and was, therefore, probably incorrect. As we mentioned in this article, even if it is all opinion or conjecture, the image of India and the safety of women in the country is going to be questioned. It taints the country and while we may not see immediate repercussions, it's bound to affect tourism.
On the heels of declaring the report false, comes a news story that confirms everything we feared. An Italian tourist was raped by a taxi driver in Mumbai on the pretext of showing her around the city. The victim left the city, went to Bengaluru, then to Delhi and registered a complaint with the Italian embassy there.
ALSO READ: Well Done, India. We Are The Most Dangerous Country For Women
As news reports like these become a daily occurrence, is it surprising that we are actually considered an unsafe country?
Maybe it's time to take cognisance of the fact that women are unsafe and scared. That the women who come visiting are as unsafe and that this is going to all turn out quite badly in the long run. And no, brushing it under the carpet isn't serving any purpose.


text:
Saturday, April 27, 2019
Karl du Fresne: Is this the man we want to shape our human rights policies?Labels: Human Rights Commission, Karl du Fresne, Paul Hunt
4 comments:
The Appointment of Comrade Hunt.
The Labour/Green alliance has chosen the right person to pursue their ideology; install Hate Speech laws (applicable to Right Wingers justifiable) and further pave the way of a one party state. Lenin's objectives coming to fruition with the demise of part democracy!
This appointment is like placing a fox in a hen coop with instructions to "look after the inmates". True to his ideals this Commissioner considers thet "State is all supreme and knows what is best; for us". The introduction of hate speech will be an Orwellian disaster, and lead to the the introduction of a NZ brand of Communism?
This secrecy over his appointment is bad enough, with the general public unaware of Mr.Hunt's political legacy, his outspoken contempt for democracy; and now the chance supreme to dominate any right to dissent.
As Karl states the NZ First Party has ignored his appointment, and National the so called party of the rights of the individual; has sat so long on the proverbial fence it has almost disappeared. Since the last election it has been hard to discover what, if anything, the present National Party actually stands for? Or if indeed it is really an opposition party of the right!
Around the world in democratic societies concern is mounting on the way political parties are running our democracies. In France it is the Yellow jackets causing chaos; Brexit in Britain is almost a musical hall joke, with its leadership seemingly committed to sabotaging any Brexit exit; Italy and those indebted European nations to Germany have to watch their P's & Q's; that is before a Brexit outcome. While Germany is on the verge of an economic setback.
The far left have an open battlefield, and are they using it to advantage with Western Civilisation going through a process of self flagellation, and political correctness over "white supremacy".
We need leaders, not appeasers with cringing atonement indefensible policies. Our Judeo/Christian Western Civilisation is now facing annihilation, as it was after the fall of Rome in the 5th century.
To counteract this advance of neo Marxist barbarism, we need to ditch apologising for our past. Take the attack to the neo Marxists, their fellow travellers, and a left wing United Nations organisation choking daily on its own bias.
This and by backing President Trump, is our last chance of any democratic survival.
- April 30, 2019 at 10:07 AM
I heard this guy being interviewed by Kim Hill.
Do we want him in our system?
Definitely not.
- May 2, 2019 at 11:54 AM
- Bud Jones QSM said...
On Saturday Morning show 27/4RNZ, kim Hill was talking to Human Rights Comissioner.
Kim, you were talking about hate speech today
You've heard much talk about hate speech as we all have recently.
I've noticed the purest form of happily tolerated hate speech every time my TV remote accidently stumbles on to a broadcast as recently occurred in Wellington of the kappa Hate Ya Festival,Te Matatini.These shout and scream gesture feasts are obscenely bloated with hate and kill gestures. You know the routine, as ,sadly we all do.
Half naked young guys and gals suitably and savagely face/body painted for war,stage an ensemble formation [ skirmish line line in military science]. Pounding spears,waving hatchets,thrusting fists up, in the, up you, kill you gesture, Faces are fully grimaced in hate with tongues wagging in full on aggressive challenge disrespect mode. Worryingly young Participants believe they are a race apart different and separate from the rest of us.Superiority is implied, while shouting unintelligible language but clearly hate /kill chants at whom it is not clear.
My question for the Comissioner to explore is. What steps is government making to stamp out this hate festival of violent hate speech/actions fomenting a challenge to battle?
Noting the rapid response to gun law and the state censor moving a ban on the manifesto maybe also a book seller chain came under a Big Brother's heavy lean to remove books from sale.Also the promised warning of officials to investigate, hate speech wherever it might occur.
So, we have a unique Kiwi form of purest hate speech happily tolerated because it comes from a certain racial group, often, and certainly here, given a Free Pass to use hate speech and gestures of hate and threatening physical violence by young people who have been taught since they were babies that they are different and special/superior, and to manifest this hate of the other in an emotionally charged ritual festival. It is embarrassingly obvious why we tolerate this.PC goneblind populous phenomena.
Not to mention the blatant naked racism of all of it.
None of this has escaped our conscious notice,as it sadly permeates all of our awareness of life in NZ.
Best Regards,
Bud JonesQSM
51 Helston Road WellingtonPh 478 6641
- May 3, 2019 at 12:45 PM
Thank-you Karl for an excellent article. But a special THANKS to Bud Jones for an even better response. Apartheid is now so well entrenched in NZ society, with one rule for them & another for us. Imagine the response if the roles were reversed, with 'whites' dancing around pointing muskets, & shouting "come out & fight like men".
- May 3, 2019 at 4:18 PM


text:
Your shopping cart is empty!
0 reviews / Write a review
Benjamin Harrison was reproduced on Premium Heavy Stock Paper which captures all of the vivid colors and details of the original. The overall paper size is inches and the image size is inches. This print is ready for hanging or framing. Brand New and Rolled and ready for display or framing Print Title: Benjamin Harrison Paper Size: inches Product Type: Fine Art Print Artist: Unknown
Benjamin Harrison Poster Print by Unknown JJRFNK3M1
Write a review


text:
The hype around the word "big data" is ever increasing. It promises to bring a big revolution in marketing. But, in all this hype, myths also arise, which need to be cleared.
Joerg Niessing,INSEAD Affiliate Professor of Marketing, and James Walker, Partner Demand Analytics, Strategy&, in their article at knowledge.insead.edu, talk about eight commonly heard myths on big data. Some of them are:
- It's big
- The more granular the data, the better
- Big Data is good data
- Big Data is a magic 8-ball
These myths need to be discarded before putting into use "the real Big Data". To know more, please visit the following link:


text:
I developed ScoreVivo.com for my mom Ann Cameron Pearce, who plays both handbells and flute, but spends much of her time creating new arrangements of songs for flute.
Mom has written more than 70 arrangements for flute, many of which have received recognition from the National Flute Association, among others.
Most of her music was published in print via two notable sheet music publishers in her field. When one of them decided to cease operations, I approached her with the idea of becoming her own publisher by selling her sheet music as electronic downloads from the web.
The idea was compelling. She would benefit by retaining the copyright of her musical arrangements and a much larger profit while her customers and fans would benefit from lower costs and the ability to instantly download the sheet music they just purchased.
Ten arrangements for flute at time of launch
With this idea, ScoreVivo.com was born. On the day of launch, mom had eight arrangements for flute and one original composition for sale.
- "Florentiner March," an arrangement for flute
- "Grieg's Lyric Pieces," an arrangement for flute
- "How Brightly Shines the Morning Star," an arrangement for flute and handbells
- "How Far is it to Bethlehem?," an arrangement for flute
- "Popcorn Polka," an original composition for flute
- "Rustic Dance," an arrangement for flute
- "Tarantella from Song Without Words," an arrangement for flute
- "There's a Song in the Air, with Jesu, Joy of Man's Desiring," an arrangement for flute
- "Three-Part Invention #1," an arrangement for flute
Downloadable sheet music
Everything on ScoreVivo.com is sold as electronic sheet music in a .PDF format that customers may purchase, download, print, and begin playing in just minutes. We hope that our customers will welcome this new means of selling and distributing sheet music. We license our music so that a single purchase may be printed for all musicians in a group, meaning our customers may print as many copies of their purchase as they need for their musical group.
Publishing sheet music from other artists
When we created ScoreVivo.com, we designed it so that we could consider the option of selling electronic sheet music from other artists and instruments. We are also entertaining a much more favorable agreement for artists who might choose to sell their compositions via ScoreVivo.com.
- Artists will retain full copyright of their compositions and may switch publishers at any time without penalty
- Artists will earn approximately 2/3 from each sale
Because our costs are low (nothing to print, nothing to mail), ScoreVivo.com would be able to better reward the artists who choose to sell their sheet music via our website in an electronic downloadable format.
I'd like to know what you think of this idea. If you are an artist, would you find this arrangement appealing? If we do decide to sell music from other artists, what else could we do to make the process more attractive to either the artist or our customers?
Thanks for visiting ScoreVivo.com. We hope you like what we've created so far.


text:
[a/n: the title's a rather apt reference to slavery]
"You wanted the truth, Potter. Did you think it would be gleaming silver?" Snape asked, his voice cold.
"no... but!" Harry was almost half a step behind in the conversation, still thinking about Snape letting him stay there. He might be pointlessly cruel, he was often impatient to the point of rage... but something here wasn't adding up.
"There are reasons you haven't been told everything, even when it's your own tale, and you've the right to hear it. Truth is rarely pleasant, and never kind." Snape said. Harry nodded solemnly, if a bit absentmindedly.
"Then tell me the truth - you said you spoke up for me... what did you say?" Harry asked, more hoping to see something accidental in the older man's words than anything else.
"I wouldn't count it as much good done, even if it had worked - you realize? A good deed that costs you little is nearly worthless."
"I still want to hear it." Harry said stubbornly, his implacable green eyes belying the softness of his tone.**
"Very well - it was two years, nearly to the day, from when you had been delivered to the Dursley's doorstep. The fanatical Death Eaters had been captured and imprisoned-"
"Except for Lucius Malfoy" Harry Potter chimed in.
Snape looked down his nose briefly at Harry Potter, and then laughed, his rich baritone ringing in Harry's ears. "Lucius has never been, and never will be a fanatic. He is a power-hungry fool, whose only motivation is aggrandizement and lust for power."
Potter tilted his head, and said, "Sir, if the Light offered him enough money, enough status - he would switch sides?"
Snape said with a sharp-edged smile, "Most likely. And if we hatched a scheme that depended on Malfoy being on Dumbledore's side for a few days, it might be worth it." Potter waited rather than interrupting, "When someone's price is power, they are always on sale to the highest bidder. And the Dark Lord would bid highly to win Malfoy back - it would crush morale if he allowed one of the arch Pureblood Supremacists to leave him, to fight against him."
"What's Draco Malfoy's price, sir?" Potter asked, secretly glad that he managed to keep the twist of hate out of his voice.
Snape said sternly, if kindly enough - for a Snape, "That is adult knowledge you're asking for, child. You'll use it accordingly, or you'll suffer the consequences."
"I think I've had enough detentions for one lifetime, sir." Harry Potter said.
"That has yet to be determined," Snape said, his scowl completely masking the grin he felt - the idea of Potter managing a year without finding some way to need a detention was laughable. "But a man's trouble isn't limited to detentions. Draco Malfoy is the type of person who is unpredictable when pressed - and I needn't tell you how dangerous a Slytherin can be, if properly motivated."
Harry simply nodded, thinking about Draco Malfoy - a more spiteful and arrogant, vindicative boy he'd never known. Dudley wasn't nearly as bad (at least he knew he was fat).
"Draco's weakness, his price, if you will, is his family. More specifically his mother. Trouble her at your peril." Snape said gravely, before smirking, "In school, I have always thought it best that children train themselves - so long as the cubs keep their claws sheathed and the snakes remember not to poison everyone in sight. If you wind up calling him a mama's boy, that's perfectly appropriate. Hurting his parents is well outside the bounds of playful activity."
Harry Potter nodded, thinking wistfully about his father and mother - wishing that he had enough memories of them to care as much as Draco did about his parents.
**Harry doesn't realize how much he's learning from Snape.
[a/n: Snape bends the truth as easily as he breathes. That doesn't mean he particularly likes to do so.
Message to Hufflepuffs out there: If you didn't notice that Snape was (presumably) bending the truth with Dumbledore, learn to read a bit more thoroughly.
Perhaps more accurately, his lies (by omission, mind) were constraining how much of the truth he choose to reveal. Slytherins are subtle creatures.
Snape has a melancholic view towards life in general, influenced by his upbringing, no doubt. His thoughts towards utilitarianism do not reflect my own - though I do share a dislike of people that insist on prettifying everything. One can do wrong and have it turn right in the end, can tarnish a victory with innocent blood. It should not be glorified.]


text:
Rental Details
"The Palms" North Pointe is the site of this exceptional 3 bedroom, 3 bath home. It features dramatic soaring ceilings, lots of natural light. Black upgraded appliances with granite counter tops, includes kitchen island/breakfast bar, with dishwasher, stove, microwave and refrigerator. Off the kitchen is slider window door to the covered patio. Also off the kitchen is another family room, with additional room for office/den with a quest bathroom. Inside Laundry room with updated Amanda washer and dryer. Then we have a large 3 car garage, boat deep,40'. Upstairs 3 bedrooms, 1 guest full bathroom. Master bathroom has big walk-in closet, dual vanity, soaking tub, separate shower and privacy toilet. Large Master Bedroom. Also upstairs is another family den/office space/or TV room. Large hall closet. 2 A/C units, R/O system and water softener. Blocked wall surrounds this large yard. 2 car garage. Pet friendly with a fee. If ever there was a "must see" this is it. You can tell this is a friendly neighborhood where people obviously care about their homes. This is a gated community!
Pool: No Spa: No
Fenced: Yes
Pet Friendly: Yes w/fee
Garage Depth: 40'
Door Height: 8
Sq ft: 2,496
Age: 2006
Area: North


text:
So I was recently in a male friend's apartment and came to realize most guys have no idea how to transition from their decorating sense in college to the point where they'e decorating their own home in the burbs. But let's be honest; that latter decorating sense consists of them sitting on the couch on Sundays watching football while their wife shops for their new house's decor.
In life there's a point where guys live alone sans twin bed and mini fridge and most of them have no idea how to decorate for that humble abode. So its time to tear down the Dark Side of the Moon poster and put up some cool photography by the great Gray Malin.
Gray is a young…hot….photographer who studied at Emerson College (what what Boston!) and shoots under the title Maison Gray. But more importantly he's got a great eye for photographing every day images that will spice of your living quarters.
I really love his collection of "Nine Poloraids". Grey takes corresponding poloraids of the same image and frames them together for an interesting look. And even better than his art work is the price. I know I know…nothing beats $7.99 at your local Hot Topic but these beauties at $189 a pop make them investment pieces. Yeah that's right I said investment pieces. That's a phrase adults use. Adults who decorate. And who knows maybe some day your wife will hang your photographs in your "Man Den".
So check out a couple of his pieces. My favs are the Nine Poloraids of the Chicago Cloud Gate Sculpture
Or chchchchcheck out the Boston photograph.
They'd look perfect next to any Periodic Table of Mixology poster! Kidding. Take it down….now.


text:
Sam Suh, Kevin Wang, Nikhil Saraf and Anatoly Yakovenko (left to right) talk shop about Building Blockchain Infrastructure
On August 22nd, Solana CEO, Anatoly Yakovenko teamed up with Nervos Co-Founder, Kevin Wang, and LightYear's Principal Software Engineer, Nikhil Saraf to introduce their projects and talk about their key learnings from developing blockchain infrastructure.
Introduction to Solana
Solana is a high performance blockchain that uses a concept called Proof of History to achieve a cryptographically secure and trustless time source.
- Telegram: https://t.me/solanaio
- Solana Github: https://github.com/solana-labs
Introduction to Nervos
Nervos is a network of scalable and interoperable blockchains built on top of an open network, built for the enterprise.
- Nervos Github: https://github.com/NervosFoundation
Introduction to Lightyear (InterStellar)
Lightyear, powered by the Stellar network, enables forward thinking financial entities to join the Stellar ecosystem.
- Stellar Github: https://github.com/stellar
Technical Discussion Panel
(Transcript below)
Raw Transcript of Video:
Sam: All right. So I think it's going to be pretty casual, right, where we could open it up to Q&A first, if you guys want, because I know some people had questions about the individual things. We'll maybe do one or two questions there and then we'll go into more of a discussion, just in case there's a burning question. Does anyone have any questions for any of the three about their presentations? Yeah, go ahead.
Man: I have a lot of questions. Maybe a good [inaudible 00:00:40] data availability [inaudible 00:00:40].
Sam: That's actually one of the questions too. But like, before we answer the questions, could I just gauge the room? Who here is a technical or a developer? Okay. Who is the complete opposite and completely not technical? Okay. Cool. And then everyone else is somewhere in between. So I think you can answer in a kind of technical way, and we'll…
SF Meetup @Starfish Mission
Nikhil: So, again, so data availability. So I think the incentive to run a Horizon node is that you wanna make sure that when you need the data it's there. And typically, if you're one of the partners and you're pushing a lot of data through the network, you wanna make sure that your transactions are going through. You don't wanna depend on someone else's node because that's where the consensus comes into play, because your horizon node has its own trust model of who it trusts. So if you have to fall back on someone else's node, you're not really getting the guarantees that you would get if it was your own node. So then, it's kind of on you to run your own highly available node, as well as make sure it's always available.
Anatoly: For us, one gigabit will generate about four petabytes of data a year. So that's a lot of data. It's actually not that expensive. So 150k buys you a petabyte deployed. But it is a lot of data for individuals to store, kind of like… Our industry right now is built upon decentralization. And what that means is there's low barrier to entry for anyone to participate in the network. So this seemed like an opportunity to me. And because of our particular implementation, we have this decentralized source of time before consensus. We can actually have a very cheap to verify proof of replication. And that allows us to stripe this enormous data set amongst any number of nodes that wanna just simply contribute storage without, like even high availability but some kind of medium availability. So to me, this seems like… In my mind, if we're successful, imagine like anyone in the space is successful and 100 years from now there's a Blockchain that's around. This isn't a data set of all economic activity for the past 100 years. That is probably the most valuable thing we're building right now. So I'm really excited about that part.
Kevin: Just make sure I answer the right question. When you say data availability, what do you mean? It's like…
Man: So, a lot of consensus protocols assume that the data is available, but the data could just not be available.
Kevin: Like fisherman's dilemma, right? Fisherman's dilemma. You're talking about that?
Man: [inaudible 00:03:47].
Kevin: Yeah. Okay. So there are two parts to the question for [inaudible 00:03:54], right? So first is the consensus of the root chain, and then we use POW. So the POW consensus basically encourages data to, miners to make data available because you want to propagate your block as fast as possible so that other people can build on top of your blocks, right? If you withhold the data, then you're not gonna be the longest chain. So that's the sort of building mechanism on the consensus level to encourage data availability. So that's one. You can withhold the data, but then you're gonna fall behind, right? So you're not gonna be the longest chain. So that's in terms of consensus on the root chain.
In terms of, for us, like layer one, layer two interaction. So data availability comes down to, you know, what if the layer two operator, for example, withhold the data, and then how do you prove fault? Right? So that's, you know, that's not an easy question. I mean, there is Ethereum is for example, doing [inaudible 00:04:59] coding to be able to, you know, recover that data. But even then, I think a lot of time there is no way to prove fault. You can't challenge the operator, basically, right? They can always review the data and then, you know, prove that you're wrong. So basically, you can't win. So in that case, there are two solutions. One is to do something like a mass exit to the main chain, like what plasma does. And then the other approach is to have…if you have sort of…we talk about side chains, right? Not stick channels. But if you talk about side chain that are built, like in the same form, then we can probably do something smart that migrate data from one site into the other without having to all exiting to the main chain. So that's something we're also researching now. Yeah.
Anatoly: So just to be a little contrarian, in proof of work systems, the miners have no incentive to keep the data set. Actually, most of them throw it away. Like, so you can hash the blocks without actually storing any proof of work, because you don't care. All you care about is getting the block. So in Ethereum, it's actually starting to become a problem because the data set is growing quite a bit and Bitcoin is still pretty small.
Kevin: Yeah, I think what I'm talking about, it's when you do, like, win the lottery, right, like POW, then you want to propagate that block as fast as possible.
Anatoly: But you can throw away the rest of it, so you don't have to store the rest of the chain, right? Like, there is…
Kevin: Yeah, but…
Anatoly: …not aligned incentives there.
Kevin: I think you were talking about verifiers, right? So it's not the miner that find the block, but like the full nodes that receive the validation. Then, I mean, you can…
Anatoly: But if no one's storing the full chain, then is it a Blockchain?
Kevin: Well, I mean, that's what we're doing. That's where, you know, we have to give incentive for people to store it. Right? I mean, this is exactly like for knowledge-based platforms, we have direct token economics designed for encouraged for preserving knowledge, yeah.
Sam: Maybe, could you go a little bit deeper into the general token economic incentives?
Kevin: So, in Nervos, for example, you know, if you look at, you know, competition platform like Ethereum, the tokens are used to pay for computation cost, or unit of computation cost. So, for Nervos, the tokens are used to bond with the storage units and then to measure the space that you use to store data, right? So in other words, if you're a user of the network, and you want to store your data entities into that network in the public Blockchain, you have to pay by locking your tokens, right? And then you're…again, if you're a miner that you do store this data, then you can get this, you know, from block reward to be able to store this data.
And we want to battle the problem of, you know, people like Ethereum, people pay once for transactions and have their data stored forever in a very, very [inaudible 00:08:09], you know, like, it could be there for 100 of years, but it's all free, right? You pay a one-time cost. So what we're trying to do is to say, for the user side, you have to pay an ongoing cost. And that's incentive, that's encouraging people to actually not to keep occupying this Blockchain, right? So they can always release their token from the storage. And then, you know, to get liquidity of their token, they can resell it. So to protect the full nodes and cost of full nodes running.
Sam: Would you guys also mind just going very broadly into the token economic structure of your projects? And kind of how it relates to maybe, incentivizing behavior that you want to drive towards a certain result.
Nikhil: So in terms of the stellar network, I think, the Lumen is mostly used just to…as a resolve when you open up an account. So this prevents people from just opening up accounts and sort of slowing down the network. And it's also used as a fees to prevent people from spamming the network. So I think it's really just to promote good behavior on the network.
Anatoly: For us, it's really like an operating systems resource. If you ever, like, I don't know, wrote kernel code, your processes and user space, they want resources from the kernel. You have to build them so you allocate file descriptors and all this other stuff. But ultimately, all that is a resource that accounts for hardware. So when a user submits a transaction, they're asking for storage in the network. When they wanna do a computation, they're asking for CPU. And those are effectively competitively priced. So, market priced. And our job is to make the system have as much capacity as possible to reduce those costs. So this is, you know, in our sense, our goal is to drive the fees to be as low as possible by making the software as kind of as fast as possible.
Sam: Very cool. So I wanted to switch it up just a little bit and instead of talking about the specific projects, maybe go from the perspective of a developer that may want to use your, you know, protocol or your platform or your product. Kind of generally, what differentiates you guys and why would someone choose to use your product over competing products? Maybe we'll just go this way. Okay.
Kevin: You know, for Nervos… Okay, so there are two… The Nervos are layered architecture, right? So we have the base layer focused on…it's a common knowledge base, so we can afford to focus not on, you know, computation cost. We don't need to provide the lowest computations possible. And we want to provide security because that's…as a common knowledge base, that's what the users demand to be able to security, preserve the knowledge. So at the base layer, we prioritize security and decentralization, right? A censorship distance, those are all the values that a knowledge system will demand.
And then, the second layer is where really people build applications, and there will be different types of layer two solutions. You know, if it's a cooperative game, then it could be, you know, state channels. If it is more of a, you know, a fast payment network, it could be, you know, specific build for that purpose. If, you know, if built for a specific industry, like for gaming and, you know, maybe there is a more non-fungible tokens, if it is, you know, for financial industry, maybe that's more about [inaudible 00:11:56]. So there's [inaudible 00:11:58] as possible. So all of these layer two solutions can specialize. But they can rely on the base layer to produce the decentralization and security so they can focus on their domain, you know, the requirement of their domain.
Sam: Maybe you guys can also, in addition to, why would someone choose yours over a competitors, maybe go into some of the use cases also about what you can use it for.
Nikhil: So I think in terms of why someone would choose Stellar, I did cover a lot of that in the presentation, but I will cover some of the highlights. I think that it's relatively easy to use. So a lot of people don't really know this part about Stellar, that if you want to issue a token on the network, it's just a few lines of code. And issuing like, comparing this to Ethereum, if you want to issue a token on Ethereum, you're really writing a full smart contract. That's a lot of code you need to write. On Stellar, a token is kind of just like a distributed counter. So if you just want to track how many people are involved in your project, or how many people…how much value has been transferred over the network, Stellar is great for that because it's cheap as well as really easy to code. And you can't really have any bugs in that because it's mostly just data. I think in terms of getting started, so we do have this project called the Stellar Build Challenge that allows people to contribute to existing projects or start their own projects, and Stellar does fund these projects with Lumen grants to keep the project going, and a lot of people join the community through this path, and we've actually hired a few people out of this as well.
Anatoly: So, for us, I think the selling point is performance. In my view, we can actually build a platform that is competitive to like a professional deployment on a centralized system. And because it's a decentralized platform open to anyone, a developer can just jump on it and get all the benefits of very fast finalities. So right now our like Alpha is under sub-second, so around somewhere between 400 and 700 milliseconds for finality. That is close enough to be an interactive, like on-chain experience for humans such that they're not annoyed with how long things take. But for developers, I think we're maybe the most interesting, exciting part of the project. All of these technologies are coming together being integrated, and there's a lot of fun opportunities to learn about consensus and scaling and performance and how to really fine tune and optimize things. So in my mind, this is like the coolest time to jump in and see what you can do. So if you guys are interested in learning Rust or building a really, really fast Blockchain, jump on our GitHub.
Sam: Maybe following up on that, if someone really did want to just start using you guys like today, right, for all three of you, what is available and what is kind of the first steps? Like, how would I literally start using you, like using your protocols and products?
Anatoly: Download the Rust tool chain, clone up the GitHub and go. That's about it.
Nikhil: Yeah. So I think the best way to get started, I would say, is just go to stellar.org/laboratory, where you can actually just create a test account with two clicks. I think using that can follow the path of creating accounts, doing transactions and then maybe building apps and whatever your heart desires from there.
Kevin: Yeah, so for us, we're still building the Nervos CKB, so the base layer protocol. So that's not test net ready yet, so people can't really build on top of that. But we do have a layer two solution we call Nervos App Chain that is ready. So you're welcome to, again, go to GitHub and try that out. There is a, you know, EVM compatible site chain solution, there is a Blockchain Explorer, there's a wallet that you can play with it. Yeah.
Sam: Thanks. So let's shift back towards like the team building this project out. How exactly do you guys go and reach out to developers, besides things like this? Is there like a best practices in terms of ways to, you know, build a developer community, or just to like get people to look at your stuff? Because there's so much out there, right? And so, how do you get mindshare in the Blockchain space towards developers?
Nikhil: So, we try to keep an active channel of communication with…we used to have a snap channel, and now we're slowly shifting that over to key base. And this allows not just us to to talk to a community, but also other community members to talk to each other. And that's how, for example, people form teams for the Stellar Build Challenge, as well as that's how we push protocol changes through the community by having those connotations first in the chat channels and then potentially moving them to GitHub and to form the proposals.
Anatoly: For us, we've been open-source from day one, so really trying to engage developers kind of from the start. And this is the hardest problem in this space, I feel, because we're building an operating system that's hard enough. We're also building a social network around it, which it's also a super hard problem. And there is no secret sauce to building that. You just have to do the hard work of engaging people and getting them to try and really focus on solving a pain point that they have. And the pain point that we're really good at solving is performance. So anyone that has problem scaling on Ethereum or any other chain, we can actually help.
Sam: So, that brings up a question that a lot of maybe first-time developers or like entrepreneurs may face, is that they see the potential and there's so much to be done where you can solve a little bit of a problem, and then you run into another problem but you're like, "I could probably solve that one too." So maybe we'll just do both of those. And then you run into a third problem. You're like, "Well, I guess if we're going to do two, we might as well do three." And before you know it, you're claiming that you're gonna solve every problem under the sun at the same time, right? How do you kind of limit what your scope of your project is, and have you guys had any issues with that yourselves?
Kevin: Yeah. That's definitely a pain. I think for anybody coming from engineering background, right? So your tool to attack complicity is abstractions, right? So for us, I mean, we wanna build the natural abstractions for developers, which means, you know, for us, you know, we have a concern to separate and compartmentalize in layers so that each layer focused on one specific concern that we can optimize it. So, it doesn't have to mix together and then force to, you know, make hard trade-offs. So, yeah, abstractions.
Nikhil: I think the first step, I would say, is to be aware of that risk and try to not fall into that. So what we do is, we try to be very conscious about exactly what we want, say in the case of Stellar, what Stellar should be. And then we say no to a lot of things, because at the end of the day, it's pretty hard to get a lot of people and hopefully the whole world using something like Stellar. So if we make it more complicated than what it needs to be to get everyone to use it, then not that many people are gonna use it. So we try to just keep things simple and figure out would some farmer in Africa be willing to use this complicated solution? And if we think that they might not, then we try to stay away from that.
Anatoly: For us, we really focus on performance. And so far, where we had to make trade-offs, I think, is really going after, like something like zero knowledge proofs and building a totally different model that requires, I think, really, really huge performance sacrifices to make it work. It is like a really fun research topic and I would love to spend a couple years trying to figure out how to make that work fast. But so far, it doesn't seem possible. So when we do make choices in terms of what we're building, we pick performance first, and then the second thing, we're optimizing it for privacy. So that is kind of our clear design goals.
Sam: Cool. So, kind of going back to the developer side, what…and you guys have all kind of touched on this, but like what developer tools do you think are critical to knowing before jumping into, like, working with your projects? Like, what is the prerequisites that we should come with?
Kevin: Like, to build with our project? Okay.
Sam: Yeah. If I wanted to use your project, what should I already know? What must I know?
Kevin: You know, again, our platform, there will be multiple audiences, right? So there are people that are building layer two solutions. I think there are to then, you know, their own program languages and so on. They need to understand the interactive proof with working with the base layer protocol. So it's more about complete economics. And then we'll make that easy for people. That's, you know, what we want [inaudible 00:21:42]. And then you have people working, building on dAPPS, on top of layer two solutions. You know, this is where I think it's, you know, it's really about…it's not so much of building on top of Nervos CKB, but just knowing the specific platforms and their features, and, you know, what's their trade-off to picking the right platform.
Nikhil: So I think the biggest thing, I would say, is like, have a mindset of security. Like, if you're building a product, the security is kind of on you and it's up to you to decide how secure your users are gonna be. And I think that combined with knowing any of the languages that we currently support, I think JavaScript is the most popular SDK that we have. I think combined with those, you can pretty much build what you want. And I think having that mindset of security is what's gonna differentiate your app from any of the others.
Anatoly: For us, I would say the clear requirement is Rust. So it's a high performance language. So, I would say that's a pretty clear requirement right now, but we will enable more languages. Basically, anything that has a LVM front-end should be supportable. And our goal might be to be the first debugger for like Blockchain smart contracts. I'm surprised there isn't one yet.
Sam: Yeah. Well, why do you think that is?
Anatoly: It's just tooling is hard. Like, developer tools are hard. It's always the last thing on anyone's mind when they're trying to get stuff out. Me coming from like 12 years of building stuff in embedded systems where tooling was hard as well. I think debuggers are very important for developers to actually get stuff done.
Sam: That's an interesting point. I know all of you have really interesting backgrounds. I don't know how much time we have to go really deep into it, but maybe you guys could talk a little bit about your backgrounds and how they relate to your current project. I know you had some really interesting stuff on like decentralized exchanges, and I know you have some. So maybe take a moment and then talk about how your past relates to what you're doing now, and maybe also how people with really interesting backgrounds out in the audience, they can kind of find a place for themselves in the Blockchain world.
Kevin: In terms of interesting background, I feel like for most of us coming from engineering background, you know, this entire Bitcoin, the Blockchain, you know, innovation is really just the last several years. So, you know, for example, I was a…I worked as a software engineer at IBM Silicon Valley lab, down, you know, in San Jose. So I wasn't really doing a lot of, you know, Blockchain or, you know, cryptoeconomics research or cryptography research. I was doing more of a, you know, data management and big data solutions at the time. So I think it's more just general, like computer science education, and knowing about distributed systems, algorithm, data structure. So I wouldn't put a very high barrier for people who wanna come to this world and who want to become a Blockchain engineer and developer. If you're interested and you have some spare time to play with it, you're probably halfway there.
Sam: What about for non-developers?
Kevin: For non-developers, I mean, it depends on if they want to become developers. Yeah. I think a good place to start it's probably Ethereum smart contracts. So it's relatively easy, you know, easy to pick up a programming language, or they can start work with JavaScript which is kind of similar, right? And go from there and learn about the base principles of, you know, Blockchain systems and start trying to play with the smart contracts. That's probably the best.
Nikhil: Yeah so, for me, I came from, I guess, more of an infrastructure background, so I was at Salesforce where I worked in the queuing team, and also at Duetto off of that, which is a startup that works on dynamic pricing. And with that, I sort of wanted to learn more about exchanges and trading. And that's when I came to Lightyear to sort of learn more about how the decks works. And now, for example, I'm currently building trading bots to work on the decks. So I think that that was kind of like a very natural path for me. And I think that anyone with a solid understanding of distributed systems would have a good opportunity to get into Blockchain and be excited about it.
Anatoly Yakovenko, CEO of Solana
Anatoly: So I spent like 12, I think, or 13 years at Qualcomm, basically optimizing operating systems. I feel like I was born to build this operating system because I spent literally 12 years optimizing hardware and optimizing very large deployments of this hardware on like very adversarial networks throughout the world. So I think one of the projects I worked was called Brew. If you guys ever had like a CDMA flip phone, like a Motorola Razor, they all run Brew. There were 500 million of these devices, and OS ran from like a phone with two megabytes to like 128. So we had to really count every bit and byte and make it as fast as possible. And that's what we were doing. We were making a consensus work by just making the single node like really, really fast because they actually can be. We have the hardware to do so.
Sam: Cool. So I wanna wrap up the panel a bit. My last question before we open it up to Q&A, is just where can people learn more and what should they focus on?
Kevin: To learn more about our projects? Okay.
Sam: Or in life, if you have life advice or something.
Kevin: Lean more, wow. Okay. I'll just focus on our project. That's an easy question. So you can just go to our website, nervos.org. You know, from there, you can join our community. We have a Telegram channel and email list. You have a bunch of forms, you want to be more involved. Yeah, just go there.
Nikhil: So I think for developers, I think the best place to start is stellar.org/developers. And from there, you can see the APIs as well as different walk-throughs that we have on how to get started.
Anatoly: blog.solana.com. You can find all the links there. There's Telegram, there's GitHub, there's Discord, whatever you guys like.
Sam: Cool. A quick round of applause and then we'll open it up to Q&A. Cool. Who has a question?
Man: Yeah. So, anytime someone talks about scaling Blockchains or like getting really high transactions per second, I always like to understand to what degree they're choosing just a corner and like the scalability trilemma versus, like, bypassing the trilemma.
Anatoly: The trilemma is BS. It's not [inaudible 00:28:54].
Man: Well, right. Yeah. And plenty of people are trying to bypass it. Like, obviously, using hardware techniques or sharding, like are all claiming to move in a dimension, not in the trilemma, but then there's also plenty of projects that just say, "Well, hey, we're gonna sacrifice decentralization, get really high transactions per second, you know, say we've had a breakthrough." And really, it's just, they've kind of made a trade-off that other people weren't willing to make.
Anatoly: So, for us, there isn't a trade-off because we're not sharding, so we're not really sacrificing the security parameter of the network. We're still limited by the slowest node in the super majority. Our goal is just to make that node as really fast, and it's actually very doable for very cheap. Our test bed machine is off the shelf, in Nvidia Gpus. So, for 1080 ti's it's under 5k. You can do the full million elliptic verifications you need per second. The latest generation, one card can do three million per second. So how we're scaling and are aligning our project is with Moore's laws it's working today. Clock speeds are not increasing, but core accounts are. So we're making the software as paralyzable as possible. So in two years from now, we'll have 8,000 cores on a $700 card. Four years from now it's gonna be 16,000 cores. My goal is to do a billion transactions per second in 10 years, right? And that's all doable as silicon gets better.
Man: You said you're not sharding, but with that amount of transactions per second, I also imagine… I mean, you mentioned yourself that your data is gonna scale a lot. So the data you do plan on sharding or striping.
Anatoly: Yeah, the data is striped. So, we use a proof of replication technique to basically stripe it and replicate it to a very large number with a very high availability. So imagine like a thousand copies of a single slice that's throughout the network. So, with that much availability, there's, you know, a thousand nines of guaranteeing of it being a copy of it somewhere. And that is, I think as close to…that is the ultimate, like, trade-off there, right? With pure decentralization, we have a full copy in every node.
Man: So what if I have to compute state that I don't have locally on my node? Do I have to retrieve that through the network first? And then…
Anatoly: Yup. And you would need to effectively pay for it. And so, there's an incentive model to kind of pay you to store it, pay you to retrieve it, stuff like that.
Man: Micro-payments for retrieving data?
Anatoly: Yeah.
Man: Cool.
Man 2: Hey, guys. So, quick question regarding scalability. So a lot of you guys are trying to solve the issue of scalability by coming up with new consensus algorithms, but if you guys had a better kind of underlay network, right, a better infrastructure so that your packets are in blocks that are propagated through traditional internet, do you think there could be changes to your protocol if you can make assumptions around the underlying network that all of your miners, and, you know…
Anatoly: Dude, I could, like, talk hours about problem with…just with networking. Yeah, multicast, you know. It doesn't work on the internet. Like, we can send a packet of data that's supposed to go to a bunch of nodes, and switches could actually do all the re-transmission for us, but it doesn't work on the open internet. So we have to build these protocols around that. And there's a lot of difficult problems there in terms of just even verifying UDP packets where they come from. So there's a lot of interesting optimizations there. So if there's projects that are building that, I think that if the space succeeds, those projects could accelerate that and actually like 10X the performance. So, I don't know, but which project are you talking about?
Man 2: We can talk offline about it.
Anatoly: Okay. Networking is hard.
Man 3: Yeah. You mentioned briefly, your timing synchronization, I guess innovations and that enabled higher transactions per second. Can you just talk more about that?
Anatoly: Sure. That doesn't actually enable throughput. What that allows us to do is kind of decouple consensus from throughput. So what we're doing is really, it's called a verifiable delay function. And the verifiable delay function is the ledger data structure itself. So a ledger, right, is the single source of truth in the network, but it's also our clock. And it's a clock that exists before consensus because you can append to this ledger, and any petition that you append to you're generating time. So the source of time, you can think of it as a water clock, and nodes in the network can use this source of time to get a synchronous complete view of the entire network and they know that everyone else has the exact same view and they can make decisions based on that. And that allows us to shortcut a lot of the messaging overhead.
It's very similar to what Google does with its true time in the spanner database. So they have these atomic clocks that they synchronize by hand. We're simply using a cryptographic function to generate this source of time, simply.
Sam: I know we're getting kind of deep into this. Does anyone have like a simple question?
Anatoly: An easy question?
Sam: Yeah, like an easy question? Like, maybe from a non-developer.
Man 4: Not for Nervos, but for Stellar and for Solana. You were working at Lightening, so this is all to Solana. Why the focus on putting things on chain, not off chain?
Anatoly: Well, it's a cryptographically secure computer. If we can make it fast, we can actually start moving more use cases into this model. And for me, what this model really enables, it is like privacy in the internet. We have an open database of all these transactions, so we have to build everything with privacy in mind because we can't share your public data. It's shared publicly, right? We can't share your information because it's all stored in this public ledger. So we actually have to start building applications with privacy first. And it's ironic that it took an open database to give us a path to privacy in the internet. So if we can make it fast and we can make it permission-less and keep those properties, we can actually start getting rid of all these vertical sandbox technologies like Google and Facebook and Apple that are really designed to kind of keep us in a single marketplace and steal all our data and really sell it, right? And it just sucks.
Man 4: So in the interest of privacy though, why form a single data set that has everyone's information instead of separating it out into off chain and stuff?
Anatoly: Well, if as an engineer you know it's going to be open, you build it to be secure and private. So we use cryptography, right, to hide all this data, to actually prevent you from…and secure you. In a very simple case, a token is a resource of hardware. When I talk to my thermostat, it doesn't need to know about my Google account. I can just send it a little bit of resource for that one transaction over self-generated key pairs that we just created. And those disappear and we don't have this, like, Google account relationship anymore. It's literally me enabling a piece of hardware to do its job and only that. And that doesn't exist right now, and I don't know why. Right? But we can actually build that and enable that.
Sam: Any of you guys wanna take a crack at it?
Nikhil: Yeah. So I think for us, so what Lightyear is trying to do is it's trying to get partners to do a lot of the transactions actually off chain, but if they want to cross the border and talk to another entity that is also dealing with the same tokens or whatever, they would then have to go through the Stellar network and then that would have to be on chain. So it's kind of like we're trying to use a mix of both.
Kevin: Okay. The specific question actually doesn't apply to us, but, you know, our view of this is, there's no…you know, we can't capture everybody's, domain-specific requirements, right? So for some domain, they may have privacy concerns, they may have both data and algorithms running under secure [inaudible 00:38:09]. And then for some other projects, you know, it could be something totally different. You know, for enterprise applications they may not, you know, for competitive reasons or [inaudible 00:38:18] reasons, they just can't put the algorithm on chain. So for whatever reason it is, we allow people to choose their own proper, you know, settings and motor run their computation and then we don't care about how they generate it. We just look at…we allow people to define their own semantics in terms of what is, you know, what does trust mean, right? So in terms of data. And then that defines the trust semantics of the Blockchain. So, yeah. So we totally welcome, you know, off chain computation and solutions.
Sam: Again, does anyone have an easy question? Like a super simple question that you've always wondered, maybe. It doesn't have to be about these projects in particular. All right. Yeah. How do we get more people to use these things? What's missing? What do we collectively have to do to get people to care?
Anatoly: I think that once scale is there, developers will start building cool things for it and people will start using it because they're not giving up their privacy. Like, I think adoption..so I was building this like CDMA phone. We had 80% market share. And Apple came out and within a year it went the other way, 80% smartphone market share. So when there's like a catalyst that things become obvious to people that this is awesome, it'll happen like that. Until that happens, until we actually build all the tools and infrastructure for that to occur, it will be hard, but when it happens it will be very fast. And it will be obvious in retrospect. Yeah, this thing is awesome.
Nikhil: Yeah. And, just to add to that, I think there also needs to be some element of trust by the general public. I think when that does happen, people are gonna trust the Blockchain and all of that a lot more. I think right now people just outside of the bubble that we're in right now, they just think of Blockchain as a buzzword, and they're not really aware of exactly what it is. And once that barrier's crossed, I think that's gonna help with adoption.
Kevin: Yeah, I think definitely what they said. Scalability is definitely a hurdle. But I think it will be solved. So I'm actually kind of optimistic, right? So I think there are gonna be a wave of applications coming onto the Blockchain platforms, and especially optimistic about like financial applications. And a lot of it comes down to whether we have regulatory certainty, and, you know, what type of financial products, you know, we can use this new platform to enable. I think once we have that, it's gonna be a whole new world. Yeah.
Anatoly: I hope you're optimistic. I think, just to add to that, this technology is just…it's really cool because it allows us to come to agreement on something without a third party. Right? Like, all of us here can come to agreement on a source of truth without trusting anyone else to put it together. And that is the beauty of it. Like, we can use this plus cryptography to create applications that have never been possible before, and they can actually solve real world problems. Like, right now I send like money through my bank, it costs $25, because they're a bank and I have to use them, right? But with cryptography, the costs of that are pennies. Like, it actually is the cost of changing numbers and memory in a computer. So we can take all this wealth that's being spent on sending money around and give it back to the world economy and actually create wealth. And this is, I think, for an engineer, this is like the biggest opportunity in the world because I think Gartner said that we spend like $2 trillion in moving money around. Like, which is absurd, right? Like, why are we spending that much money on money?
Sam: Yeah. So I think that highlights an interesting area where suddenly…well, it's been since the internet, but suddenly as a developer, you can make real world impacts, right? It's not just about moving bits and bytes. Those changes in bits and bytes are really doing things in the real world. They're paying someone's rent or, you know, all of that. As a developer, how do you learn all of the different moving pieces about a Blockchain business, right? Because there's so much, right? There's so much to learn. It's overwhelming at times. Like, even as a developer, maybe you'll code something, but then there's like a legal issue or something. Or How do you even handle that? Or do you have to just kind of do it and run into a wall every once in awhile?
Kevin: I don't think it's different from other types of new, brand new technology that evolve very fast. When you go online, you typically find out of date tutorials, you typically found things that are no longer maintained and things evolving very, very fast. So I'll recommend going to events like this to meet people and see what people were doing. You know, go to conferences and get the most up-to-date technology. That's probably the best. And then just so willing to play with Beta software and just experiment and, yeah. I think a lot of it comes from that. Just tolerate ambiguity because there's gonna be a lot of that. And then if you fall, that's fine. Just try something else. Ask for help, go to community, you know, forums, you know, slack channels and everything. Yeah.
Nikhil: I think that's one thing that when I entered the Blockchain industry, I was completely surprised by it positively, that a lot of the projects are actually all open source. So there is a competitor [inaudible 00:44:37], I guess, software companies. There's a lot that you can do in this space without actually getting blocked by all these legal issues that obviously does come about every once in a while. Like, for example, Solana trying to encourage people to take their code and do things with it. And I think that, if you create a project, I would say that that be open source, because you will be positively surprised by how many people contribute to your codebase and help your product.
Anatoly: Just, you mentioned legal issues, I think that is the biggest gray cloud over this whole space right now in the United States. I think it will get solved sooner or later because there's simply kind of too many smart people working in this technology. So just go build stuff. Like, don't worry about it.
Sam: So I personally find the open source, like closed source thing, very interesting. Could you guys talk about kind of the design decisions or the decision in general of making your projects either open or closed source? And maybe the thought process behind how you thought it through?
Anatoly: So, for me, I started programming when I was very young. This was in the Soviet Union. And I really continued in the United States and I started working on Linux, and that's an open source project, and I just learned so much playing around with it. And I was there for the legal battle between SCO and IBM, and kind of like as the open source ecosystem matured. And I saw projects that were really promising, that stayed full source and they failed even though they might've been better technologies when an open source project had all their code out there and those communities grew and kind of created these awesome ecosystems. So from my perspective, I think anyone that's building Blockchain stuff closed source is shooting themselves in the foot, because the hardest thing in the space is getting people to understand what you're doing and getting that information to spread and be absorbed by the rest of the world. And if you put any brakes on that, you're just killing yourself. Like, nobody's gonna care about a closed source Blockchain 10 years from now.
Nikhil: Yeah. I think that's pretty much exactly what I was thinking about. And I think if you're not allowing people to contribute to your codebase, then you're just harming yourself and you're just giving other people that are encouraging others to contribute a better chance of being successful. And, yeah, I think that's kind of one of the things that we keep in mind when we try and open source things. But I think sometimes you do have to keep things closed source. And I think it's also important to consider maybe you can open source a small part of that, you know. And anything you open source, I always believe is going to just get better by contributions from other people.
Kevin: Yeah. I mean, it's not too different here. So Blockchain system in general, it's all about trust, right? So how do you gain trust of the users if you don't let them examine your source code? Right? So, what system you're running? And also, just, you know, Blockchain system in general, or public Blockchains especially, are running in the open. So there are gonna be people that constantly think about ways to attack the network, right? So you want it to have, both…if the source code is in the open, then anything that happens, you all of a sudden have your own community to try to help you and, you know, figure out the problems and evolve and go from there. Right? So, you know, for us, we're currently temporarily closing source of network CKB, but we'll open it in a few months. We're running some experiments and, you know, once the sort of source code stabilizes, we'll definitely open source everything before test nets.
Anatoly: Just do it now. No one's gonna steal your code, dude. If like, you actually imagine somebody building a team, taking your code or running with it, they have way too much time on their hand.
Kevin: I agree. It's really not for competition reasons because, you know, we're trying a few iterations just to prove things right. So for some, that's not, you know, the time yet for people to come in because that's just…we're not committed to specific design one way or the other. So once we do know the direction we go, then, you know, we'll make it open and people will come and contribute.
Anatoly: All our warts are in our code base. There's a bunch of ways to, like, knock down the test net right now. If you do so, we'll give you a T-shirt. I'm still waiting for somebody to do so. We did have a contributor that was like contributing in the weekends, and we hired him because he was awesome, and it was like, "Why don't you do this full time?"
Sam: Any questions from the audience still? Okay. Maybe final question, biggest tip that you have for an aspiring developer in this ecosystem?
Kevin: Just find a project you like and start contributing. Don't ask for permissions, right? So everything is all in the open, specifications, economic discussions, codes and building smart contracts. It's just don't wait. Yeah, just get started.
Nikhil: I think that it would be great if you could look at existing projects, see what people are doing, and then use that to inform yourself about what your project should be doing and that would allow you to not recreate what other people have already done, and maybe contribute to an existing project.
Anatoly: I think it's really hard to kind of get going. So find something you really like. I don't know, it doesn't even have to be what you normally do. You could be a JavaScript programmer, start working on encryption. You know, like, do whatever really inspires you, because we're in such a really cool and early stage in this field that you can do anything. So, go do what you really love.
Sam: Yeah. I'll add one too. Just read a lot. There's a lot of information out there, maybe too much information. So find a place where you feel comfortable, like, getting information and just, like, go there regularly and try to learn as much as you can, because it's ultimately not that hard. Right? It's doable.
Anatoly: Yeah. It's all doable.
Sam: Yeah. So, I'll encourage you guys to, like, keep at it and that you can do it. So, thank you, everybody.


text:
Sacramento blackfish
|Sacramento blackfish
|Scientific classification
Girard, 1856
O. microlepidotus
|Binomial name
|Orthodon microlepidotus
(Ayres, 1854)
Leuciscus microlepidotus Ayres, 1854
The Sacramento blackfish (Orthodon microlepidotus) is a cyprinid fish of central California. It is the sole member of its genus.
Blackfish are distinctive for their overall dark color (thus the common name). Younger individuals are more silvery, but darken as they age. The scales are unusually small, counting 90-114 along the lateral line. The forehead has a straight-line profile, the eyes are smallish, and the terminal mouth slants upwards. The dorsal fin starts just behind the pelvic fins, and has 9-11 rays, while the anal fin has 8-9 rays, and the pelvic fins 10 rays. The pharyngeal teeth are long, straight, and knife-shaped; the dorsal part of each tooth has a narrow grinding surface. They have been recorded at up to 55 cm in length.[2]
Unlike most North American cyprinids, they feed on zooplankton, planktonic algae, and floating detritus, including rotifers, copepods, cladocerans, diatoms, and the like. Younger fish pick at food items individually, while adults work by pumping large amounts of water through the oral cavity; the food bits are caught in a patch of mucus on the roof of the mouth, where it is secreted by a special organ, and then the fish swallows mucus and food together.
Blackfish are primarily denizens of the warm turbid waters found on the floor of the Central Valley, such as sloughs and oxbow lakes connected to the Sacramento and San Joaquin Rivers. They are also common in Clear Lake, Pajaro River, Salinas River, the small creeks that feed into San Francisco Bay. A population is present in the Russian River, although they may have been introduced. They also thrive in reservoirs, and have been spread to a number of California reservoirs via the California Aqueduct, and into Nevada via the Lahontan Reservoir (1964) where they have further colonized the Humboldt River drainage.
Sacramento blackfish are of some commercial significance, and are sold live at many Asian fish markets in California.
- ^ NatureServe (2015). "Orthodon microlepidotus". IUCN Red List of Threatened Species. 2015. Retrieved February 25, 2016.old-form url
- ^ Froese, Rainer and Pauly, Daniel, eds. (2016). "Orthodon microlepidotus" in FishBase. February 2016 version.
- Peter B. Moyle, Inland Fishes of California (University of California Press, 2002), pp. 144–146
- IUCN Red List least concern species
- Leuciscinae
- Endemic fauna of California
- Fish of the Western United States
- Freshwater fish of the United States
- Monotypic fish genera
- Natural history of the Central Valley (California)
- Humboldt River
- Sacramento River
- Salinas River (California)
- San Joaquin River
- Fish described in 1854
- Freshwater fish of North America


text:
A culturally-rich part of the world, Asia Pacific invites visitors to explore its vibrancy through cultural experiences, cuisine, and interaction with its warm and friendly people Yet another great way to explore the region and all that it has to offer is through the wide range of events. A diverse variety, our portfolio of events and festivals not only each country's unique culture but as well, some of the world's most revered attractions.
Explore our wide range of experiences happening in the future to secure your place at some of the world's top events. Whether it's next to the track in Singapore as the Formula 1® race cars pass by or watching athletes on the world stage at the Tokyo Olympics, our experienced team and strong relationships and partnerships ensure we have your front row access.


text:
General Information
Dixie State University is an open-enrollment institution committed to student access, affordability and success. DSU has adopted an instructional approach of "active learning. active life" and DSU is located in picturesque southwestern Utah with its red rocks, desert climate, over 300 days of sunshine annually, and featuring easy access to world class outdoor recreational opportunities. We offer 1 master's degree, 44 bachelor's degrees, 15 associate's degrees, and 124 certificates, endorsements, minors, and/or emphases for a total of 184 programs. The DSU Booth Wellness Center provides acute health care, brief mental health services, health education, and referrals so that students are able to pursue their academic, career, and personal goals. The DSU Booth Wellness Center has a staff of licensed medical and mental health practitioners. We work to provide high quality, cost-effective care for DSU students, staff and faculty. The DSU Booth Wellness Center offers wellness programming that delivers educational services and information to teach healthy approaches to life, coping skills, and encourages the development of healthy lifestyle behaviors.
The Intern Experience
The DSU Booth Wellness Center seeks to recruit Psychology Interns who will enthusiastically support the University's strong commitment to the academic success of all our students, including students of color, students with disabilities, students who are first generation to college, veterans, students with diverse socio-economic backgrounds, and students of diverse sexual orientation and gender expressions. Interns placed at the DSU Booth Wellness Center are engaged in many aspects of the services provided. Their primary clinical responsibilities at the site are conducting mental health screenings, providing brief individual therapy, and participating in Health Promotion. The intern placed at the DSU Booth Wellness Center may also have the opportunity to engage in other supervised opportunities including provision of awareness and prevention workshops, process group therapy and consultations with the medical staff, and assist in providing training, supervision or consultation to practicum students.
Special Requirements of Applicants
DSU is a tobacco-free campus.
Contact Information
Garyn Gulbranson, Ph.D. email@example.com
DSU Booth Wellness Center
St. George, UT 84770