Thanks to @test_variation, Mokum now has native Dark CSS theme, supported in every browser and device without the need for extensions. Enable it in Settings -> Browser Settings -> CSS Theme -> Dark -> Save settings [via /mokum-support/2116610]. #mokum-releases
Mokum now better supports TODO lists. Your comments in your posts beginning with "[ ]" or "[x]" and other similar syntaxes are now rendered in a special way. You can click on the checkbox and it will edit the comment text appropriately. PSA: don't forget that Mokum supports "For your eyes only" posts which could be a perfect simple todo list.
Posts with newlines were reimplemented: this should fix all of the cases where the last line of such post was not displayed, and "readmore" button was not visible. Please report if you still see such cases, preferrably with screenshot and URL of affected post (if not private). This of course mainly affects small-screen mobile devices.
On July 13th a data leak was discovered and fixed in Mokum. If you happened to visit some rarely-used pages, you could sometimes see the sidebar menu that belonged to one of the users that accessed Mokum in past few seconds. You could not "choose" the user, only those that were online at the same time as you. Private posts were NOT accessible. The following information was accessible: a) private subfeed name and URL (but NOT the contents of any private posts); b) list of groups that the user was subscribed to; c) list of groups that the user was admin of; d) list of invites and subscription requests (but they could not be accepted or rejected). [EDIT: after some deliberation word "vulnerability" was replaced with "data leak").
First mitigation was enabled 40 minutes after discovery. Bug was diagnosed and fixed in 2 hours 20 minutes. Initially this data leak was noticed on API tokens page, but the bug has nothing to do with passwords, API tokens, authentication etc. API tokens were disabled as a precaution, but then re-enabled after it was proven that it was not the cause of data leak.· псы в рапиде
Additionally, the following improvements were rolled out recently: a) no more spurious popups on Android and iOS mobile devices;
We've enabled <script async> feature by default. This should improve page loading speed for bad connections, especially high-latency ones. If your Mokum breaks completely, please report to @support, providing your browser version and device model (you can use some other browser or the magic link http://mokum.place/?js=script). Feature is disabled for Opera Mini because of negative reports. Thank you for testing [/changelog/2041753].
Dear friends, I need your help in testing some change in Mokum that could only be tested in real world. You can help by visiting https://mokum.place/?js=async and using Mokum as usual (staying on the front page). Least intrusive way to check is to click Fav/Unfav on any post — it should just work as normal. There could be two failure modes: a) the page doesn't work — it looks completely normal but controls have no effect, and b) same but the page starts to work few seconds later. I'm especially interested in a) bad or slow connections and b) non-mainstream browsers and devices. Thank you!
Mokum now supports JPEG-2000. Practically speaking that means that more sharing URLs with images are going to be processed without errors.
Groups got a new checkbox: "only admins can post". This allows you to have personal-type groups, like in the old Friendfeed, or official-style groups, like @mokum.
b) React 16.4.0, and some other version upgrades. Nothing should change, but if anything breaks please report.· псы в рапиде 1
c) on touch-based devices there is now a tiny clock button near the post timestamp that shows precise timestamps of post and comments (it was a menu item before but it was deemed too expensive visually). For non-mobile computers you can still use mouse over the post date and comment cloud icon.· псы в рапиде 3
You didn't think you could escape this in Mokum, did you?· псы в рапиде 7
Dear friends, as you may have noticed, Mokum now supports line breaks (e.g., /squadette/1972805). Allow me to explain some details behind the implementation of that feature: а) line breaks are enabled with the flag "options -> Linebreaks". When you're editing the post on desktop, you can press Shift-Enter, and the line breaks will be enabled automatically. When the line breaks are enabled, you can submit form with Ctrl-Enter or with the usual "Post to..." button. If you're on mobile device, you will have to first enable the flag, then you can use "return" button on your screen keyboard to add new line.
б) Posts with line breaks in your feeds have height limit. If the post is longer than 10 lines, it is cut to 7 lines, with "read more" button. "Line" is the visual line of your device. Single post pages are always shown in full.· псы в рапиде 5
в) line breaks work only in posts for now, not in comments. We need to sort out implementation, then we can try to implement this feature for comments.· псы в рапиде 4
г) leading spaces in lines are preserved, because poetry.· псы в рапиде 7
д) the main driving force behind the implementation of this feature is poetry, code snippets and small casual lists. If you need to write a longer text with multiple paragraphs, you are encouraged to use the "first paragraph as post, other paragraphs as comments to that post" pattern; support for this will be soon enhanced a bit. Also, you can use k-texts (https://mokum.place/k) to create longer post with full Markdown markup.· псы в рапиде 9
Calendar view for feed pages (both users and groups) was just released: e.g., https://mokum.place/squadette/calendar (or https://mokum.place/changelog/calendar as an example of group). You can find the link to the calendar view on feeds pages. Calendar includes your primary feed, private subfeed if you have one, "for your eyes only" posts and Friendfeed archive (if you have one imported). Only feeds that you have access to are counted in the calendar.
You can now enable "Allow direct messages from anyone" checkbox on your settings page (https://mokum.place/settings). Also, if your account is private and someone is subscribed to your account, they can also send you direct messages even if you're not subscribed to them.
There is now an experimental burger menu on phones. Currently it's prototype-quality, but more items will be added, and hopefully we'll make it be more usable. Please report if you it gives you any trouble or if you have suggestions.
a) some improvements for burger menu on mobiles: text size, subscription lists, text baseline alignment;
b) comment like on direct message comment decrements number of notifications in sidebar; [reminder: when you like incoming direct message, the counter is also decremented accordingly];· псы в рапиде
Another batch of important on-going fixes was deployed. With luck it should not affect anything for now, but please report if it breaks for you. The ultimate goal is to have some more improvements in visual performance of Mokum.
b) an issue with page going completely blank was fixed;· псы в рапиде 3
c) fixed an issue with bogus confirmation prompt after some edit comment / cancel / edit again sequences.· псы в рапиде 1
e) "Groups" blocks in the sidebar were reimplemented with more popups;· псы в рапиде 2
f) another batch of refactoring changes was deployed;· псы в рапиде
Small improvements in the sidebar: a) if you use subscription lists (https://mokum.place/settings/sublists) they are shown in the right column; b) "Subscription requests" block was reimplemented with more popups on user and group names; c) "Manage > Subscription lists".
The code was temporarily reverted back to few days ago to debug multiple reported issues with random scrolling/"jumping".
#mokum-releases: React 16.0.0. HTML size was drastically reduced (e.g., 287 Kb -> 232 Kb for the reference page). This should also be a bit faster.
#mokum-releases: The Big Frontend Cleanup, phase I. Nothing should change, except for less bytes to download from the server and parse, so things should be a bit faster. Please report here or in @support if anything breaks. Thanks,
#mokum-releases: a) text area resizer was fixed, again;
1 2 3 4 5 6 7 8 9 10