Alternatively, you just described the effects of going clubbing and using 'pejorative' language near aggressive fellow patrons...
36 posts • joined 10 Nov 2011
...for this would be for this thread to be closed to comments, and for the two (or more!) entities concerned to settle this bullshit little spat like adults, and out of public view.
Anything less dignifies this BS!
Just man up and sort it out between yourselves without involving us (well, me anyway). It's like two teenagers arguing!
Someone, somewhere, must be able to correlate which repeater was active at the time of the offending broadcast, which gives you an input frequency to listen on, and a rough location.
Having a rough location reduces the number of variables to manageable proportions...I guess:-) I have an amateur licence (G7, if anyone is interested), and have found (a while ago, I admit) that a little traffic analysis really helps with fox-hunts.
That said, I confess I don't fully understand their radio architecture...but the principles don't change:-)
Anecdotally, some fellow members of my local radio society were lucky enough to get hold of some ex-police Motorola UHF programmable handhelds around the time plod switched to Tetra....and one of them got
hammering from the local low-lifes who mistook them for el Fuzz:-)
>only 10Mbps and dial up was 56kbps...
10Mbps half-duplex, on a hub with lots of other users hanging off the other ports...meaning a big collision domain and shite throughout for all.
56K was 'up to' 56k, and frequently less than that. I was working for a major telecoms equipment manufacturer then, and had the job understanding the impact of this new-fangled V.90 stuff on our equipment and network, then adjusting our stuff accordingly. Oh what fun!
Even under laboratory conditions (as opposed to 'real world' conditions), lots of different manufactures kit struggled to interoperate at >45k reliably. Common trick was to establish at and report a high connection speed to appear good, then fall back to a lower speed for reliability/stability reasons. Plus things like running Lap-m (HDLC, really) introduced further overhead.
I went on to develop ADSL DSLAMS for a while, then moved on to other things before VDSL became a thing.
Bottom line here is that nothing apart from the base speed of the low layer bitstream has changed. Base speed is now several orders of magnitude above that of the 90s, but the other issues (Selling/differentiating on reported speed, rather than useable throughout), optimising for appearance rather than performance etc.) remain the same.
...the conversation went like this:
Dev grunt:"It's still not quite right"
Dev lead:"but does it work well enough? Remember, we are horrendously late with it already?"
Grunt:"Not really, still got some schema and logic issues in the time processing. Also, it depends on which version of the requirements you assess it against."
Lead:"Ah... I'll see what higher management want to do..."
Mgmt:"Give us what you have, we can't be seen to fail the timescales we gave the head honcho!"
...of the article!
Not living in a Virgin service area (thank $DEITY ?) one is 'meah' about Virgin and their network....but the class ASCII art is another thing. Nice to see some again:-)
Now, where did I put that old fan-fold-and-sprocket-holed paper for the noisy old line printer!
....and it is that the guy is a 'stirrer' and not worth a light.
The Pi foundation has done a wonderful job of bringing an affordable educational tool to market, and all this numpty can do is moan.
Engineering is actually a gender-neutral arena, although I admit it is rather male dominated.
Whilst I respect his right to an opinion, I don't see why he would expect me to sign a petition endorsing it! After all, "Opinions are like ars****les, everyone has got one".
He should just stop meddling and let people form their own opinions!
... here is bollocks design!
Leaving aside the obvious information leakage and privacy issues (well covered above), who thinks it is acceptable to waste bandwidth ('cheap' xDSL/DOCSIS or 'expensive' cellular) and server-side resources with this 'char by char' lookup rubbish?
And don't get me started on the probable* piss-poor performance of the client app due to the latency if the public WAN/lower layers.
What a waste! When will people realise that bandwidth is neither free or limitless, and as a designer you have an obligation to minimise it's use by what you write.
This shoddy design makes my teeth itch!
No wonder ever increasing broadband speed is of such importance...it has to carry all this cruft..as well as the cruft that masquerades as 'content'.
(* One is not a WhatsApp user, so I cannot test my assumption)
Seriously, do we really need yet more 'crawler' traffic indexing the web?
Competition is good, but how on earth do they think they can compete with the established players in search...and, what makes them think they are competant to do it anyway?
Thinks:Hope they don't expect us to maintain the content of their index for them!
Never mind all that worrying...I say more power to the guy.
Typical British pluck...he wanted to do something, no-one was going do it for him so he got off his arse and did it himself, probably learning loads in the process.
Ever tried to do something just to see if you can? I have, and it's one of the most rewarding feelings ever when whatever it is you have attempted to do or make works.
We need more people like him - in the tech. industry, in Britain and in the world.
Ta for a decent review...however (unless this evening's ration of vin rouge has crossed my eyes too much) I didn't see anything about the codecs supported and how it performed on on a voice call... there are *some* of us who still have to talk on these smart devices! Text/MMS/data capabilities are important, but so is voice.
Have you ever tried to get complex equipment, or even simple stuff, through UL, TUV or CSA certification? Not as easy as it sounds, I promise you!
Having said that, the only way to prevent poor conducted or radiated EMC performance (meaning interference! ) is good product design that conforms to well established rules and best practice.
Oh yeah - the powerline technology on sale now (and probably in the future) is an abomination that should be taken out and shot. It's truly awful shit that broadcasts electromagnetic effluent around the home and immediately surrounding area. FM/DAB radio not working properly? Radio-dependant remote controls playing up? If so, turn your bloody PLT gear off!
>they went with whatever they had come the promised released date.
An ex employer used to do this all the while..the hardware and software was delivered in whatever state it was in, usually...true, there were release criteria, but these were best described as 'flexible':-) Us integration and test people always bitched at release meetings as we knew that *we*, not the support arm of the company, would be on the phone & VPNs for weeks after a 'managed release'. I know you have to get the stuff out there, but....sheeesh!
Sound familiar to anyone?
Everyone cries, because
1) MS-published rules and information is generally incomprehensible and/or ambiguous, leading to confusion;
2) When it comes to the WWW, the ratio of speculation/assumption/supposition/bullshit to accurate facts is huge....well written and accurate info is hard to come by and too many people read the bullshit without realising that it *is* useless/erroneous crap....
3) People like to moan!
Leaving aside the inevitable quips about grumble-flick-searchers' failed requests possibly encountering '417 Expectation Failed' or even '411 Length Required', it strikes me that :-
If some entity has decreed (Irrespective of the popularity, validity and correctness of said decree) that content available from a web server has been deemed unacceptable AND they have the clout to enforce it, what *is* wrong with the idea of a specific HTTP Error (In either the 4xx or 5xx series) being provided to the requesting client?
Looking at the existing list of 4xx and 5xx codes (See RFC2616 etc.), we see most of them have detailed and explicit use-cases...which are all designed for known or anticipated specific conditions.
IMHO this business of government censorship of the World Wide Web (If not the other wider aspects of the Internet) is a NEW specific condition which ought to be separately identified with it's own unique error code and use case with sensible optional or mandatory supplementary information. I'm thinking of it as a new requirement for HTTP.
And before someone jumps on me for supporting censorship - I don't. I'm merely pointing out that HTTP needs to evolve along with the rest of us, no matter what individuals think of censorship, politics or the 'nanny state'.
I'm not gonna guess on the details of this new error may be - there are enough people with bias doing that already [ '451' indeed, we are NOT in that sort of autocratic state as yet, and I hope we never are :-) ].
I think this bloody censorship-at-ISP level is a joke and is not the way to go..gotta be a better way than that for all concerned.
Fail, as there is no icon for cluster-f**k.
Synthi-meat? Sounds like someone is pulling a fast one here, make sure it's not 'Soylent Green' before tuckling in :-)
This is all very clever, but the point escapes me - it must be cheaper and tasitier to grow one's animal protein in the traditional manner......oh, I see - this synthi-meat won't contribute to global warming due to it's lack of methane emissions :-)
BTW, I believe 'The Space Merchants' was written by both Frederik Pohl AND Cyril Kornbluth - David Willis omitted Cyril Kornbluth from his credits, which means Mr. Kornbluth didn't get the recognition he deserved for such a cracking read :-)
Sometimes I wonder if these two guys actually had managed to predict the future - now, to which advertising behmoth(s?) can we assign the 'Chlorella Protiens' role?
Penguin 'coz that's what this stuff will taste like :-)
I had one of these for years, until it died from being lugged around. It was a brilliant machine, by far a leader in it's class - what a spec. out of the box!
Mine was used for BASIC programming practise but really came into it's own with the Front Panel assembler system - I wrote the assembler code for a home-brew digital sampler / reverb machine (Still got the listing somewhere!) which had 512KB of SRAM as I worked for a major telecoms firm repairing stuff and SRAM was cheaply available :-)
The software development cycle used was laborious by today's standards : Write the code and copy it to a battery-backed (PP3, 7805) SRAM via a homebrew interface board (74LS138, 74LS245, 74LS00, VeroBoard with VeroWire - anyone remember them?) and make sure it worked on the real hardware, then once it did, I'd take the SRAM to work, load it into the EPROM programmer and actually turn it into Firmware!
I even got my employer out of the brown stuff with it when someone went postal and scrubbed some all-important Z80 firmware - hex editing was never so much fun, and I got to show off my marvelous Memotech toy (And comparitively 'funky' I/F Board) to my colleagues.
There was only ever one game I played on it - 'Maxima', written by a 'D. Richie' and published by a software house (Name maybe 'Psi'?) based on the Stoney Stanton Road in Coventry. Co-incidentally, I ended up working with the very same Doug Richie a number of years later - turns out we'd been working for the same firm for ages all along (He was a 'Softie', I was a 'Hardie' at the time). We got a decent jolly off to Atlanta, GA.
That machine taught me more about software and hardware than anything else, was invaluable, and is sadly missed.
Pint is for Doug if he reads this, and the machine's design team for doing it :-)
Cracking explanation - someone forward this as a lesson to the ubiquitous Mr Robert Peston.
Thanks God that I don't have anything to do with politics (Even the office sort!).
I have to agree with EddieD above - I've been cautious and lived within my means ("If you can't pay cash, you can't afford it!") and am peeved that I will now be suffering because of someone else playing fast and loose with the bookkeeping. Sort of makes Enron's accountants look employable again..
Biting the hand that feeds IT © 1998–2019