Jak ukarać Śląsk Wrocław za korupcję sprzed lat

O tym, że Śląsk ustawiał mecze w III lidze prokuratura wiedziała już od kilku lat, wyjaśnienia w tej sprawie złożył jeden z sędziów. Jednak śledztwo trwało, trwało... i zakończyło się dopiero pod koniec ubiegłego roku (więcej na ten temat) tutaj. Śledztwo śledztwem, akt oskarżenia aktem oskarżenia, a wyroki karne wyrokami karnymi. Kibiców mniej obchodzą. Bardziej interesują ich konsekwencje dyscyplinarne wobec klubu. Klubu, który jest teraz liderem ekstraklasy. Niechętni Śląskowi kibice żądają degradacji, degradacji żądają też fani klubów, które zostały "spuszczone" do niższych lig (np. Widzewa Łódź, Górnika Polkowice, Zagłębia Lubin czy Arki Gdynia), miłośnicy Śląska są oczywiście przeciwni. Twierdzą, że sam klub nie powinien odpowiadać za korupcję sprzed lat. I doszukują się jakiś spisków innych klubów walczących w tym sezonie o mistrzostwo.
Niektórzy twierdzą dodatkowo, że PZPN zdecydował o abolicji by nie karać wybranych klubów (Śląsk, Cracovia i Lech Poznań).

Ja sam jestem kibicem Śląska od końcówki lat 70. I ciężko mi wyobrazić sobie, że teraz gdy mamy szansę na "mistrza" moglibyśmy zostać zdegradowani czy niedopuszczeni do gry w europejskich pucharach. Jednak nie mam wątpliwości - jeśli Śląsk ma na sumieniu korupcję - karę powinien ponieść. I to surową karę. Nawet degradacją. Chociaż trzeba miarkować - siedem ustawionych meczów Śląska to nie to samo co prawie 40. Arki Gdynia...

Pozostaje czekać na decyzję Wydziału Dyscypliny PZPN. Oby szybką decyzję!
Komentarze do artykułu (474)
komentarze od 16 - 20 z 474
  • 16 04.05.2012 22:16 Hey, thanks for ntincoig our project! A couple of follow-up notes on FeedTree:Yeah, Java is a pain. Unfortunately, most of the leading academic research into scalable peer-to-peer overlays is done in Java, so that's the platform FeedTree is built on. (Yes, I know BitTorrent is Python; it's also really the wrong kind of p2p system for this application.) Fortunately, some of the future work of the team includes developing a new runtime-independent binary wire protocol, so one could develop a compatible Pastry implementation in some other language (FeedTree then being layered atop that).It's true, we could have made digital signatures mandatory on the part of publishers. We chose not to for a couple of reasons, chief among them adoption. We figured it would be daunting enough to get feed owners to install a persistent daemon, let alone messing around with certificates. Maybe it's a flimsy reason, but we're eager to do whatever we can to spur adoption. This is a problem domain (feed updates on a push schedule, fixing the ping crisis , keeping the bandwidth manageable) that can really benefit from peer-to-peer techniques.[It's also worth noting that sometimes you can't sign things. When there's no authoritative publisher pushing feed content to the FeedTree network (what we call a "conventional" or "legacy" feed), FeedTree subscribers self-organize into a collaborative polling scheme (staggering their requests, and sharing new events with one another). The thing is, none of them is really authoritative, so it's not meaningful for them to sign their content; as such, if you use FeedTree, you'll see that these shared events carry no signature and can't be authenticated.]If, in the worst (best?) case, FeedTree should become so popular that spammers start to try to fill it with spam pings, there are a couple of properties of the network that should make this a losing proposition, long-term:If you're not subscribed to the feed, you don't see its updates. If a user injects a bunch of bogus updates for a splog nobody cares about, those updates won't reach any eyeballs. There will be some network overhead if this happens, but it should be limited to a small portion of the system (and, again, no users will see any of the spam pings).If spammers start injecting junk into legit feed channels, it's pretty easy to say, OK, for this feed I'll ignore any unsigned updates. If FeedTree's ever so popular that this scenario becomes reality, the publishers of those spammed feeds will have incentive to reach their readers using FeedTree, and will hopefully invest the effort to start pushing signed updates. Jade
  • 17 05.05.2012 02:25 Anyways, At $work we do not currently acpcet pings from anyone. Instead we crawl every site in our system, every 30 minutes. Its not that hard, honestly, thanks to memcached and conditional http requests. (Oh, and lots of bandwidth). This does help Bloglines maintain a fresh index, but there are various ways that your algorithm could be improved that would save others bandwidth and respect established protocols such as the RSS 2.0 channel-level ttl element. Intelligent spacing of visits, based on historical frequency of posting would also not be a bad thing. For systems with lots of feeds, a deluge of 10 requests per second, twice an hour, on top of normal loads of traffic can be crippling. We've had to start sending 304 s to Bloglines during peak hours. Nicolas
  • 18 05.05.2012 02:29 Khun Battambang Kid :ai phanthamitr man sun phan mot leo tich teat ov me vea kor ngeab chol vea hey 0 likes Long
  • 19 05.05.2012 04:11 I relaly wish there were more articles like this on the web. Wannisa
  • 20 05.05.2012 07:02 This is really attnotien-grabbing, You're an excessively professional blogger. I have joined your feed and look forward to seeking more of your magnificent post. Also, I've shared your website in my social networks ElNegro
komentarze od 16 - 20 z 474
podpis:

mail:

komentarz:

Publikowane komentarze są prywatnymi opiniami użytkowników. Polskie Radio S.A. nie ponosi odpowiedzialności za ich treść. Komentarze zawierające wulgaryzmy (art. 3 Ustawy o języku polskim z dnia 7 października 1999r.), będą usuwane.