Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I'm planning to create a custom system for comments. I was wondering about comment moderation. For approving comments, is it as simple as just creating a field called "Moderated" in MySQL?
What's a good suggestion for countering spam? Akismat?
If you design your columns to have a status column, so only approved comments are displayed, then you could use a DATETIME column called approved date:
COMMENTS table
comment_id, INT, primary key
comment_detail, VARCHAR
approved_date, DATETIME, NULL
This way, you know it was approved and when. But it also relies on staff to approve things before they are visible. It's unclear if there are other statuses involved in your proposed comment system - if there are, it might require a COMMENT_STATUS_CODE table.
You could use a bit field called Moderated which has 0 for unmoderated and 1 for moderated. Then, from your app, simply query those comments which have Moderated = 1. There are various ways of countering spam, which also depends on how you're moderating comments. If you're manually reading each comment before they appear on the site, then spam wouldn't really get through to the site itself, but it could still get to your inbox. You could use a Captcha program such as ReCaptcha. This will make it trickier to submit multiple comments with a bot.
It's highly depend on your site traffic.
Yep, a 'moderated' flag would enough if your traffic is low now, but later you should look forward for another technics (captcha, spam dbs etc, filter apps).
You can check the comments manually, and thats the best, but later you cant check every comments.
But I dont know anything about your site traffic.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm working on a project and I usually use the person's ID as a primary key to identify the person. But right now I'm working on something much more formal and serious then what I've been working on... (School DB) Is it good practice to use the person's/student's ID card instead of having another field (ID) auto generated/sequence as a PK.
It is a bad idea, for one simple reason: security.
You are better off designing your databases to have internal ids for all entities. The person's id would then be an attribute on the records, rather than a primary key. This allows you, for instance, to encrypt the id (and other sensitive information). If someone gets a hold of a print-out of some data, you don't have to worry that they are seeing personal information.
In the United States, this design is helped by the fact that social security numbers -- the closest thing we have to a national id -- were specifically designed not to be national id numbers. Apart from the issue of fraud, the approximately one billion numbers will run out one day.
I look after a similar student database and we use student ids as PK.
It helps us because students are aware of their IDs and if they have any issues they can come to us and quote their ID for us to resolve the issue. It certainly makes it easier than trudging through a load of John Smiths.
The down side I have found is that we do export data to programs such as excel and alot of the IDs have leading zeros which if you are not careful will be removed.
It is entirely up to you, but in my opinion I would use them.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I want to use an approval workflow to accept or reject additions to my sharepoint site. The caveat is that I don't want any changes that are pending approval to appear. Only changes that have been submitted and approved should be visible to others who open the page.
Is a workflow the best way to go about this? If it is, what do I need to change from the OTB Approval solution to have only approved changes be visible? Or is this a code-only problem that I need to dig deeper to solve?
I'm currently testing this with a Calendar web part, but the solution to this could potentially apply to any other type added to the page.
The way I see it, there are two requirements:
Being able to change your site and have the updates only visible to a select few
(optional) A workflow to handle the process.
So the first requirement could be handled by the SharePoint Publishing Infrastructure. Take a look at the interwebs and see if that would work for you. You could also just require approval for items added to the library where your pages are stored but that doesn't seem as straightforward.
I mentioned your second requirement being optional because it might be overkill depending on your situation. You would want to require approval on the library, then attach a workflow to the library. But if you're in constant contact with the approver(s) otherwise, it might be just as easy to say "he dude, check out the 'About Us' page, if you like it, click the approve button in the toolbar".
Hope that helps. There's probably a bunch of different ways to go about it.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
A solution to get quick exposure:
Since my website just got lunched 3 days, i still have time to change my domain name. I decided to do is:
Pick a domain name with keyword tacked before domain name as of: {Keyword}Brand.com (looks ugly)
Keep it for at least 1 year till my site get fair exposure, just to reach to my competitors.
Move back to Brand.com (Probably). I know i will loose ranks, but it won't be hard to bring it back because the website is already being exposed and used by many.
Question:
Do you believe this is a good temporary solution?
Hence, The keyword is non-English word.
So get everyone to learn your name and then change it and get everyone to learn your new name? Does that sound like a good idea? Why not build a strong foundation and then keep building upon it? Races are marathons, not sprints. Think long term, not short term. If you're actually good at what you do you will eventually outrank your competitors for all of your keywords even without your keywords being in your domain name. If you're not good at what you, then hacks and tricks like this won't help you anyway.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I need help being pointed in the right direction (to the right documentation or tutorial) since I don't know exactly what this programming would be filed under.
Basically, I saw an app that had a section of 'Deals' on food and drinks at stores. You had to use the app to redeem the deal, but you could only use the deal once. It seemed that the table view of deals was being populated by a PList from a server (because it is constantly updated) BUT when you choose a deal and use it, it disappears from the table view (because you claimed it).
Now I was thinking it could be coding using an if else statement declaring integer values (and if they weren't equal to the integer, then the deal wouldn't display) but that can't be the case because if I close out the app and reopen it, the deal still isn't in the list. Am I right in assuming that somehow the PList or database is being updated by the user interaction? Are databases for each user being created when someone downloads the app (or starts it)?
I'm kinda in the dark about it and trying to figure out how they pull this off. I'm not sure if I'm way off base and there is some sort programming that I'm possibly not even aware of. Any thoughts? Thanks!
You should investigate NSFetchedResultsController - it allows to perform a lot of pretty things with your data + database.
Check this tutorial.
Also, take a look at the Apple documentation.
Core data basics strongly required.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I'm working on quite complicated project, in terms of business-logic quantity and quantity of components.
Each developer mostly works on "his own" component. I understand that this isn't very cross-functional, but it is impossible to know every components' details.
Team sostav changes from time to time. So we have situations when one person have to work on "other person's component". And this can be on periodic basement, so you can come back to the issue a month later - in that moments you can ask component business-logic's owner the same questions again and again, because you simply can forget some tiny but important details a month later.
This situation is annoying sometimes.
We have daily stand-up meetings, when person tells about what he has done and going to do.
We have project's wiki F.A.Q. page - we extract the most frequently asked questions.
What do you think about the problem?
And how would you recommend us to solve it?
given the component nature I'd go with:
1.) A framework document specifying the applications purpose, setup, requirements etc.
2.) Module documents for each component in a common format and indexed by name.
Look at the http://docs.python.org for a good example of general docs and http://docs.python.org/modindex.html for a good example of module/component docs
Oh, and daily meetings are generally bad, they take up a lot of time and answers get forgotten. Newcomers or sick people miss the meetings and have to be re-briefed. It's 100x better to write it all down and keep a paper/email trail unless discussion/feedback is required.