Submodule file contains duplicates with different cases. This makes it impossible to check out the repo on Unix.

Right now the homestream is just a series of posts in reverse-chronological order. Users should be able to define what appears here - eg, blog posts, photos, or some combination of items. Also see the ideas in #55.

should I be able to request arbitrary .php files under Idno*, external or templates?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

... it ain't going away any time soon, so perhaps a nod to backwards compatibility would be good.

It's a silly thing to do. Quit it.

Content plugin titles are all currently in the singular.

That makes sense for the "add some content" buttons, but less sense for the "Content" dropdown or page titles. Is the right way to fix it to add another string to each plugin?

Add some links to your profile, then upload a profile icon.

Gone!

... so that they can be styled accordingly

Default landing page lists messages which are a reply by default, this makes it a little hard to follow. It's be nice to have an option to hide the thread by default.

I've made some progress towards this on my fork, but suffering from lack of resources. Happy to have anyone interested in this help out :)

https://github.com/mapkyca/idno/tree/couchdb

When, eg, someone comments on one of my entities, I want to see notifications. These can also be piped to third party software like Firefox, and sent via email.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Right now single-user mode involves a custom plugin that makes the homescreen look like a profile page. It would be better if idno could have a single-user mode that would actually make the homepage be the user's profile URL.

... yeah. :/

FF & Chrome, Ubuntu 12.04

UUIDs shouldn't be http(s)://example.com/yawn/care/whatever they should be //example.com/yawn/care/whatever

Discuss.

For the mobile viewport, let look into moving the sign-in link up in the navigation so that it sits above the content nav link.

• Better documentation
• A warning if you install idno on a non-https URL
• Links to cert providers
• Integration with ISPs?

Ideas welcome!

It depends on leaflet and stamen maps being served over http. stamen maps don't appear to have an ssl option :(

... so plugins can hook in and provide security auditing.

Switch the Status Update to a text box rather than single text line. Even a Twitter-length update can run longer than the space visible in the text field, and it's difficult to view what you've written.

Instead of hard coding HTTP:// in base url, just use //

ATM you can't bounce to HTTPS as modern browsers won't fetch CSS and JS from non HTTPS locations for security.

For the checkin plugin, update "save" button language to something more specific to the plugin, like "checkin."

Include a plugin for App.net similar to Twitter, Facebook, et al.

Create a plugin for pump.io

Right now, to "git co" a plugin into IdnoPlugins, I need to check it out elsewhere and ln -s it to get the "right" directory into the IdnoPlugins directory. If the content of the plugins were lifted up one level, the deploy-from-git process would be a lot easier.

URLs are an interface too. Hide the hashed URLs and provide simple, human-friendly permalinks as a service to all plugins.

Provide an option to select or deselect which networks an update will be pushed to. This should be enabled for any of the plugins that push to a network: status update, checkin, picture, etc. Simple checkbox for each at the bottom of the update could work. We could also explore fancier interface options with buttons, images, etc instead of a basic checkbox.

I will try to work on this one. I want to make a really basic plugin for recipes with h-recipe. It would probably have a title, a list of ingredients, and a text space for instructions. It might also have the option to include a picture, but that's probably beyond me.

I post, person B replies on his blog and webmention appears on mine. I reply to it on mine and webmention hits B.

These should be threaded, rather than appearing in the main SoC.

All static Javascript, CSS and image files should live in their own directory structure, which should be configurable to live at a user-definable path.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Need to patch ToroPHP to be able to return an instance of the page handler class that would handle a given URL, so that we can choose an alternative method to call.

eg, for webmentions, need to get a page handler object as $pagehandler and call a function of the form $pagehandler->webmention($source).

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Looks like an incorrect mime type being returned. Possibly to do with it being a virtual file.

Occurs in firefox and chrome. Hitting refresh returns correct image.

Actually has a crack at this, but there is something in the main template that prevents any of the lightbox/fancybox/bootstrap-lightbox code from functioning.

Very annoying.

So perhaps the title of this issue should be "Something about Idno's loaded libraries stuffs up modal dialogs"

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Direct comments to a post, merging transparently with webmention.

For status updates, add a character count similar to what you might see for Buffer. Might be nice if it turns red after 140 but lets you keep typing. That way if you're sharing to Twitter, you'll know when you've passed 140 and can stop or continue knowing it will include a link. Similarly, if you're sharing to App.net you can note when you've hit their limit as well.

At the very least login and signup should be forced over HTTPS.

I'm sure it's on the roadmap, but an IO api would be handy.

It'd be super cool if, when pushing a post to another service (FB, twitter, etc), we could pull comments on those platforms out and display them with the post.

Of course, this may be impossible and/or impractical...

Just lodging this as a placeholder for a future wishlist.

Some posts I'd like to go to FB but not twitter. It'd be nice to have a tickbox of options similar to bufferapp.

Include a plugin for App.net similar to Twitter, Facebook, et al.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Post later and/or a feature like buffer,

Did you help close this issue? Go claim the $10 bounty on Bountysource.

Probably piggy backing off #62, but turns out the no 1 asked for feature in corporate deployment is email interaction, so that's:

• Comments and post notifications via email (#7)
• Reply to address on those
• Post new entry via email (with attachments handled sensibly).

Have this in your mind when building out #7

Doesn't boot on a Unix box because many of your includes are referencing things without the proper / inconsistent case.

Idno when you mean idno, Symfony when you mean symfony etc... Also check the case in your .gitmodules.