pull down to refresh

Finally.

You can post to up to five territories at the same time. The same post, and all of its comments, are shared across the territories.

how the monies workshow the monies works

For costs variable with the territory, like posting and reply costs, you pay the costs of posting in each territory combined. 30% continues to go to the rewards pool, and each territory gets their proportion of the rest. For example, if you create a post crossposted in ~bitcoin (30 sats) and ~econ (63 sats), you'll pay 93 sats. The comments of that post with pay 6 sats (1 sat for ~bitcoin plus 5 sats for ~econ).

For costs that are fixed with the territory, like boost and zap sybil fees, territories split those fees evenly. Continuing our example, when that post crossposted in ~bitcoin and ~econ is zapped 100 sats, 9 sats go to the rewards pool, and each territory founder gets 10.5 sats.

new territory selectornew territory selector

This is harder to explain with words but, in the post form, territories can be selected/filtered by typing now. It's pretty basic at present but the hope in the future is to have semantic searching, and recommendations based on the content of your post. This multi-select will also move to the navbar before too long.

That's it.

what's next and nearwhat's next and near

In addition to the usual extermination services, most of my focus will shift toward:

  • improving our onboarding experience
  • healing all the scar tissue introduced by the noncustodial stuff
  • simplifying the product in any way that I can
  • making the site more aesthetically consistent and thoughtful

After that I will continue working on all the planned territory improvements that have been delayed.

Sox will continue our introduction of the WYSIWYG editor and then extending its usage beyond simple posts and comments.

I am seeing an issue on desktop when making a post and selecting territories. See recording below. This is the error message when I copy details:

Objects are not valid as a React child (found: object with keys {label, items} for the full message or use the non-minified dev environment for full errors and additional helpful warnings.). If you meant to render a collection of children, use an array instead.

It seems like posting from a territory directly is OK, but this flow is not working for me. It is just me? I disabled cache too, so it should be pulling the latest app?

Edit: I can open this as an issue in the GH repo if that's easier. I just thought I'd mention it here since it seems related.

reply
50 sats \ 1 reply \ @k00b OP 11h

It's muted territories. I'm deploying a fix now.

reply

Great, thank you!

reply

My PWA is suddenly unhappy, related?

Edit: and copying the error info popped a failure toast

reply

Mine is fine.

The PWA has an issue where it can't recover from clientside errors like this without a hard close-open.

If this persists after hard close-open then it's probably related.

reply
171 sats \ 7 replies \ @siggy47 4 Jan

I'm also experiencing PWA error, but only when clicking notification bell.

reply

Ah okay. I'll try to fix it asap

reply

It's an error at ek 😂

TypeError: Cannot read properties of undefined (reading 'name')
    at ek (https://a.stacker.news/_next/static/chunks/pages/notifications-89c7e82366fa6a0d.js:1:31113)
    at ad (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:58499)
    at i (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:119464)
    at oO (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:99117)
    at https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984
    at oF (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991)
    at ox (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:95743)
    at oS (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:94298)
    at x (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:137528)
    at MessagePort.T (https://a.stacker.news/_next/static/chunks/framework-c6ee5607585ef091.js:1:138058)

Component stack:

    at ek (https://a.stacker.news/_next/static/chunks/pages/notifications-89c7e82366fa6a0d.js:1:31004)
    at div
    at c (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:427584)
    at et (https://a.stacker.news/_next/static/chunks/pages/notifications-89c7e82366fa6a0d.js:1:14781)
    at es (https://a.stacker.news/_next/static/chunks/pages/notifications-89c7e82366fa6a0d.js:1:13666)
    at eH (https://a.stacker.news/_next/static/chunks/pages/notifications-89c7e82366fa6a0d.js:1:33291)
    at main
    at tI (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:420779)
    at https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:950071
    at tO (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:422309)
    at eD (https://a.stacker.news/_next/static/chunks/pages/notifications-89c7e82366fa6a0d.js:1:34457)
    at V (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:994243)
    at p (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:139717)
    at f (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:131809)
    at H (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:439386)
    at O (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:503339)
    at g (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:126768)
    at l (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:123894)
    at h (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:126306)
    at b (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:465050)
    at F (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:477915)
    at d (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:212181)
    at c (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:520946)
    at tR (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:1076356)
    at tF (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:1076063)
    at u (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:429649)
    at c (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:990181)
    at x (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:990960)
    at V (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:994243)
    at ei (https://a.stacker.news/_next/static/chunks/pages/_app-7e4d014e88519dd9.js:2060:995127)
    at p (https://a.stacker.news/_next/static/chunks/main-3bc905d33a3f61f9.js:1:58914)
    at $ (https://a.stacker.news/_next/static/chunks/main-3bc905d33a3f61f9.js:1:9438)
    at Q (https://a.stacker.news/_next/static/chunks/main-3bc905d33a3f61f9.js:1:10949)
    at es (https://a.stacker.news/_next/static/chunks/main-3bc905d33a3f61f9.js:1:14169)
reply
252 sats \ 2 replies \ @k00b OP 4 Jan

awwww

yep it was territory subscription notifications

deploying the fix meow

reply
115 sats \ 1 reply \ @optimism 4 Jan

works very meow

reply
reply

Hard close then open, I get it navigating to notifications every time.

reply

Same for me but I'm on my laptop

reply

This should be cross posted for fun lol

reply

Done!

reply

This answers another question- can you add cross posting when editing a post.

Can you remove a territory during edit? How do the fees change?

reply
50 sats \ 1 reply \ @k00b OP 4 Jan

You basically pay the diff on edit like (new_territories - old_territories).sumPostCosts().

You pay for the new territories you're adding. No refunds for any that you remove.

reply

Makes sense. Thank you!

reply
50 sats \ 0 replies \ @Fenix 23h

I can’t imagine where I can use it, but is good know that I can, improvement is always good. Anyway I know this is huge. Congrats guys and success in making SN a place where our mouth is.

  • simplifying the product in any way that I can
  • making the site more aesthetically consistent and thoughtful

SN is very simple and aesthetically consistent to me. I pleased by this since I started here.

reply
100 sats \ 1 reply \ @sox 4 Jan

already used it, wanted to use it again

reply
0 sats \ 0 replies \ @sox 5 Jan

cursed, love it

reply

Very exciting. We'll have to rethink our posting fees to attract crossposters.

reply
reply

Great news! It’d be sick if territory owners could set different prices when crossposts.

reply

There will be room to add lots of stuff to cross-posting

reply

Awwwww yeah!!! I am excited!!

reply
50 sats \ 0 replies \ @Angie 4 Jan

Bueno si todo sale bien bienvenido sea, espero tener un día un territorio o afiliarme a uno mientras sigo apilando, 🧡⚡

reply

pretty cool

reply

Can't get about comment price.


Now I see 5 sats, who'll get them: aliens, dev, meta or someone else?

And what would happen to comment price if one of the territories got archived?

reply
Now I see 5 sats, who'll get them: aliens, dev, meta or someone else?

they'll be split between them

And what would happen to comment price if one of the territories got archived?

it would stay the same. as it is, posts in archived territories can still receive comments.

reply

So the price of comment is equal to the price of the most expensive comment of all cross posting territories?

reply

No, it's the price of all territories' comment costs combined

reply

Gracias

reply

de nada

reply

Interesting!

reply

you

reply

WYSIWYG is better than this old editor.

reply
0 sats \ 0 replies \ @sox 14h

Then you're gonna like our next releases, stay tuned ⚡️

reply

Being able to cross post ~Music with ~Gaming has opened up a whole world of awesome for me.

This is going to be great!

reply

Nice.

reply

This is excellent! I love knowing that S.N. is growing every day as a platform for all of us who interact and revolve around the new world that Bitcoin has opened up for us ⚡⚡.

reply

This breakdown of territory costs is extremely helpful for transparency, especially seeing how the 30% reward pool split works. The complexity around variable costs (like the 93 sats example) is unavoidable with multi-territory posting, but the clarity here is a big step forward. It shows the inherent friction in broadcasting widely, which loops back to why simplifying the initial on-ramp (via temporary custody) is so crucial for attracting the mainstream user who just wants to post once. Great work on simplifying the mechanics

reply