Bitcoin Forum
October 19, 2018, 12:42:00 PM *
News: Make sure you are not using versions of Bitcoin Core other than 0.17.0 [Torrent], 0.16.3, 0.15.2, or 0.14.3. More info.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: [Feature Request] Ability to add Editors to Coin Announcement 1st Posts  (Read 64 times)
togoshigekata
Full Member
***
Offline Offline

Activity: 434
Merit: 113


BiblePay.org


View Profile WWW
September 04, 2018, 09:20:26 AM
 #1

In need of a way to be able to allow others to update Coin Announcement Posts
without the original account having to share full access

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
cabalism13
Member
**
Offline Offline

Activity: 294
Merit: 55

•○●Rence-Ann●○•


View Profile
September 05, 2018, 04:57:50 AM
 #2

In need of a way to be able to allow others to update Coin Announcement Posts
without the original account having to share full access

It can only lead into having a false information regarding the coin. If the ANN isn't updated anymore then members just have to go into their official website.

Initscri
Hero Member
*****
Offline Offline

Activity: 812
Merit: 559


OneHash.com - Mutual Betting & Casino


View Profile WWW
September 05, 2018, 05:16:52 AM
 #3

In need of a way to be able to allow others to update Coin Announcement Posts
without the original account having to share full access

I like the idea of allowing multiple users to edit a post. For example, a organization team member may create the original post, but allow other team members accounts to update the post as they see fit going forward.

As such, a topic is owned by one user, but the user then permits edits by a certain list of users.

Only concern: This needs to be kept simple. With anything overly complicated/requiring weird access rules, the owners of the thread should probably just create a Wiki & link to it.

Strufmbae
Member
**
Offline Offline

Activity: 168
Merit: 18

Hire me as your assistant with low pay


View Profile
September 08, 2018, 12:34:34 PM
 #4

Multiple users who can edit a certain thread is kinda difficult to trace and to send a negative trust, it is better to only have one original poster,  why not just the management,staffs, and developers just request to the maker of the thread to add some feature when they have other ideas.

[
SFR10
Legendary
*
Offline Offline

Activity: 1232
Merit: 1156


SFR DESIGNS - http://bit.ly/2ClWYOh


View Profile WWW
September 08, 2018, 05:07:27 PM
 #5

That's a useful request but I can argue on both sides:
- Having such ability, increases the chances of having announcement threads hijacked by hackers (ex. read this thread).

Simple solution:
- Create/use official public accounts for "OP".

togoshigekata
Full Member
***
Offline Offline

Activity: 434
Merit: 113


BiblePay.org


View Profile WWW
October 05, 2018, 10:45:29 PM
 #6

Yeah Ideally to combat this issue, you set up a shared account beforehand to use as the ANN OP (Original Post),

We are in the boat where the Lead Developer has made the post and uses the account as his main account,
so he does not want to share his password, but he is open to sharing the ANN OP.

The Lead Developer gets really busy at times, and updating the ANN documentation can tend to be a lot lower on his priority list

Initscri
Hero Member
*****
Offline Offline

Activity: 812
Merit: 559


OneHash.com - Mutual Betting & Casino


View Profile WWW
October 05, 2018, 10:47:10 PM
 #7

Yeah Ideally to combat this issue, you set up a shared account beforehand to use as the ANN OP (Original Post),

We are in the boat where the Lead Developer has made the post and uses the account as his main account,
so he does not want to share his password, but he is open to sharing the ANN OP.

Would be helpful in that situation to be able to transfer ownership of a specific thread.

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!