Implement Open Graph Protocol in my web application - facebook-opengraph

I am interested to implement Facebook way of link sharing feature in my web application. In FB when we paste a link it shows the content of link as thumbnail,few text etc.
How can I do that?
I know its Open Graph Protocol but how to implement it in my web application(based on spring MVC)?
What are the technology needed for this? I am a java,jquery guy.
Is it necessary to use facebook for this?

Open Graph isn't a library or a script you can use to build an application that is capable of doing what you want. Open Graph is a Protocol that follows a set of rules that provide a convinient scheme of building social applications.
By doing so, it's made sure that there is a standarized way to work with that data.
So the short answer: OG does not provide such a functionality, you have to build it by yourself (though there are pretty good links and scripts that make your life much easier: http://ogp.me/ scroll to the very bottom). Instead by using OG, you make sure that every application that works with OG (facebook and google to name a few examples) can work with your data properly.
It might not be the answer you searched for, but I think it should give you a little information on what OG really is.

Related

How can I pull User IDs from Adobe Analytics for users who match a segment?

I'm trying to lift all the User IDs that match a segment in Adobe Analytics and store them somewhere (anywhere really), so I can then feed them into an action system for targeting.
Documentation seems hard to find - anyone have ideas on how I could achieve this?
Not sure if there's APIs or SDKs that let me pull this data, or pre-built connectors into something like Google Sheets, but again documentation seems light at best.
The simplest tool to use would likely be the Report Builder. It's an Excel extension by Adobe to export the data. It's pretty powerful. Can do pretty much everything AA can.
You could also generate data feeds and ETL the data from there to wherever you need it. It's a bit more advanced though.
Finally, you have the customer journey API, which would now be an even more advanced level of ETL.
Otherwise, yes, Adobe is notorious for how bad their documentation is and how hard it is to find it. It's almost like they don't want the good documentation to be there in order to sell more of their certification courses.
Note that sometimes when you google something and get to their forum to see the answer, Adobe will attempt to hide the answer behind the authentication wall. Just open that link in incognito and you'll be good. Adobe is pretty weird.

Realtime Web Based Rich Text Editor

Does anybody know of a web based Rich Text Editor like TinyMCE or FCKEditor which supports realtime collaboration? I know of systems like EtherPad, but I'm interested in finding something I can embed into another application, rather than something that works standalone.
Ideally something open source, and works on the .NET platform would be great.
Cheers
Matt
There are
beweevee, using .NET, but it is not open source.
collabedit
While there are several all in one solutions they often tend to be a bit lacking in features. I believe this to be because building a great editor and a great collaboration infrastructure are both very difficult and require different skill sets. It's very hard to do both very well. On the other hand if you find one that meets your needs it might be the simplest approach. ProseMirror comes to mind as a good example that does it pretty well.
I prefer to take a great editor with a great API and pair it up with some real time collaboration technology. Currently Quill and CKEditor 5 are great editors that have sufficient API's to enable real time collaboration. Both of them were built with collaboration in mind. You can pair them up with a realtime back end like the Google Drive Realtime API by Google or Convergence offered by Convergence Labs (full disclosure, I am a founder at Convergence Labs). Or if you are looking for an open source alternative you can look at Together JS or ShareDB.
For a fully javascript based solution try etherpad!
There is a .NET Client example on HTTP API and a page on other examples
Also refer this jQuery demo that can be embedded into your existing solution on the .NET Platform

Best practice to implement back functionality in flex

I'm not using deep linking, so all the pages/states appear as http://site.com
Is it still possible to implement back functionality in this case? It looks like flex has a browser history feature, but not sure if it would still work given that all the pages are at site.com
The other option is that I would save information in the main file itself so I can go to the last page and retrieve whatever data was on it.
Anyone can advise what's generally the best practice way to handle back functionality?
Unfortunately I don't know of any other way to implement browser history (ie, back/forward) without using deep linking (eg, example.com/#foo). This is how the Flex browser history components implement it.
However, one thing you could do, if you need to keep the URL static, is stick your Flex application in a frame. That way the outter frame would still show example.com while the inner frame is at, for example, example.com/#widget=42.
Check out the Flex docs on Deep Linking and the Browser Manager.
The best practice and generally the only way to do it is to use deep linking.
it's best because the users can add a section of your application to "Favorites" and that's an important feature to have IMHO.
Do you need to keep your website with just http:// site.com or is that just how it looks now because deep linking is not implemented?
Checkout Angela's Accessible Rich Internet Application tutorial which gives instructions on how to quickly and easily set up deep linking using UrlKit. The added bonus of this site is that the tutorial is delivered in the environment described... IE: you can view the source for an "in production" example of the implementation.

dashcode and external rss feeds

I was wonder if anyone can help me with this. I've been looking everywhere for this information, but I want to make a web application using dascode rss. I know that you can't link external sources. Does anyone know a way I can get around it. From what I understand a little php can get around this, but I'm unsure where to look.
OK, first thing no PHP. Dashcode is limited to HTML, CSS and JavaScript. Although having said that there are a whole range of system calls that cna be made using the functionality provided by various parts of the x-cde system.
Second yes you can link to external sources such as other web sites, api on say Twitter, google etc. RSS feeds and so on, not sure where you got the idea to the contrary.
If you want to learn how to do a Dashcode RSS then open up Dashcode, start a new project, either web based or Dsashboard based and choose the RSS project. This will give you an out of the box template to add you own information and then see how it works. Then customise it.
In the above i am assuming Snow Leopard and the latest Dashcode/X-code but it will still gove you most of what you want on earlier version.

How (or should) I create my own wiki capabilities?

I have an ASP.NET website and over time it has become more and more of a data repository where I have numerous database tables and the site just ships out this data.
I am realizing that a wiki might actually start to be a better model for what my website is turning into. Or at least parts of it as it's really just adding and updating content that I am doing. Here is my dilema:
There are certain parts of the site that do need to be non-wiki and fully customizable, etc. Should I go and build my own wiki capapabilities into my website so I can make it part wiki (embedded when I need it) and the rest regular ASP.NET? If the answer if yes, are there any tips or boiler plate code on how to build and host a wiki?
The alternative is to use existing wiki software. I have tried most of them and my issue is that I need to host it myself on Windows and as mentioned above I want to have complete control and have just a simple wiki page editable inside my site. I have tried using frames, etc. to simulate this, but it all seems kind of hacky.
Any advice on:
A. If you think I should build the wiki part of my site below, is there best practice, boiler plate code on how to do this quickly?
B. If you think I shouldn't go reinvent the wheel, is there any existing Windows-hosted software that I can embed in my site without losing any control?
Rolling your own is a waste of time unless you have some major change or addition to the functionality of a wiki not otherwise available in existing systems (and even then, it's often a waste of time to start over than to branch an existing setup).
I recommend using something like ScrewTurn, which is open-source and ASP.NET, which gives you a fully-functioning wiki with no development, as well as gives you as much control as necessary if you do need to make changes.
I would agree with Rex M. You don't need to start from scratch. Leverage an open source product that is already available and build on it (if you even need too).
The added benefit of that is from a collaborative perspective when you build some interesting functionality into your version of the software and then share that back with the community.
Chances are if you need to build something and find it useful that other folks somewhere have close to the same needs and would welcome your features and enhancements.
That's the beauty of open source.
Take a look at dooWikis. With this, you can embed wikis into your site like you want to, without redirecting to a third-party service, and restrict who gets to make edits.

Resources