Keep in mind that as a university you are going to have a much larger turnover than a standard organisation, so their strategies may not be suitable for you.
I would suggest that using any combination of First Name and Last Name will give you a pretty large amount of collisions, either with current users, or with past users. Collisions with past users may not seem like a huge problem until you get a ton of new users asking you why their accounts filled up with donkey porn spam on the first day.
Of course you could do something like including their first year in the account, i.e. joe.bloggs.2013@uni.edu. But it's probably just easier to use the username (as long as that is unique of course)
I like the concept, and it's relevant to my line of work so I'll probably be keeping a regular eye on it.
But the layout is pretty awful, the two-uneven-columns approach really doesn't do it for me. It's hard to read, and particular it's hard to read one article summary then just move on to the next. Could it not just use the normal slashdot style single list ?
I would suggest that the "bouncing from router to router" is most likely the cause of your performance issues. TBH where feasible an application server should always be on the same local network as it's database server, particularly when the application server is as database intensive as sharepoint. It's also not uncommon for there to be a dedicated gigabit (or higher) link.
As for the storage model, I'd agree SQL Server (or any other RDBMS I know of) isn't really optimum, it's great for list based data, site config etc, but I suspect it's not the ideal solution for document storage (I don't have hard facts to back that up but I don't think too many will disagree). But at the same time I think it is a step on a standard file system when it comes to the kind of dynamic structures, metadata storage, search/indexing etc. I suspect though that when (if?) WinFS is released Sharepoint will move to some combination of a SQL Server DB with a WinFS file store.
Wow, even for/. there's a lot of people who didn't even read the summary, let alone TFA. And there's a lot of FUD being spread.
What this means is that IP address information might be considered personal data under EU data protection laws. This means that companies/corporations/organisations which log your IP address will have to have a privacy policy in place governing how that information is used.
There are also certain requirements, such as they have to make people's own information available to them if requested, they have to disclose breaches of information to those affected and so on.
It doesn't stop logging IP addresses, it won't stop webservers using client IPs to maintain statefull connections, it won't stop google associating IP addresses with search data, it won't stop wikipedia or forums storing the IP of posters. It just means that organisations doing this need need a privacy policy in place to protect this data (which most of them already have to protect other private data they store).
It's just acknowledging that IP addresses can/may be used, in some cases (the summary points out that they already acknowledge IP addresses are often dynamic), to identify a person and deserves the same level of protection that things like phone numbers and home addresses already have.
"Linux hackers are far better coders then most people who use Visual Studio"
Silly comment tbh. Good coders write good code whatever tools they use, be it Visual Studio, Eclipse, Emacs, VI or anything else, bad coders write bad code whatever tools they use. And in addition to that if you take a good coder who has only ever written VB.Net with VS and sit them in front of a linux box and tell them to write something in C++, Java, Python, Perl etc, they will figure it out. But bad coders will just stick to what they've always done and fling poo at the other side to make themselves feel better.
Isn't the silverlight format open ? While the microsoft implemtation may be closed-source, it should be possible for someone else to simply write a client for it.
He's obviously forgotten that a large chunk of the taxes those corporations pay in Ireland (along with the rest of us taxpayers here) has gone to providing compensation for victims of abuse at the hands of the church.
The point of this is that at the moment Tivo boxes run linux directly on the bare metal. But Tivo want to implement certain policies to control usage of the device, for e.g. they may not want you to be able to send unprotected video over a network link, or they may only want you to be able to send anything to specific authorised devices. These policies are implemented in software. Somebody who wants to bypass these policies can therefore, largely thanks to linux being open, simply modify the linux installation on the tivo box to do whatever they like. To prevent this Tivo have implemented a solution restricting users from modifying the linux software on the device.
The GPL v3 prevents this kind of restriction, (among other things) in short if a device runs Linux the user must be free to modify it. This means that again users can bypass any software policies Tivo decide to implement.
What TFA is suggesting is that linux on a tivo box can be run on a hypervisor. This means that tivo's policies can be implemented within the hypervisor, the hypervisor can be configured to only allow certain types of network connections for example. With linux then running on top of the hypervisor users can change what they like but they will not be able to bypass tivo's policies (untill the inevitable security hole is found in the hypervisor of course).
I actually quite like this solution, while I don't like DRM this does mean it will be easy for users to customise it's OS anyway they see fit, maybe altering the UI or adding small apps or maybe even light games
Are social networks (presumably they mean things like myspace, bebo etc) really the most educational resources on the internet that they could think of ? If so future generations are in serious trouble.
Slashdot Mirror
Keep in mind that as a university you are going to have a much larger turnover than a standard organisation, so their strategies may not be suitable for you. I would suggest that using any combination of First Name and Last Name will give you a pretty large amount of collisions, either with current users, or with past users. Collisions with past users may not seem like a huge problem until you get a ton of new users asking you why their accounts filled up with donkey porn spam on the first day. Of course you could do something like including their first year in the account, i.e. joe.bloggs.2013@uni.edu. But it's probably just easier to use the username (as long as that is unique of course)
I like the concept, and it's relevant to my line of work so I'll probably be keeping a regular eye on it. But the layout is pretty awful, the two-uneven-columns approach really doesn't do it for me. It's hard to read, and particular it's hard to read one article summary then just move on to the next. Could it not just use the normal slashdot style single list ?
I would suggest that the "bouncing from router to router" is most likely the cause of your performance issues. TBH where feasible an application server should always be on the same local network as it's database server, particularly when the application server is as database intensive as sharepoint. It's also not uncommon for there to be a dedicated gigabit (or higher) link. As for the storage model, I'd agree SQL Server (or any other RDBMS I know of) isn't really optimum, it's great for list based data, site config etc, but I suspect it's not the ideal solution for document storage (I don't have hard facts to back that up but I don't think too many will disagree). But at the same time I think it is a step on a standard file system when it comes to the kind of dynamic structures, metadata storage, search/indexing etc. I suspect though that when (if?) WinFS is released Sharepoint will move to some combination of a SQL Server DB with a WinFS file store.
Wow, even for /. there's a lot of people who didn't even read the summary, let alone TFA. And there's a lot of FUD being spread.
What this means is that IP address information might be considered personal data under EU data protection laws. This means that companies/corporations/organisations which log your IP address will have to have a privacy policy in place governing how that information is used.
There are also certain requirements, such as they have to make people's own information available to them if requested, they have to disclose breaches of information to those affected and so on.
It doesn't stop logging IP addresses, it won't stop webservers using client IPs to maintain statefull connections, it won't stop google associating IP addresses with search data, it won't stop wikipedia or forums storing the IP of posters. It just means that organisations doing this need need a privacy policy in place to protect this data (which most of them already have to protect other private data they store).
It's just acknowledging that IP addresses can/may be used, in some cases (the summary points out that they already acknowledge IP addresses are often dynamic), to identify a person and deserves the same level of protection that things like phone numbers and home addresses already have.
"Linux hackers are far better coders then most people who use Visual Studio" Silly comment tbh. Good coders write good code whatever tools they use, be it Visual Studio, Eclipse, Emacs, VI or anything else, bad coders write bad code whatever tools they use. And in addition to that if you take a good coder who has only ever written VB.Net with VS and sit them in front of a linux box and tell them to write something in C++, Java, Python, Perl etc, they will figure it out. But bad coders will just stick to what they've always done and fling poo at the other side to make themselves feel better.
Isn't the silverlight format open ? While the microsoft implemtation may be closed-source, it should be possible for someone else to simply write a client for it.
He's obviously forgotten that a large chunk of the taxes those corporations pay in Ireland (along with the rest of us taxpayers here) has gone to providing compensation for victims of abuse at the hands of the church.
The point of this is that at the moment Tivo boxes run linux directly on the bare metal. But Tivo want to implement certain policies to control usage of the device, for e.g. they may not want you to be able to send unprotected video over a network link, or they may only want you to be able to send anything to specific authorised devices. These policies are implemented in software. Somebody who wants to bypass these policies can therefore, largely thanks to linux being open, simply modify the linux installation on the tivo box to do whatever they like. To prevent this Tivo have implemented a solution restricting users from modifying the linux software on the device. The GPL v3 prevents this kind of restriction, (among other things) in short if a device runs Linux the user must be free to modify it. This means that again users can bypass any software policies Tivo decide to implement. What TFA is suggesting is that linux on a tivo box can be run on a hypervisor. This means that tivo's policies can be implemented within the hypervisor, the hypervisor can be configured to only allow certain types of network connections for example. With linux then running on top of the hypervisor users can change what they like but they will not be able to bypass tivo's policies (untill the inevitable security hole is found in the hypervisor of course). I actually quite like this solution, while I don't like DRM this does mean it will be easy for users to customise it's OS anyway they see fit, maybe altering the UI or adding small apps or maybe even light games
Are social networks (presumably they mean things like myspace, bebo etc) really the most educational resources on the internet that they could think of ? If so future generations are in serious trouble.