*** Post Your IDEAS to IMPROVE the FORUM. ***

[Brynjar]

AFAIK, you can make partial quotes by editing the raw bbcode (via the "[]" button in the top right). At least, this seems to be possible on PC (see below), but maybe it's blocked in whatever editing method you normally use (which seems to be some kind of mobile client)?

Yes, but that either requires the user to either quote the entire dev diary (including images), then cut away the parts you don't want to use. Another alternative is to copy/paste one section at a time, but that does not add the reference to the original post. With the partial quote functionality you can quote each specific section of a post as you read, without having to go to the bottom of the page for each section you want to quote, or having to cut away some sections (including bb code for images). The built in partial quote functionality which could be used with the old dev diary format (and with any normal forum post) therefore had both superior functionality, and it was a lot easier to use (especially on phones where cutting away the correct sections are a lot mlre difficult due to the limited display space). All the possible workarounds are just worse from a user point of view.

 

[Lister23]

Yes, but that either requires the user to either quote the entire dev diary (including images), then cut away the parts you don't want to use. Another alternative is to copy/paste one section at a time, but that does not add the reference to the original post. With the partial quote functionality you can quote each specific section of a post as you read, without having to go to the bottom of the page for each section you want to quote, or having to cut away some sections (including bb code for images). The built in partial quote functionality which could be used with the old dev diary format (and with any normal forum post) therefore had both superior functionality, and it was a lot easier to use (especially on phones where cutting away the correct sections are a lot mlre difficult due to the limited display space). All the possible workarounds are just worse from a user point of view.

You can already do partial quotes. Just highlight the option you want to quote and you will get the option. See screenshoot below:

 

[InvisibleBison]

You can already do partial quotes. Just highlight the option you want to quote and you will get the option. See screenshoot below:

View attachment 992285

That doesn't work on dev diaries, for some reason.

 

[jonjowett]

You can already do partial quotes. Just highlight the option you want to quote and you will get the option. See screenshoot below:

View attachment 992285

I don't think I've ever used that feature before. I tested it on a recent dev diary and I can confirm that this is not supported. You can hit the reply/quote button at the bottom of the dev diary and edit the entire quote, but you can't highlight a small part and immediately quote it.

This is particularly pertinent for dev diaries, because they are likely to be some of the longest posts on the forum, and are likely to cover a large number of different topics, and it's therefore arguably the most likely situation where a user is going to want to follow up on a specific sentence buried in the middle of the post.

Now that the meaning of "partial quote" is clarified, I agree with @Brynjar that it would be good to re-enable the feature for dev diaries.

 

[Lister23]

That doesn't work on dev diaries, for some reason.

I don't think I've ever used that feature before. I tested it on a recent dev diary and I can confirm that this is not supported. You can hit the reply/quote button at the bottom of the dev diary and edit the entire quote, but you can't highlight a small part and immediately quote it.

This is particularly pertinent for dev diaries, because they are likely to be some of the longest posts on the forum, and are likely to cover a large number of different topics, and it's therefore arguably the most likely situation where a user is going to want to follow up on a specific sentence buried in the middle of the post.

Now that the meaning of "partial quote" is clarified, I agree with @Brynjar that it would be good to re-enable the feature for dev diaries.

Ah, sorry. I think one of you had already mentioned this in a previous post. I should have read them more carefully before publishing mine.

 

[Panzerslothen]

I am once again asking for the ability to block users outright.

Ignoring them is helpful, but a block function would be preferable.

 

[Phibs]

How would that even work?

 

[Mder1]

How would that even work?

 

[Phibs]

Zensursula to the rescue ^^

 

[Wagonlitz]

How would that even work?

Poorly, would be my guess.
Like, imagine if you block the OP of a megathread. Then you can't read the OP, end up violating the rules in the first post that the title orders you to read, and get yourself banned.

Or less extreme then it can lead to threads either not showing up or you being unable to see the OP.

Also, I presume that given they ask for a block when ignore exists that means they want the blocked user to be unable to read their posts too, like on Twitter.


Which means that if the OP of a megsthread blocks you then jf you want to discuss that issue you'd be forced to keep opening new threads and ask mods to merge them with the megathread once the topic you're discussing is over.
Or, if the OP of say the UK Politics Thread blocks one of the regulars then you'll essentially have two, concurrent UK politics as a result, or the first just gets retired.


In all cases, absolute mayhem.


And you'd be unable to see if somebody had made a thread about what you want to discuss, if they've blocked you, so you'll make a duplicate.
And if the dupe is merged with the original you can't see it anymore as OP blocked you, so you're forced to make a dupe...

Again, absolute mayhem.

Perhaps there's ways to do it to avoid mayhem, but I don't really see how you'd do it.
Even just hiding non OP posts the person who blocked you made can cause mayhem too, as it can lead to multiple people repeatedly posting the exact same stuff when new stuff happens, leading to lots of thread bloat.