github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
[personal profile] github posting in [site community profile] changelog
Branch: refs/heads/develop
Home: https://github.com/dreamwidth/dw-free
Commit: 95ea9eefee2d6f9d0891a0550d581053875ac725
https://github.com/dreamwidth/dw-free/commit/95ea9eefee2d6f9d0891a0550d581053875ac725
Author: Vinothan Darael Shankar <darael@tpchq.org>
Date: 2014-04-20 (Sun, 20 Apr 2014)

Changed paths:
M CONTRIBUTING.md
M htdocs/site/opensource.bml.text

Log Message:
-----------
Remove references to Bugzilla

Replace any such references with references to GitHub, as appropriate.
Leave "dw-bugzilla@" email addresses alone.


Commit: b2d7cf21d8282cb022de05266323ca230af1692c
https://github.com/dreamwidth/dw-free/commit/b2d7cf21d8282cb022de05266323ca230af1692c
Author: Vinothan Darael Shankar [:darael] <darael@tpchq.org>
Date: 2014-04-20 (Sun, 20 Apr 2014)

Changed paths:
M cgi-bin/DW.pm
M cgi-bin/ljlib.pl

Log Message:
-----------
Remove last bugs.dwscoalition.org references

Fixes #663. Both the references here removed were links to further docs
of what had been done, rather than notices about outstanding bugs, in
any case.


Commit: 26e8f4554b3d6695a5769afd46fd3bae403a8bde
https://github.com/dreamwidth/dw-free/commit/26e8f4554b3d6695a5769afd46fd3bae403a8bde
Author: Vinothan Darael Shankar [:darael] <darael@tpchq.org>
Date: 2014-04-20 (Sun, 20 Apr 2014)

Changed paths:
M CONTRIBUTING.md

Log Message:
-----------
Actually fixes #663

Add a temporary explanatory note about the broken link to the CLA, and
what to do about it.


Commit: 4c209b006f3b5e257c70555acfee2056546ba2a8
https://github.com/dreamwidth/dw-free/commit/4c209b006f3b5e257c70555acfee2056546ba2a8
Author: Vinothan Darael Shankar <darael@tpchq.org>
Date: 2014-04-20 (Sun, 20 Apr 2014)

Changed paths:
M htdocs/site/opensource.bml
M htdocs/site/opensource.bml.text

Log Message:
-----------
Change names of updates strings

Avoid later trouble in this way. Simply append "2" in two places, in
each of two files, to fix commit before last.


Commit: d65b4419cfe4b705dc9511800b4bbda80043c8de
https://github.com/dreamwidth/dw-free/commit/d65b4419cfe4b705dc9511800b4bbda80043c8de
Author: Afuna <afuna@users.noreply.github.com>
Date: 2014-04-23 (Wed, 23 Apr 2014)

Changed paths:
M CONTRIBUTING.md
M cgi-bin/DW.pm
M cgi-bin/ljlib.pl
M htdocs/site/opensource.bml
M htdocs/site/opensource.bml.text

Log Message:
-----------
Merge pull request #698 from Darael/bug663-bz-to-ghi

Fix #663 - Bugzilla to GitHub Issues migration


Compare: https://github.com/dreamwidth/dw-free/compare/367b5c1212b1...d65b4419cfe4
github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
[personal profile] github posting in [site community profile] changelog
Branch: refs/heads/develop
Home: https://github.com/dreamwidth/dw-free
Commit: 3a1ea3811bbff5b1c1741f4fdd5c5b4402e88038
https://github.com/dreamwidth/dw-free/commit/3a1ea3811bbff5b1c1741f4fdd5c5b4402e88038
Author: Afuna <fu@dreamwidth.org>
Date: 2014-04-22 (Tue, 22 Apr 2014)

Changed paths:
M cgi-bin/DW/Controller/Community.pm

Log Message:
-----------
Display poster column only when relevant

* in members/new, only show the poster column if the community post
level is "select", instead of always showing (that was left over from
when you could always revoke poster access, even if the post level was
"all")

* in members/edit, always show the poster column if anyone has "posting
access" set on them (this makes it act the same as
unmoderated/moderator columns). This is a bit of an edge case, caused
when someone switches community settings, but their community members
used to have posting access explicitly -- this meant that the members
would still show up on the "edit community members" page, because they
still had an edge connected to the community, but there might not be a
checkbox to uncheck


Commit: 367b5c1212b1c33c8e152adc3bc557c11ed7d274
https://github.com/dreamwidth/dw-free/commit/367b5c1212b1c33c8e152adc3bc557c11ed7d274
Author: Afuna <afuna@users.noreply.github.com>
Date: 2014-04-22 (Tue, 22 Apr 2014)

Changed paths:
M cgi-bin/DW/Controller/Community.pm

Log Message:
-----------
Merge pull request #705 from afuna/handle-poster-column

Display poster column only when relevant


Compare: https://github.com/dreamwidth/dw-free/compare/86d184812691...367b5c1212b1
github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
[personal profile] github posting in [site community profile] changelog
Branch: refs/heads/develop
Home: https://github.com/dreamwidth/dw-free
Commit: 78ba93321e5128c8a36a3121d2109c2944d926ef
https://github.com/dreamwidth/dw-free/commit/78ba93321e5128c8a36a3121d2109c2944d926ef
Author: hotlevel4 <hotlevel4@hotmail.com>
Date: 2014-04-22 (Tue, 22 Apr 2014)

Changed paths:
M cgi-bin/LJ/S2.pm

Log Message:
-----------
(Issue #691) Hide 'track thread' icon from free users

Checks whether a user can track threads before displaying tracking icon.


Commit: 86d1848126919a82ac03ffc13a86be07491efe85
https://github.com/dreamwidth/dw-free/commit/86d1848126919a82ac03ffc13a86be07491efe85
Author: Afuna <afuna@users.noreply.github.com>
Date: 2014-04-22 (Tue, 22 Apr 2014)

Changed paths:
M cgi-bin/LJ/S2.pm

Log Message:
-----------
Merge pull request #703 from hotlevel4/bug691/hideTrackButton

(Issue #691) Hide 'track thread' icon from free users


Compare: https://github.com/dreamwidth/dw-free/compare/30a00166e2e0...86d184812691
github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
[personal profile] github posting in [site community profile] changelog
Branch: refs/heads/develop
Home: https://github.com/dreamwidth/dw-free
Commit: 14387ed718571490fefd8c08b3d7720c1f0a7143
https://github.com/dreamwidth/dw-free/commit/14387ed718571490fefd8c08b3d7720c1f0a7143
Author: hotlevel4 <hotlevel4@hotmail.com>
Date: 2014-04-22 (Tue, 22 Apr 2014)

Changed paths:
M htdocs/inbox/compose.bml

Log Message:
-----------
(Issue #661) Allow People with Siteadmin Priv to PM Uncomfirmed Accounts

Allows somebody to PM an unvalidated account (unconfirmed email address)
if they have the siteadmin:* priv. Fixes #661.


Commit: 30a00166e2e04af7cad4693e92a4627c23acb1cb
https://github.com/dreamwidth/dw-free/commit/30a00166e2e04af7cad4693e92a4627c23acb1cb
Author: Afuna <afuna@users.noreply.github.com>
Date: 2014-04-22 (Tue, 22 Apr 2014)

Changed paths:
M htdocs/inbox/compose.bml

Log Message:
-----------
Merge pull request #704 from hotlevel4/bug661/PMUnverifiedAccounts

(Issue #661) Allow People with Siteadmin Priv to PM Uncomfirmed Accounts


Compare: https://github.com/dreamwidth/dw-free/compare/fc2510fdf4ec...30a00166e2e0
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise posting in [site community profile] dw_dev
It's storytime with mama rahaeli: I think we've got a legacy 'feature' that can be removed, but I'm not 100% sure. Read the background and try to convince me one way or the other.

The situation as it is now: If you try to post to your journal with a time before your most recent entry, you are prevented from doing so.

(The check is in cgi-bin/LJ/Protocol.pm, lines 1323-1327; the error is "You have an entry which was posted at $u->{'newesteventtime'}, but you're trying to post an entry before this. Please check the date and time of both entries. If the other entry is set in the future on purpose, edit that entry to use the \"Don't show on Reading Pages\" option. Otherwise, use the \"Don't show on Reading Pages\" option for this entry instead.")

This check was added in the LJ days (I'm not sure when, because the web gateway to LJ's source is down right now and I can't look up the history, but it was very early in my tenure so I want to say 2002 or so) to prevent a very common problem with people's computer clocks being set wrong. It was a horrible support burden (leading to dozens if not more support requests per day): someone's computer battery would be dying and their clock was set wrong because of it, or their clock would just be set a year or two off. Because entries in personal journals are displayed on the Recent Entries page by the time they're dated, not by the time the server received the post, a post dated 1970-01-01 would disappear completely: the person would post it, it would display on Recent Entries behind every other post they'd ever made, and they wouldn't be able to find it when they loaded their journal to see it so they would assume it hadn't been posted at all.

(This is not a problem in communities: to avoid the problem with having posters from many timezones, communities show all entries ordered by server time, not by user-supplied time.)

The fix definitely helped that problem, but it introduced the opposite problem (someone who posts once with an accidental date of 2038-01-01 then has to do some farting around with the backdating flag) and the whole concept of backdating in general is very hard to explain to people. It also, for us, causes issues with emailed-in posts: when someone emails a post to the site, it's posted with the timestamp in UTC (aka, DW server time), which then causes problems if someone wants to post within the 'window' of their timezone offset. (This is what made me start this post: I emailed in today's stupid kitten pic, which got a timestamp of 2014-04-21 0500 UTC, then I tried to post a second entry at 2014-04-21 0421 EDT and got the error. I've opened an issue for applying timezone offsets to emailed-in posts, but there's still the wider question to address.)

My gut instinct is that this check may have been necessary in 2002 (or whenever) when very few people had self-correcting clocks, but now it's 2014 and I don't think there's a single operating system out there that doesn't ship with the "update from timeservers" checkbox checked. I think the few people who will have disabled that auto-time-correction will be used to things behaving weirdly for them if their clock is hella off, and any potential support burden will be alleviated by the lack of having to support questions like "I posted an entry in 2020 to future-date it and now I can't update without errors".

So, discuss:

1) Do people think we can safely remove the "are you trying to post in the past" check?

2a) If not, should we switch to using system time for the "are you trying to post in the past" check? (IE, go by "time the entry was received by DW" rather than "time the user specifies for their post".)

2b) If yes, which of the two options should we take:

2b1) Eliminate all future-date/past-date checks when updating, but otherwise leave things as-is, so that entries on a personal journal's Recent Entries page are still displayed in the order they're dated, not the order they were posted;

2b2) Eliminate all future-date/past-date checks when updating, and switch to treating personal journals like communities, in which entries are displayed in strict order they're posted regardless of date specified by the user.

(I can make up some examples if people are confused about the distinction.)

I think we should get rid of the check, and we should otherwise leave things as-is (so: yes to 1, and of the two, option 2b1) but I am willing to entertain arguments in any direction. Convince me!

On clients and APIs

Apr. 20th, 2014 01:53 am
darael: Black lines on a white background.  A circle, with twenty-one straight lines connecting seven equally spaced points. (Default)
[personal profile] darael posting in [site community profile] dw_dev
Dreamwidth's APIs are poorly documented (people basically have to work off docs for old versions of LJ's APIs). They're also missing key features, like comment handling for more than backups.

I've been told there have been "some internal conversations about deprecating the XML-RPC API -- keeping it for backwards compatability, but moving to a much more modern second-gen API", but that nobody has had both the time and the inclination to work on designing such a thing.

Well, this is me, volunteering. To that end, I'm looking for input on what exactly such a new API needs to provide, and whether there's a preferred underlying technology to build on (exempli gratia, stick with XML-RPC? Change to SOAP? Use JSON? RESTful or not? et cetera). What I'm getting at here is that I'm entirely happy to take point, as it were, and to make decisions (especially where there's little or no consensus and someone has to make the call), draw up specs, write docs, and so forth, but the result is highly unlikely to be a really useful API unless I get input from more sources than my own experience and looks at the code.

At this stage, therefore, I want everything you, the reader, have to say on the subject. Use cases especially.

Go.

Changelog Digest for Fri, Apr 18

Apr. 18th, 2014 11:27 pm
kareila: "PERL!" (perl)
[personal profile] kareila posting in [community profile] changelog_digest
Sorry I haven't posted an update here recently. The transition from Bugzilla to Github Issues will make things bumpy for a while.

[dw-free]

38ce1f7: Bug 215: Implement v-gifts
Add database table for vgift transactions.
428b6bf: Bug 215: Implement v-gifts
Strip trailing whitespace in DW/VirtualGift.pm.
0adfd1f: Bug 215: Implement v-gifts
DW::VirtualGiftTransaction - methods for working with transaction data.
d922b93: Bug 215: Implement v-gifts
New module DW::Shop::Item::VirtualGift.
9e3a057: Bug 215: Implement v-gifts
New event for delivery notification, LJ::Event::VgiftDelivered.
6e0a656: Bug 215: Implement v-gifts
Add vgift-trans.t for testing transaction methods.
4a66ec9: Bug 215: Implement v-gifts
Add methods related to viewing transactions on profile pages.
b81e166: Bug 215: Implement v-gifts
Requested code style tweaks.
30d6f37: Bug 5041: Include comments search in S2 search module
Add a "with comments" checkbox to print_search_form S2 method.
12bb380: Bug 5041: Include comments search in S2 search module
Style fixes as per review comments.
0e27559: Bug 5041: Include comments search in S2 search module
Put each element of the search form in a separate HTML span.
247eb2b: Bug 5041: Include comments search in S2 search module
CSS added for styles which don't inherit from Tabula Rasa.
9d4acb9: Issue 658: Improve accessibility on landing page for screened comments
Accessibility fix: screened comment link is now more descriptive.
2b02219: Issue 668: Change 'state' to 'states/regions/territories' for all countries when editing profile
Changed widget.location.fn.state.inline to "state/province/territory".
c9c43d2: Bug 5191: sticky posts won't work with slug URLs
Fix sticky_entry method to accept slug URLs as well as ditemids.
ebac26b: Bug 5191: sticky posts won't work with slug URLs
Tweak slug-finding regex to use non-capturing groups.
d6f033e: Issue 667: add ted.com as embed source
Add ted.com to whitelist for embedded videos.
rydra_wong: dreamsheep with spork and "SheepSpork" logo; no, it wouldn't make any more sense if you saw it  (dreamwidth -- sheepspork)
[personal profile] rydra_wong posting in [community profile] metaquotes
[personal profile] minim_calibre had a terrible idea:

Or, why the hell did I decide to put on Acqua di Gio (pour femme)?

HELP, I SMELL LIKE 1995.

WHICH, APPROPRIATELY, WAS A YEAR OF POOR LIFE CHOICES.

I can't even review it. It's... a fruity floral with notes of Weezer.

Layout: Gold leaf

Apr. 15th, 2014 11:08 pm
rosecarmine: (Default)
[personal profile] rosecarmine posting in [site community profile] dreamscapes
Name: Gold leaf
Author: [personal profile] rosecarmine
Image info: Backgroung image from subtlepatterns.com (license), metadata, tag images by p.yusukekamiyamane.com (license)

Layout layer: Info | Source | Syntax Highlighted
Theme layer: Info | Source | Syntax Highlighted | Preview

Hello again. This is my second time posting an entry for my Gold leaf layout so I hope you don't mind seeing it again, but this time I come with its layout layer and theme layer. I started converting the CSS without having any experience working with S2 so I am unsure if I made the layers correctly. That's why I am looking for feedback, corrections and suggestions so I can get it ready for patching.

I have tested it in the latest versions of Firefox, Chrome, Internet Explorer, Opera and Safari at 800 x 600px, 1024 x 768px and 1280 x 1024px resolutions on Window 7. I don't have a mobile though so I can't test it on that.

The layout only supports one column page setup with modules at top and bottom. The topbar is supposed to be short so it wouldn't take up too much of the screen, that's why I limited the number and type of modules that can be placed in it. However, any module can be moved to the bottom.

I didn't know how to properly replace the "Top of page" link with an image so I need some help with that, if possible. It would be better if the user could choose to have it displayed as text or as an image. Also, I added custom bullets to the lists and replaced the metadata labels with icons. Let me know if I did that wrong.

I would like to hear your opinions on this layout so any kind of feedback is greatly appreciated. Thank you very much. Sorry for the bother and please excuse any mistakes I made.

Five for Ciel

Apr. 15th, 2014 08:28 pm
dancing_serpent: (Default)
[personal profile] dancing_serpent posting in [site community profile] dreamscapes
layout: Ciel
author: [personal profile] dancing_serpent

Dried Flowers / Preview
Marble IV / Preview
Quasar / Preview
Rose Garden I / Preview
Rose Garden II / Preview

Trying to get my feet wet again, getting back into things with recycled colours.

Perfume for Tabula Rasa

Apr. 13th, 2014 03:55 pm
carlotta: aritcles of clothing assembled neatly (my lordship is a laughing stock.)
[personal profile] carlotta posting in [community profile] dreamwidthlayouts
Title: Perfume
Credit to: [community profile] demanded
Base style: Tabula Rasa
Type: Layout in CSS
Best resolution: 980x1280+
Tested in: Mozilla Firefox, Internet Explorer 11, Google Chrome
Features: custom comment pages, custom security icons, fixed width
Notes: Modules aside from navigation and custom text have been disabled. Custom icon pages aren't coded.

layout preview image

Temporary live preview at [personal profile] carlotta.

Instructions this way!
Page generated Apr. 24th, 2014 01:32 pm
Powered by Dreamwidth Studios