GUEST COMMENTS [Feature Discussion]

[jarvie-dev]

Many APPS are working on the same issues and feature sets... this is one of them.

In this community we will be discussing the following.

1. What different Apps are doing in regards to the topic.
2. If there are ways to help each other save time or effort
3. How to support other apps regarding this TOPIC using our own apps.
4. If this topic should be
   A. Decision for a simple protocol/standard that will help
   B. Candidate for a more in depth RFC
   C. More just as a topic for group discussion

Having started this post @jarvie will be responsible for editing the comment itself
These are some of the items we discussed at SteemFest4 in bangkok
Please start threads regarding this topic in the comment section

Comments

[martibis]

At Haveyoubeenhere we have the centralized platform, where in a way you could say everyone is a guest, we currently don't mix comments from the centralized platform with those crossposted to the Steem-blockchain.

One of the immediate challenges I can see pop-up in my case is that not every user will exist on both Steem and Haveyoubeenhere so @username would be strange if the user exists on Steem but not on Haveyoubeenhere.

[grampo]

Maybe we can start with something small.

We need proper author attribution for guest posts and comments. If we all can use a similar set of .json data fields then guests posts can be properly displayed in other apps as well.

Note: sometimes we can use bots not for just guests, but even for existing Steem users (ex. object updates on Waivio are posted by bots in order not to clutter user profiles, comment feeds and to save user's RC).

• flag: guest or Steem user
• username to show (guests names can have duplicates on Steem, so they should be marked: "username (guest)");
• profile URL (for guest users);
• icon URL (for guest users).

Did I miss anything?

[jarvie]

I like the idea of putting a metadata field into the comment for profile URL that makes sense.

What would ours be @asgarth and is that something we're considering?

[asgarth]

Why do we need a profile url? Just clicking the guest username will bring you to the correct page.

[grampo]

Basically, we need it for guest accounts. Other apps may not index your guest posts accurately. Plus you may have some additional public information about this guest user, which my app would not be able to display.

[asgarth]

If you check how the guest accounts are created on steempeak you'll see that everything is already there ;)

[grampo]

I am sure. So is 3speak, Haveyoubeenhere, Waivio and others. We just need to decide to support one of these, so that we can show proper guest attribution even if it was not our guest account.

If you post you .json specs here first and they are flexible enough to support key scenarios, we might as well just use them. More work for us and less for you ;-)

[jarvie]

The SteemPeak.com method about to roll out will be:

1. guest user will write comment
2. and then our proxy account peak.proxy.1 etc will post the comment to the blockchain for the guest
3. End of comment will have some commentary saying which guest wrote the post
4. I assume we'll also have the metadata field on the comment be author=guest.account
5. One of the key things we did with guest accounts was make sure they were ALL longer than 16 characters so that they never conflict with steem accounts.

When talking with a few apps like 3speak one idea we had was to recognize the Proxy type comments and which accounts do them and then take a look at the author metadata field. Or whatever becomes the standard.

[cadawg]

That's the approach I'm thinking of (the footer + meta) -> https://steempeak.com/testingnewversion-1/@guestbusters/hello-world-my-first-post1575213270718

[jarvie]

For those who want to see what that post looks like

[jarvie]

@theycallmedan @starkerz let's hear how your guest comment system works and how we can work together to show eachothers guest comments.

Does anyone else have a system to share?
Or maybe does anyone have a really great protocol idea for supporting eachother's systems?

cc @lukestokes @roadscape @eonwarped

[grampo]

This standard should allow proxy services for Steem accounts as well.

For example, on Waivio, updates to wiki-objects on Steem blockchain are posted on behalf of Steem users by bots (does not require users to have a lot of RC credits, does not clutter comments feed for users with technical posts, prevents users from editing updates after other users accepted/rejected them, etc.)

[jarvie]

GUEST ACCOUNT STANDARDS?

I think the guest account has to be

1. Longer than 16 characters (To never be confused with a steem account)
2. Has to do something only that app would do. Like prefix or suffix or something particularly unique.
3. Needs to put it into the comment/post metadata (and we should agree how that shows up... something as easy as "guest_account": "peakguest.0000001"
4. Someone suggested the post can also have a URL to where the guest profile can be found.
5. We need to know the accounts that we can trust and only look at the metadata of those fields created by those accounts ... for example ours will be peak.proxy.1 etc.

This is until there is a system for actual guest accounts

[cadawg]

1. Supported by @guestaccounts - Additional Constraints? :
   1. Starts and ends with a letter or number
   2. Only contains letters, numbers, - and .
2. Agreed, Something Like ga (@GuestAccounts) and ca (or first 2 app name letters) for GuestAccounts
3. Yup, and I need to get my shit straight and name it reasonably (once we all agree)
4. Nothing against it, would have to be user-supplied for our api
5. Yup.

Who ya gonna call?
(Guestbusters!)