
Someone mentioned this on the radio and now I cannot unsee this!
Thank you!
read more here:
Continue reading Upsidedown licenseplates KSomeone mentioned this on the radio and now I cannot unsee this!
Thank you!
read more here:
Continue reading Upsidedown licenseplates KBericht van mijn leverancier:
Aanpassing in uw abonnement
Bij XXX werken we continu aan de verbetering van onze dienstverlening. Graag garanderen we u de betrouwbaarste hosting en de snelste en beste service, ook weer in 2023.
Onze kosten zijn het afgelopen jaar flink gestegen, met als gevolg dat we ook uw prijzen moeten verhogen om de kwaliteit te kunnen garanderen die u van ons gewend bent. Gegeven de inflatie (de CBS CPI jaarmutatie van september bedraagt 14,5%) en de significante kostenstijgingen vanuit onze leveranciers informeren we u graag op tijd en sturen we deze brief. De belangrijkste wijziging voor u betreft een verhoging van 15% tot 20% op onze hosting services. Graag lichten we dit verder toe:
Helaas betekent dit dat ook My Brain Hosting alle prijzen in 2023 moet gaan aanpassen.
Sorry.
The sport originates from the UK, so all measurements are in feet and inches. Let’s convert these correctly.
1 foot = 12 inch, 1 inch = 25,4 mm.
From the floor to the center of the Bull’s Eye:
5 feet. 8 inches = 68 inches = 1727,2 mm
From the front of the dartboard to the Oche / throwing line:
7 feet 9 1/4 inches = 93,25 inches = 2368,55 mm
Most websites will mention 1,73m and 2,37m, but as you can see this is not quite right.
Now, let’s add some math:
As good old Pythagoras says: “a2 + b2 = c2”, so:
5610029,1025 + 2983219,84 = 8593248,9425 and get the square root from this last one gives us:
2931,424387989566 !
So, our bullseye – oche distance should be 293,14 cm long to test the measurement diagonally.
The more you know…
Have a nice day!
I like walking around with a group of people with camera’s. It is fun if you all shoot images around a common theme, so you can compare everyone’s unique vision in their photo’s later…
Here’s a list of idea’s:
Continue reading Photograpy Photowalk Themes2021… Red Bull outsmarted Mercedes:
Max Verstappen beat Lewis Hamilton!
Now do you want to see the upcoming 2022 season? You could get a F1 membership, or watch it using a free livestream. Most of the time these streams are limited to the country, but you can use a good VPN service to watch it anyway. I used to promote NordVPN (but got no commission from posting a link to them, my advise… wait until February and get an F1 subscription with a good promotion and discount… anyway…)… they say this is how it works:
Continue reading Watch Free Formula 1 streams F1Every square meter counts!
EarthToday was founded on a vision of a future society where we care for each other and the planet we live on. It is developed to sustainably facilitate a growing group of conscious people from all around the world who share the same dream. Everybody can join by protecting one or more m² of nature. From that moment on you can virtually visit your m² and curate inspiring content about nature conservation and a sustainable and holistic lifestyle.
We believe in equality, freedom, transparency and collaboration. We are organized as a for-purpose venture where 83% of all revenue is directed to the purpose. We are a community for change, and we invite you to join.
Have a nice day!
Learned something new today… Also see the wiki:
Een kilobyte, afgekort kB, is 1000 bytes. Vroeger werd er verschil gemaakt tussen een hoofd- en een kleine letter k:
k = kilo (103) | 1.000 |
K = kilo (210) | 1.024 |
In praktijk werkte dit verwarrend en bedoelde men met 1 kB vaak 1024 bytes.
De oude notatie wordt ontraden sinds er een nieuwe standaard is voor binaire voorvoegsels (zie: veelvouden van bytes). Deze standaard wordt echter nog niet veel toegepast.
Let op: het is nog steeds van belang voor de B een hoofdletter te gebruiken: een kleine letter b staat namelijk voor bit en niet voor byte.
1024 B heet nu een kibibyte, afgekort KiB. 1000 kB heet een megabyte, 1024 KiB heet een mebibyte.
In een tabel:
symbool | naam | waarde | symbool | naam | waarde | |
---|---|---|---|---|---|---|
kB | kilobyte | 10001 = 103 | KiB | kibibyte | 10241 =210 | 2,4% |
MB | megabyte | 10002 = 106 | MiB | mebibyte | 10242 =220 | 4,9% |
GB | gigabyte | 10003 = 109 | GiB | gibibyte | 10243 =230 | 7,4% |
TB | terabyte | 10004 = 1012 | TiB | tebibyte | 10244 =240 | 10,0% |
PB | petabyte | 10005 = 1015 | PiB | pebibyte | 10245 =250 | 12,6% |
EB | exabyte | 10006 = 1018 | EiB | exbibyte | 10246 =260 | 15,3% |
ZB | zettabyte | 10007 = 1021 | ZiB | zebibyte | 10247 =270 | 18,1% |
YB | yottabyte | 10008 = 1024 | YiB | yobibyte | 10248 =280 | 20,9% |
The more you know… 🙂
I ran into this issue: Any link in my code/theme/plugin to standard Woocommerce pages did not go to the correct translated page!
However the solution provided here will break whenever WooCommerce is updated. The correct way of solving this is adding some filters…
//20210216 - (c) My Brain - correction for function wc_get_page_id()
function woocommerce_translate_polylang_page_id($pageid) {
if (!empty($pageid)) {
if (PLL() instanceof PLL_Frontend) {
$pllpageid = pll_get_post($pageid);
if (!empty($pllpageid)) {
$pageid = $pllpageid;
}
}
}
return $pageid;
}
//myaccount, edit_address, shop, cart, checkout, pay, view_order, terms
add_filter( 'woocommerce_get_myaccount_page_id', array( $this, 'woocommerce_translate_polylang_page_id' ), 10, 1 );
add_filter( 'woocommerce_get_edit_address_page_id', array( $this, 'woocommerce_translate_polylang_page_id' ), 10, 1 );
add_filter( 'woocommerce_get_shop_page_id', array( $this, 'woocommerce_translate_polylang_page_id' ), 10, 1 );
add_filter( 'woocommerce_get_cart_page_id', array( $this, 'woocommerce_translate_polylang_page_id' ), 10, 1 );
add_filter( 'woocommerce_get_checkout_page_id', array( $this, 'woocommerce_translate_polylang_page_id' ), 10, 1 );
add_filter( 'woocommerce_get_pay_page_id', array( $this, 'woocommerce_translate_polylang_page_id' ), 10, 1 );
add_filter( 'woocommerce_get_view_order_page_id', array( $this, 'woocommerce_translate_polylang_page_id' ), 10, 1 );
add_filter( 'woocommerce_get_terms_page_id', array( $this, 'woocommerce_translate_polylang_page_id' ), 10, 1 );
Have a nice day!
HTTP Error 413.1 – Request Entity Too Large – The page was not displayed because the request entity is too large.
Large file? Large problem! On IIS you can get this error while trying to upload. Read this and then think… maybe edit the web.config file in the root? So you try adding this, or something similar:
<serverRuntime>
<uploadReadAheadSize>2147483647</uploadReadAheadSize>
</serverRuntime>
<security>
<requestFiltering>
<requestLimits>
<maxAllowedContentLength>2147483647</maxAllowedContentLength>
</requestLimits>
</requestFiltering>
</security>
but you simply get: HTTP Error 500.19 – Internal Server Error – The requested page cannot be accessed because the related configuration data for the page is invalid. – so, whatever you were thinking is: Wrong!
When using IIS manager you get:
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="2147483647" />
</requestFiltering>
</security>
while the ‘uploadReadAheadSize’ does not appear anywhere in the web.config. But: it helps and there are no more errors while uploading!
So you have to set these values in IIS Manager itself.
Problem? Solved!
Have a nice day!