> > The single like break issue is because of Markdown. When he has finished implementing the BBCode parser, Markdown will be removed. Thus, your single line breaks will be restored. > > > > So again, perhaps you can survive with double line breaks while he finishes implementing? > > > > EDIT: with a bit of googling, it turns out that you can use single line breaks by adding two spaces to the end of the line, then moving to the new line. > > > > Example: > > New line! > > > > [Source](http://meta.stackexchange.com/questions/26011/should-the-markdown-renderer-treat-a-single-line-break-as-br) > > Oh > This is a great find! > Ty so much > > --- > > I think I can fare without buttons for awhile. As long as it's for the editor being fixed! :D Going to second this. Will certainly make the wait for a better text editor easier to carry through.

Hey Mahz, I'm wondering if you've licensed your Guild code? Or is it just All Rights Reserved copyrighted to Mahz?

> Hey Mahz, I'm wondering if you've licensed your Guild code? Or is it just All Rights Reserved copyrighted to Mahz? Thanks, added AGPLv3 license: <https://github.com/danneu/guild/blob/master/LICENSE.txt> Update: I've essentially kept everything the same (I like this bare-bones editor) but replaced Markdown with BBCode. So far in my testing, the BBCode parser is compatible with QQCode (so I will make old posts editable again) except for these cases. QQCode allows this short-hand: [img=example.com/flower.png] [url=example.com] BBCode convention is: [img]example.com/flower.png[/img] [url]example.com[/url] or [url=example.com]Click Me[/url] Right now I'm working on the logic for the transition to BBCode from the user POV. Once I push the change, when you edit a post, it's going to dump into the editor either Markdown or QQCode for you to modify. When you save the post, it inserts into a new BBCode column. By making the Markdown/QQCode read-only, I'll be able to avoid the nightmare case of losing data in the event of a glitch.

Random idea here, but what's the chance of a search bar at some point?

> Random idea here, but what's the chance of a search bar at some point? The new database has first-class support for fulltext search: <http://www.postgresql.org/docs/9.4/static/textsearch.html> The implementation will probably take a week + weekend (I don't get to work on the Guild every day). Once BBCode is finished, the next things on my plate (off the top of my head) are: - notifications (big feature, partially coded already) - being able to archive/delete private convos (medium feature) - search (big feature) Of course, these are always interleaved with random patches and smaller issues (I don't know why every line in this post has parentheses).

That's super great Oh btw who are the people that are helpin you with the site? Do you have like a Code Crew

> That's super great > > Oh btw who are the people that are helpin you with the site? Do you have like a Code Crew - [TheMaster99](http://www.roleplayerguild.com/users/12164) has been learning the code and started fielding some issues with patches. - I've had two anonymous patches submitted to me by email. One of them was a surprisingly advanced patch, so I'm not sure why they patched by email instead of through the code repository. I'd like to give credit. - Also had someone register on Github just to submit an anonymous patch to fix a link: <https://github.com/danneu/guild/pull/8/files>. I'd also like to know who that was. Honestly it's a lot more than I expected at this stage, and it's heartwarming ^_^. The code at the beginning is pretty unorganized since it's just me trying to belt stuff out. I'd like to refactor the project "README" file with a better quickstart for interested contributors. Someone actually requested that earlier in this topic. I'd also like to explain how to make trivial changes to files for non-developers. For example, if you wanted to change some text on the "Edit User" page: - You can go here: <https://github.com/danneu/guild/blob/master/views/edit_user.html> (All html templates are in the "views" folder) - Click the pencil icon on top  - Make the edit right there in the browser - And then click "Submit" Unless I'm missing a step, that should create a patch ("Pull Request") that I then can merge into the project without any effort.

> > Hey Mahz, I'm wondering if you've licensed your Guild code? Or is it just All Rights Reserved copyrighted to Mahz? > > Thanks, added AGPLv3 license: <https://github.com/danneu/guild/blob/master/LICENSE.txt> Thanks for adding the license. Can't say I care for the terms, but at least its open source and modifiable/distributable.

> > > Hey Mahz, I'm wondering if you've licensed your Guild code? Or is it just All Rights Reserved copyrighted to Mahz? > > > > Thanks, added AGPLv3 license: <https://github.com/danneu/guild/blob/master/LICENSE.txt> > > Thanks for adding the license. Can't say I care for the terms, but at least its open source and modifiable/distributable. Relicensed: <https://github.com/danneu/guild/blob/master/LICENSE.txt> ;)

Just have to say, I've been extremely impressed with the development you've done this past month, Mahz. All the hard work you're doing for this community fills me with warm fuzzies and has really strengthened my trust in you and the stability of the guild. Thanks so much! Shorty, you da best. And, ahhh, notification system!!! Yes! I'm so ready to stop obsessively checking my subscriptions for new posts.

> Investigate missing self-convos like Fallenreaper's. Mahz, I don't know if you fixed this, but I can find my self convos just fine.

> > > > Hey Mahz, I'm wondering if you've licensed your Guild code? Or is it just All Rights Reserved copyrighted to Mahz? > > > > > > Thanks, added AGPLv3 license: <https://github.com/danneu/guild/blob/master/LICENSE.txt> > > > > Thanks for adding the license. Can't say I care for the terms, but at least its open source and modifiable/distributable. > > Relicensed: <https://github.com/danneu/guild/blob/master/LICENSE.txt> ;) Oh, that's a nice, happy license. Awesome, Mahz! :D

> Just have to say, I've been extremely impressed with the development you've done this past month, Mahz. All the hard work you're doing for this community fills me with warm fuzzies and has really strengthened my trust in you and the stability of the guild. > > Thanks so much! Shorty, you da best. > > And, ahhh, notification system!!! Yes! I'm so ready to stop obsessively checking my subscriptions for new posts. Thanks. What stung so much last year was that the Guild was suffering catastrophic scaling issues while I was AWOL. Performance is now my #1 concern next to data retention (I still sob when I think about the data loss of December 2013). The notification sytem will start out pretty basic. But it will at least let me migrate from showing total PM count to just showing unread PM count. I'm also keeping it generalized so that I can eventually support notifications for things like: - Mentions. Maybe something like `[@]El Taco Taco[/@]` and when you're quoted in a topic. - New posts in subscribed topics. > > Investigate missing self-convos like Fallenreaper's. > > Mahz, I don't know if you fixed this, but I can find my self convos just fine. Thanks for mentioning. I can see all of my personal convos as well, so it must be a more local issue. Off the top of my head, maybe Fallenreaper's PMs were tagged by the old system's spammer countermeasures. I'm still looking into it, though. Sorry to Fallenreaper for the delay. > Uhh... The rest of the formatting can wait, but single line breaks? Please? I have IC posts to write... Sorry about that, Shienvien. Hopefully the workaround is good enough for now. I made sure the new parser is liberal about honoring line-breaks.

Hello Mahz, I`ve been seeing this problem every time I use a certain symbol in my posts and I don`t understand why it`s happening. 

> The notification sytem will start out pretty basic. But it will at least let me migrate from showing total PM count to just showing unread PM count. I'm also keeping it generalized so that I can eventually support notifications for things like: > > - Mentions. Maybe something like `[@]El Taco Taco[/@]` and when you're quoted in a topic. > - New posts in subscribed topics. How do you plan to do unread notifications in threads? For example, my favorite forum software (SMF) has a topic log in its database with the member id, topic/thread id and the id of the last message id viewed (which I believe is an AJAX call for browsers with JS enabled, and a message included with POST when users access a new topic page for disabled JS browsers like WAP or Lynx). That makes it simple (relatively so) to handle indicators of new posts by comparing the topic's latest message id with the topic log.

> Hello Mahz, I`ve been seeing this problem every time I use a certain symbol in my posts and I don`t understand why it`s happening. > >  The grave (`) symbol is for inline code. Switch to apostrophes (') to avoid.

> > Hello Mahz, I`ve been seeing this problem every time I use a certain symbol in my posts and I don`t understand why it`s happening. > > > >  > > The grave (`) symbol is for inline code. Switch to apostrophes (') to avoid. Alright, I`ll try, thank you.

^ How on Earth is it that you've been using grave accents instead of apostrophes this entire time? What's your keyboard layout? Also: you're still doing it, so you're still going to be having problems with it in the future whenever you use more than one attempted apostrophe in a post.

@The Nexerus: People have different habits. I myself tend to use asterisks quite liberally in OoC context (and no, I don't use those as I would italicization). Also underscores in filenames and such, a habit from a time when spaces could not be used in there, and from writing function names in programming (personal preference compared to thisStyleOfNaming)... In other contexts, the accents can also be a handy way to bypass breaking a code, since apostrophes are quite frequently (perhaps even more frequently than the accents) used as functional characters. (Layout-wise, for me both are equally accessible - accents are right next to backspace and the apostrophe sits next to enter key.)

@The Nexerus: I would say my keyboard is a normal layout. @Shienvien: I agree, it's a habit I have that I never found as anything until now. I type that way because I've always typed that way since I learned how too. It won't be easy to break that habit now that this has come to my attention.