You are reading content from Scuttlebutt
@mmckegg

Patchwork v3.10.0 Released!

See https://github.com/ssbc/patchwork/releases

It's currently marked as pre-release for the next few days until we are sure that it is stable, but feel free to try it out now and let me know!

What's new?

  • the feeds now group follows, blocks, subscribes, and profile updates into visual meta summaries (that can be expanded to see full messages)
  • preview window now displays for all types of posts (including profiles and gatherings)
  • replies are no longer visible when the author of the thread has blocked the author of a reply (the beginnings of thread moderation)
  • added post visibility warnings to confirm publish dialogs (public, private, number of recps, assigned name visibility)
  • when you visit a profile that you have not downloaded (outside your hop range), patchwork will attempt a once off retrieval from connected pubs (this works well in conjunction with missing message warnings and author guessing)
  • add "Copy Embed Markdown" to right-click menu on all image blobs
  • lots of stying improvements and bug fixes
  • 4 new localizations

View full changelog

Updated to latest scuttlebutt and electron deps!

Thanks @christianbundy and @arj for all the work you put into this!

Missing Language Strings

There are currently a lot of missing translations for the recently added strings. Feel free to update them, and send pull requests! More info here: https://github.com/ssbc/patchwork/issues/654#issuecomment-340185274

@Tim Schumacher (work)

@Matt McKegg wrote:

Patchwork v3.10.0 Released!

Congratulation to the release!

Could you please post sha512 hashes of the binaries under your identity, so people can verify them?

@mmckegg
  • Patchwork-3.10.0-mac.dmg 9180d09158860027869dfd3f500d6dd54305792e05f7ea5522557ba318ef31f5d1a078d646b08b398395eb72998a7b0bcbb0671739e05f5dc84cc414f065a658
  • Patchwork-3.10.0-windows.exe fa8ce741691f7a3972c9d4d6c3281adda8c5847c215d309033514b866e458804fb219bc6140d2b0249e4369a7d78d3a027e02a3f6dc7b9201d7013c6803b2816
  • Patchwork-3.10.0-linux-x86_64.AppImage 04a1190c459dc8bb061b3f90db8994e1a7bddcb9e42392a52f039d9be22b67a5d48558490f33503c031b02f9e048babeee29141abdb07ff5e10daf7ea883e117
@mmckegg

whoops, I mean hashes :sunglasses:

@cryptix

Very nice! are the sbot and index plugins updated now or was that in 3.9 already (PR 789)?

@mmckegg

@cryptix

Very nice! are the sbot and index plugins updated now or was that in 3.9 already (PR 789)?

Updated in this latest version!

@andrestaltz

Congrats for releasing! I'm using it now :)

@Rich

Thanks Matt, love your work

@mmckegg

There seem to be some performance regressions in this release. I haven't got the time to get into them at this exact moment, so I released anyway. Keen to hear if things are noticeably slower for others.

@MistyWrites

So for the rest of us who are interested in getting this new release, is it downloaded automatically when we launch #patchwork or do we need to download it from the releases page?

Also, I'm assuming we don't uninstall patchwork from our machine?

For people who don't instinctively get github or how releases work, or who just want the new software -- how do we get it while using the current version?

I get github. I'm just a technical writer and I'm always instinctively looking out for the new person. I'm not finding the upgrade instructions on the releases page or the scuttlebutt.nz guides pages.

@Zach!

Heya, @MistyWrites !

Historically, when a new release is set as the stable, current release a small banner appears in your Patchwork letting you know there's an update to install. It did not appear here as 3.10 is still in a pre-release stage.

If someone wanted to use the pre-release version of patchwork, they would go to the github releases page, and click the download link within the 'pre-release' section for whichever operating system they're using.

I am using a mac, so I am not sure how it works for linux and pc, but for me I clicked on the .dmg link, and when it downloaded a patchwork installer appeared, prompting me to drag the patchwork icon to my applications folder. This required me to replace the instance of patchwork already in my applications, but that was alright. It's safe to replace patchwork, as none of your data is stored in the client--it's all safe within your .ssb folder.

The FAQ could be updated to include this, but I am curious; do you feel there is confusion on how to find and upgrade to experimental versions of patchwork, or is it how to upgrade the client in general?

@MistyWrites

@Zach!

I guess just the experimental versions. But I haven't been around #patchwork long enough to experience an stable upgrade and would not have known I would have gotten a notification directly from #patchwork.

To make things clearer when announcing a pre-release, etc... a sentence could be included: "As a reminder, when stable upgrades are available, you'll receive a notification [or whatever] from Patchwork." If you want to upgrade to use the pre-release version, do the following: ...."

I think the FAQ could be upgraded to include this. I went to look it up in the FAQ before I posted the question here. I could update it if the docs are in github. Would you like me to do that?

@MistyWrites

@Zach!

I found it. Let me look at it. I'm already in github.

@Zajo - ZAR

Why is it marked as a Pre-release?

@mmckegg

@Zajo - ZAR

Why is it marked as a Pre-release?

Because I made a bunch of changes last minute and I'm slightly concerned I might have broke something. Instead of just waiting to see, I released it! :grinning:

If no one reports anything critical in the next day, I will mark it as a proper release. This is pretty standard for Patchwork releases.

I don't like to push out too many updates in a row, so I want to avoid having to do a notified point release a day after a previous one. Trying to avoid update fatigue.

@Quold

Very nice! I was so thrilled i began typing on the midi piano keyboard. Thanks for the labor of love.

@masukomi

Thanks to everyone who contributed to this I'm especially happy to see that some tools to deal with / protect against bad actors made it in. :+1:

@Zajo - ZAR

@Matt McKegg
That's reasonable. Thanks for explanation.

@bobhaugen

@Matt McKegg

Keen to hear if things are noticeably slower for others.

I notice two things being slower: clicking the Public button to return to the top, and clicking to show 1 or 2 new posts.

I have not seen any of the infinite loading or scuttling events in the new release. If that was a planned improvement, or even if accidental, thanks a lot, I appreciate it. :smile_cat:

@MistyWrites

Wow!!! I loaded the new version. I feel like I just walked into my house and seen a bunch of upgrades. This is sooooo awesome!! (MistyWrites just keeps looking around in awe)... :+1:

@Thunder

@Matt McKegg great update! I love the grouping for that clean look on our profiles alot :smiley:
one questions though, there was a mention of back/forward keyboard shortcuts; what are the shortcuts? :sweat_smile:

@christianbundy

@Thunder

  • Back: CommandOrControl + [
  • Forward: CommandOrControl + ]

Explanation on why we're using both Command and Control as options:

On Linux and Windows, the Command key does not have any effect so use CommandOrControl which represents Command on macOS and Control on Linux and Windows to define some accelerators.

-- Electron documentation

@masukomi

I don't know who's responsible for this little bit of UI design but i have to say, I love it.

Patchwork.png

Those notifications have gone from a thorn in my side to a widget I enjoy encountering. :smiley:

@christianbundy

@masukomi

I'm really enjoying it too -- @Matt McKegg is a machine!

https://github.com/ssbc/patchwork/pull/828

@happy0

@Matt McKegg it does feel like there's a small performance regression for me on loading people's feeds / maybe loading the public feed. I think it improves a bit once the client has 'warmed up.'

Good release =D. Fanx.

@Jacob

@Matt McKegg

when you visit a profile that you have not downloaded (outside your hop range), patchwork will attempt a once off retrieval from connected pubs

Is this ooo :O

@mmckegg

@Powersource

No, it's a cheap hack :sweat_smile:, but it will work much better once ooo (and ebt) are in patchwork (as we'll get a much more reliable hint about who the author of a missing post is).

All that patchwork is doing is adding the IDs of profiles you visit to the replicate request table. This is like following them (or someone that follows them), but only temporarily until you close patchwork, and without publishing that fact to your feed. It's kind of like a follow preview.


How this works in practice

If someone replies to a post in patchwork, their post includes the ID of the user they are replying to.

So if another person is viewing that thread and sees that someone is replying to a post they don't have, the interface can display a link to the profile of the missing person (just their ID as we don't know their name yet). But as soon as you click the link to their profile, it will download and you will see all of their messages! But you won't actually follow them for new messages.

Does that make sense?

@mix

replies made from patchwork don't do this (so people know).

@mmckegg

@mix

replies made from patchwork don't do this (so people know).

Do you mean patchbay?

@Alanna

@Matt McKegg I think this is a change in the recent release. When I updated my profile picture I saw this in my main feed.

Screen Shot 2018-07-12 at 10.11.23 PM.png

Is it supposed to show my old profile pic changing to my new one? Or is there another meaning I'm missing in this symbolism? It shows the new pic in both boxes.

@cryptix

Interesting find @Alanna! Having the before would be nice but I'm not sure the ssb-about reduce plugin is capable of history (yet..)?

also: I guess the module is just looking for type:about msgs. In this special case of A about B both parties are equal and it might be okay/less noisy to ignore since it is about yourself?

@Rich

@Alanna I am pretty sure that UI is saying "Alanna did something to Alanna", which makes sense in logical terms, but not really in UX terms.

@mmckegg

@Alanna

Is it supposed to show my old profile pic changing to my new one?

no, unfortunately it is working as I intended!

I agree that what you suggest would be much better, but as @cryptix mentioned, it would be quite difficult to do. But I'll put it on the todo list anyway!


@Richard D. Bartlett

makes sense in logical terms, but not really in UX terms.

Yeah, pretty much. This is a case of pushing an algorithm too far :grinning:

Originally I was gonna have another state just for people updating their own profiles, but it made things a bit more complicated. Originally I was gonna do a completely different rollup for about messages (one that actually told you what changed), but it was hard and the follows interface worked... well.. better than the old way.

@Alanna

Thanks all for the context :smile:

Join Scuttlebutt now