Blatantly Partisan Party Review VI (NSW 2023): Group G (Silvana Nile / Revive Australia Party)
Prior reviews (as the Christian Democratic Party): federal 2013, federal 2016, NSW 2019, federal 2019
What I said before: “The CDP sees no place in society for people who think, behave, or believe differently to them. Unless you worship the strict, narrowly-defined, judgemental, petty god to whom the CDP claims allegiance, this party is not for you.” (federal 2019)
What I think this year: This is all just a little bit weird really. Fred Nile was first elected to the NSW Legislative Council in 1981 for the Call to Australia Party, the predecessor of the Christian Democratic Party. He has been in the NSW parliament for over 40 years now; he is 88 years old. He secured the election of his first wife alongside himself for 14 years, the late Elaine Nile, and his second wife Silvana is running this year.
Perhaps unsurprisingly, Fred announced his retirement in 2021, endorsing Lyle Shelton as his successor. But then he rescinded the deal (eat shit Lyle) and has served out his term. The CDP dissolved in 2022 and Nile joined Seniors United, but it too has been dissolved. He again announced his retirement in October 2022, but—you can see where this is going—announced last month that he’d stand again. Weirdly, he’s the second candidate to his wife Silvana, and they are the only two candidates in Group G. They do not get a square above the line (you need 15 candidates for that) and even if they had a square above the live and Silvana won election, there’s no chance they’d get a high enough vote for Fred to win a seat from second place. Why is he going out on a loss rather than retiring with dignity? Strange stuff.
Anyway, don’t vote for the Niles, they’re awful bigots. I would say they’ve leapt on the latest bandwagon of bile against drag queens, but Fred’s been pulling that particular wagon since he came to prominence as an opponent of Mardi Gras in the 1980s. Forty years down the track and he has not become a better person.
Recommendation: Give Group G (Silvana Nile / Revive Australia Party) a weak or no preference.
Website: https://www.facebook.com/fnileindp/
6 notes
·
View notes
Nile Archer's Blog: Marketing Insights
Is streamlining fan user data the most effective way to generate effective marketing campaigns for Sports?
The NBA has entered into a multi-year, league-wide partnership with the fan engagement platform StellarAlgo, according to a press release. The league has also taken an equity stake in the company, which was founded in 2016.
In 2017, the LA Kings (AEG) partnered with StellarAlgo a customer data platform (CDP) that helps organizations in the sports and entertainment industry improve their fan engagement strategies. It uses data analytics and machine learning algorithms to identify and target high-value fans, personalize marketing messages, and optimize ticket sales and revenue. The platform also provides insights on fan behavior, preferences, and demographics, which can help organizations make data-driven decisions to enhance the fan experience and increase fan loyalty. StellarAlgo's clients include professional sports teams, college athletics programs, and live entertainment venues.
Approximately, 72% of consumers only engage with marketing messages that are personalized to their interests according to ProemSports.com
Personalized messages feel more relevant, valuable, and tailored to their specific needs and preferences. Personalization allows marketers to create more targeted and relevant messages that are tailored to each individual's interests, behaviors, and preferences. When consumers receive messages that are personalized to their needs, they are more likely to pay attention and engage with the message, leading to higher response rates, conversions, and sales.
Furthermore, personalized messages help to build stronger relationships between consumers and brands. When consumers feel that a brand understands their needs and preferences, I feel like they are more likely to trust and be loyal to that brand over time.
2 notes
·
View notes
CCNA Exercise 14: Cisco Router and Switch Basics
Objective: Verify Cisco Discovery Protocol (CDP) and analyze the effects of interface speed and duplex configuration
R1 is a router. The FastEthernet0/0 (F0/0) interface has an IP address of 10.10.10.1/24 which connects into the FastEthernet0/1 (F0/1) interface on SW1 (which is the switch). The /24 tells us the subnet mask is 255.255.255.0, this is called the CIDR value
R2 is also a router. The FastEthernet0/0 (F0/0) interface has an IP address of 10.10.10.2/24 which connects into the FastEthernet0/2 (F0/2) interface on SW1 (which is the switch). The /24 tells us the subnet mask is 255.255.255.0
> denotes you’re in user exec mode
# denotes you’re in privileged exec mode
(config)# denotes you’re in global configuration mode
Configure Router 1 with hostname of R1
enable - enter privileged exec mode
config t - enter global configuration mode. Full command is configuration terminal. I just shortened it here, which you can do for every command!
hostname r1 - renaming the router to “r1″. Command is hostname [the name you want]
Configure Router 2 with hostname of R2
enable - enter privileged exec mode
config t - enter global configuration mode
hostname r2 - renaming the router to “r2″
Configure switch 1 with hostname of sw1
enable - enter privileged exec mode
config t - enter global configuration mode
hostname sw1 - renaming the switch to “sw1″
Configure FastEthernet0/0 (F0/0) with an IP address of 10.10.10.1/24 on R1
enable - enter privileged exec mode
config t - enter global configuration mode
interface fastethernet0/0 - stepping inside the fastethernet0/0 interface
ip address 10.10.10.1 255.255.255.0 - giving f0/0 an IP address of 10.10.10.1 and a subnet mask of 255.255.255.0. Command is ip address [ip address you want] [subnet mask]
no shutdown - by default all interfaces are not enabled. This command brings them up
We can verify we configured it correctly by running the show ip interface brief command or show interface [interface name] command. Show commands cannot be run when you’re in the configuration terminal mode
Also see that FastEthernet0/1 is down/down? That’s the default state of interfaces
Configure FastEthernet0/0 on R2 with an IP address of 10.10.10.2/24
enable - enter privileged exec mode
config t - enter global configuration mode
interface fastethernet0/0 - stepping inside the fastethernet0/0 interface
ip address 10.10.10.2 255.255.255.0 - giving f0/0 an ip address of 10.10.10.2 and a subnet mask of 255.255.255.0. Command is ip address [ip address you want] [subnet mask]
no shutdown - by default all interfaces are not enabled. This command brings them up
Verifying with show ip interface brief and show interface commands
Give SW1 the management IP address 10.10.10.10/24
Note: Management IP addresses on switches are configured on the VLAN1 interface. The management IP address is used to connect to the switch (via ssh, etc) to manage the switch. When we configure the VLAN, it is called the switched virtual interface.
/24 tells us the subnet mask is 255.255.255.0
enable - enter privileged exec mode
config t - enter global configuration mode
interface vlan1 - stepping inside the vlan1 interface
ip address 10.10.10.10 255.255.255.0 - giving the vlan1 interface an IP address of 10.10.10.10 and a subnet mask of 255.255.255.0. Command is ip address [ip address you want] [subnet mask]
no shutdown - enabling the vlan1 interface, by default interfaces are not enabled
The switch should have connectivity to other subnets via R2
I didn’t understand this at first because I was like, there are no other subnets? But that didn’t matter and really it’s telling us that the switch should be able to reach other subnets (sub networks, other networks) via R2. Don’t know why I wasn’t understand it! But how do devices reach outside their network? Why through the default gateway of course~
So basically I need to set the switch’s default gateway to 10.10.10.2 because this is the IP address of the FastEthernet0/0 interface on R2 which the switch (SW1) is directly connected to!
So in SW1...
enable - enter privileged exec mode
config t - enter global configuration mode
ip default-gateway 10.10.10.2 - setting the default gateway to 10.10.10.2
Verifying SW1 is able to ping 10.10.10.2
ping 10.10.10.2
Also, made a mistake here. I tried pinging while I was in the enter global configuration mode, forgot you can’t do that. I had to exit and get back to the privileged exec mode or user exec mode
On SW1, verify that speed and duplex are automatically negotiated to 100
Mbps full duplex on the link to R1
R1 connects to the FastEthernet0/1 interface on SW1. The command to view details of an interface is show interface [interface name]
enable
show interface fastethernet0/1
As you can see in the highlighted text above, we ran the command show interface fastethernet0/0 and we can see “Full Duplex, 100Mb/s” So the duplex is set to Full and the speed is set to 100Mbps
Manually configure full duplex and FastEthernet speed on the link to R2
R2 connects to the FastEthernet0/2 interface on SW1. So we need to configure FastEthernet0/2. The command to set the duplex is duplex [full, half], the command to set the speed is speed [10, 100, 1000].
enable - enter privileged exec mode
config t - enter global configuration mode
interface fastethernet 0/2 - stepping inside the fastethernet0/2 interface
duplex full - setting the duplex to full
speed 100 - setting the speed to 100mbps
When we changed the duplex to full on the FastEthernet0/2 interface, the connection dropped! But why? After being puzzled for a bit I remembered that when you manually configure an interface, you must manually configure the other side! The other side being the FastEthernet0/0 interface on R2 that SW1 is directly connected to.
So hopping on R2 you can see the message, “... interface fastethernet0/0, changed state to down” I ran the show ip interface brief command just to confirm, and yep, it’s down
But why does it also say “up” under “Status”? Well that’s because we enabled the interface by running no shutdown on it! The interface is enabled but the link is down. To bring it back up, we gotta manually configure it just like we did on SW1.
enable - enter privileged exec mode
config t - enter global configuration mode
interface fastethernet0/0 - stepping inside the interface
duplex full - setting the duplex to full
speed 100 - setting the speed to 100Mbps
And as you can see above, the FastEthernet0/0 interface came back up as soon as we set the duplex to full
What version of IOS is the switch running?
Two things come to mind, we can either run reload on the switch to restart the switch, which then will show us the version or we can run show cdp neighbors detail on any other connected device. Let’s do both?
Restarting the switch
Running show cdp neighbors detail on R2
Also, I cheated a google’d another way and yeah, you can run show version on the switch itself too!
Verify the status of the switch port connected to R2 with the show ip interface brief command. It should show status and protocol up/up.
Verify the directly attached Cisco neighbors using Cisco Discovery
Protocol
So I guess we have run show cdp neighbors detail on all devices!
Running show cdp neighbors detail on R1
Running show cdp neighbors detail on SW1
Running show cdp neighbors detail on R2
Prevent R1 from discovering information about Switch 1 via CDP
There are two commands to disable Cisco Device Protocol (CDP), no cdp run is to disable it globally, no cdp enable is to only disable it on a specific interface, but you have the step inside the interface first.
Since R1 is connected to SW1 on FastEthernet0/1, we’re going to run no cdp enable on the FastEthernet0/1 interface on SW1
enable - enter privileged exec mode
config t - enter global configuration mode
interface fastethernet0/1 - stepping inside the interface
no cdp enable - disabling cdp from running on this interface, which prevents R1 from using CDP to discover SW1
Flush the CDP cache on R1 by entering the ‘no cdp run’ then ‘cdp run’ commands in global configuration mode and then verify R1 cannot see SW1 using CDP
enable - enter privileged exec mode
config t - enter global configuration mode
no cdp run - disabling cisco device protocol (cdp)
cdp run - enabling cisco device protocol (cdp)
exit - exiting global configuration mode
show cdp neighbors detail - discovering devices using cisco device protocol
Since we’re making a change on the router, we have to enter the global configuration mode. Once we ran the cdp commands we exited out of global configuration mode to run the show cdp neighbors detail command and R1 wasn’t able to find anything
Verify the status of the switch port connected to R2 with the show ip interface brief command. It should show status and protocol up/up
Shut down the interface connected to R2 and issue a show ip interface brief command again. The status and protocol should show administratively down/down
enable - enter privileged exec mode
config t - enter global configuration mode
interface fastethernet0/2 - stepping inside the fastethernet0/2 interface
shutdown - shutting down the fastethernet0/2 interface
exit - getting out of the interface
exit - getting out of the global configuration mode
show ip interface brief
I exited out of the configuration modes because we can’t run the show commands while we’re in there
Bring the interface up again. Verify the speed and duplex setting
Duplex is set to Full and speed is 100Mbps
Set the duplex to half on Switch 1. Leave the settings as they are on R2 and verify the state of the interface
enable - enter privileged exec mode
config t - enter global configuration mode
interface fastethernet0/2 - stepping inside the fastethernet0/2 interface
duplex half - setting the duplex to half
exit - getting out of the interface
exit - getting out of the global configuration mode
show ip interface brief
After changing the duplex to half on the FastEthernet0/2 interface on SW1, the connection dropped! And just like before, this happened because by default the duplex and speed are set to auto negotiate and when you manually configure an interface you must manually configure the other side as well!
Set the duplex back to full duplex and set the speed to 10. Check if device is still operational
enable - enter privileged exec mode
config t - enter global configuration mode
duplex full - setting the duplex to full. Only options here are full or half
speed 10 - setting the speed to 10. Options here are 10, 100, or 1000 in Mbps
exit - getting out of the interface
exit - getting out of global configuration mode
show ip interface brief
The FastEthernet0/2 interface is showing as down/down
Check if the interface is operational on R2. What is the status of the
interface
The FastEthernet0/0 interface on R2 is showing as up/down. Meaning the interface is enabled but the link is down
2 notes
·
View notes
𝐒ı𝐧ı𝐫𝐝𝐚 𝐊𝐚𝐫𝐛𝐨𝐧 𝐃𝐮̈𝐳𝐞𝐧𝐥𝐞𝐦𝐞𝐬𝐢 𝐌𝐞𝐤𝐚𝐧𝐢𝐳𝐦𝐚𝐬ı (𝐒𝐊𝐃𝐌) 𝐤𝐚𝐩𝐬𝐚𝐦ı𝐧𝐝𝐚 𝐲𝐚𝐩ı𝐥𝐚𝐧 𝐊𝐚𝐫𝐛𝐨𝐧 𝐄𝐦𝐢𝐬𝐲𝐨𝐧𝐮 𝐎̈𝐥𝐜̧𝐮̈𝐦𝐮̈ 𝐯𝐞 𝐑𝐚𝐩𝐨𝐫𝐥𝐚𝐦𝐚𝐬ı, 𝐀𝐁'𝐲𝐞 𝐢𝐡𝐫𝐚𝐜𝐚𝐭 𝐲𝐚𝐩𝐚𝐧 𝐮̈𝐥𝐤𝐞𝐥𝐞𝐫𝐝𝐞𝐤𝐢 𝐮̈𝐫𝐞𝐭𝐢𝐜𝐢𝐥𝐞𝐫 𝐯𝐞 𝐢𝐡𝐫𝐚𝐜𝐚𝐭𝐜̧ı𝐥𝐚𝐫 𝐭𝐚𝐫𝐚𝐟ı𝐧𝐝𝐚𝐧 𝐲𝐚𝐩ı𝐥𝐦𝐚𝐬ı 𝐢𝐬𝐭𝐞𝐧𝐞𝐧 𝐛𝐢𝐫 𝐫𝐚𝐩𝐨𝐫𝐥𝐚𝐦𝐚 𝐯𝐞 𝐛𝐢𝐥𝐝𝐢𝐫𝐢𝐦𝐝𝐢𝐫.
Bu durum, özellikle karbon yoğun sektörlerde faaliyet gösteren firmaları etkileyecektir.
SKDM, AB dışından ithal edilen belirli ürünler için geçerlidir ve bu ürünlerin üretimindeki karbon emisyonlarının maliyetini içermesi amacıyla tasarlanmış bir sistemdir.
İthalatçılar, SKDM kapsamındaki ürünleri AB'ye ithal etmek istediklerinde, bu ürünlerin üretimi sırasında ortaya çıkan karbon emisyonlarının miktarına karşılık gelen bir maliyeti karşılamak zorundadır. Sistemin amacı ise AB içindeki üreticiler ile dışarıdan gelen üreticiler arasında adil bir rekabet ortamı yaratmak ve karbon emisyonlarını azaltmaktır.
𝐀𝐁 𝐝ı𝐬̧ı𝐧𝐝𝐚𝐤𝐢 𝐮̈𝐫𝐞𝐭𝐢𝐜𝐢𝐥𝐞𝐫 𝐯𝐞 𝐢𝐡𝐫𝐚𝐜𝐚𝐭𝐜̧ı𝐥𝐚𝐫 𝐒𝐊𝐃𝐌'𝐧𝐢𝐧 𝐠𝐞𝐫𝐞𝐤𝐥𝐢𝐥𝐢𝐤𝐥𝐞𝐫𝐢𝐧𝐢 𝐲𝐞𝐫𝐢𝐧𝐞 𝐠𝐞𝐭𝐢𝐫𝐦𝐞𝐤 𝐯𝐞 𝐢𝐥𝐠𝐢𝐥𝐢 𝐤𝐚𝐫𝐛𝐨𝐧 𝐬𝐞𝐫𝐭𝐢𝐟𝐢𝐤𝐚𝐥𝐚𝐫ı𝐧ı 𝐚𝐥𝐦𝐚𝐤 𝐢𝐜̧𝐢𝐧 𝐤𝐚𝐫𝐛𝐨𝐧 𝐞𝐦𝐢𝐬𝐲𝐨𝐧𝐮 𝐡𝐞𝐬𝐚𝐩𝐥𝐚𝐦𝐚𝐥𝐚𝐫ı𝐧ı 𝐲𝐚𝐩𝐦𝐚𝐥ı 𝐯𝐞 𝐛𝐮 𝐛𝐢𝐥𝐠𝐢𝐥𝐞𝐫𝐢 𝐀𝐁 𝐢𝐭𝐡𝐚𝐥𝐚𝐭𝐜̧ı𝐥𝐚𝐫ı𝐧𝐚 𝐬𝐮𝐧𝐦𝐚𝐥ı𝐝ı𝐫.
𝐒𝐊𝐃𝐌 𝐢𝐥𝐞 𝐢𝐥𝐠𝐢𝐥𝐢 𝐭𝐮̈𝐦 𝐬𝐮̈𝐫𝐞𝐜̧𝐥𝐞𝐫𝐝𝐞 𝐝𝐞𝐬𝐭𝐞𝐤 𝐚𝐥𝐦𝐚𝐤 𝐢𝐜̧𝐢𝐧 QSI BELGELENDİRME LTD.ŞTİ 𝐢𝐥𝐞 𝐢𝐫𝐭𝐢𝐛𝐚𝐭𝐚 𝐠𝐞𝐜̧𝐞𝐛𝐢𝐥𝐢𝐫𝐬𝐢𝐧𝐢𝐳
Detaylı Bilgi Almak İçin;
📞 +𝟗𝟎 𝟑𝟏𝟐 𝟒𝟕𝟐 𝟔𝟎 𝟔𝟕
📧 𝐢𝐧𝐟𝐨@𝐪𝐬𝐢.𝐜𝐨𝐦.𝐭𝐫
0 notes