XSF Discussion - 2020-07-28

For thoses that wants to try out, I've implemented a few days ago bookmarks:1 in Movim master

You can directly try it out on the official pods

edhelas: 👍

It also supports :0

So now we just need a switch day?

As you want :)

I'm planning to release the 0.18 soon with this feature in

edhelas: are you migrating bookmarks?

Or will this make bookmarks incompatible with literally everything else out there?

Nah

Well

I have a tool to migrate from the old system and push it to :1

And i'm pulling from :0 and :1 and pushing to :1 on edit

A tool? Does that run automatically?

When and how often?

No

This should really be done by servers I guess.

Basically after I pull from :0 and :1, if the list is empty I invite the user to sync its old bookmarks

There's a button for that

Users switching browsers are used to importing bookmarks 🤪

Luckily I haven't switched browsers since firebird 0.7

edhelas, so that means a user using any client other than Movim will effectively lose their bookmarks in it?

Link Mauve no, because I don't clear the old storage:bookmarks ones

Like Firefox is not clearing Chrome bookmarks when they are imported :p

edhelas, so you’re only desynchronising?

My current advice would be to keep using Private XML bookmarks until the server advertises bookmarks2 conversion.

Fwiw Conversations also has code for bookmarks 2.0 - but it's currently not enabled because I don't want my users to loose sync

okay

Plus I think servers don't support the unlimited items feature yet

Which is sort of required if you don't want to use magic numbers

that was the goal of "multi-items" in 0060

> The service supports the storage of multiple items per node. It requires the pubsub#max_items configuration item to be exposed to the user and allow sensible values (higher than one) to be set in Configure a Node.

I'm talking about the publish options max

Which turns out server devs don't like

Meaning we probably have to redo that

I doubt we'll support *unlimited* items

it's not specified as unlimited. but as server defined max

Daniel> Meaning we probably have to redo that What a pitty, I do like it. What would be the alternative? An additional (boolean?) field which tells the server to allow multiple items on that node?

flow, the issue isn’t whether multiple items are allowed, it is that multiple implementations have a different value for their maximum amount of items, and short of hardcoding 255 or so (which might be too low for some applications) in all clients it was impossible to know the server’s maximum pubsub#max_items.

It’s still impossible, but you can now request it since 0060 1.17.0.

Link Mauve, I know

If I am not mistaken we previously only had a field which set the max items for a node, and if you set it to a value >1, then you allowed the node to carry multiple items

and this field was extended to allow besides the integers, also a string value, "unlimited" (or so), to denote that you want the pubsub service to retrain multiple items for that node

but ppl where not happy, because we now have a value that can either be an integer or a string

so my suggestion was to add another field 'multiple-items', which if set to 'true', signals the server that it should keep multiple items for that node, akin to the "unlimited" value for max-items

and I was wondering if that's a good idea that would make people happy

flow, it’s not 'unlimited', it’s 'max', and its meaning isn’t that the node can retain multiple items, it’s that the node will accept as many items as the server is configured to accept.

(Limit which isn’t even queryable.)

I know, hence I wrote "unlimited (or so)"

Some people would probably prefer -1 instead of max

Daniel, then the feature wouldn't be discoverable, or you would need to jump through an extra hoop to make it so, no?

Max currently has a disco feature. So you'd need a new disco feature

Or rename that feature essentially

if it was a new field, we could re-use the existing mechanisms for pubsub feature discovery, I believe. not a big deal, but still

hi

🇸🇪

Guus: how did you do that?

> Guus wrote: > 🇸🇪 Hmm just a picture? No code?

That's just an emoji.

Well not sure how that works

🚩🇯🇵🇩🇪🇨🇳🇺🇸🇫🇷🇪🇸🇮🇹🇷🇺🇬🇧

Similar to things like these: 😁👍💕🍿🏆🥳

Ahh well...

Roger

Don't seem to have scandinavian flags myself

Guus:

🏴‍☠️

If you can see them, you can probably copy paste them.

Just ask Guus whenever you need a flag.

You have a Danish flag or an all white flag would be cool ✏

I walked right into that one

🇸🇪🇸🇯🇩🇰🇫🇮

How much more Scandinavia do you need?

🇩🇰

!XSF_Martin: well does not seem to be part of my system.

Old android maybe.

8

9 here

Ahh... Well it sounds like it is a bad idea to update on my old mobile... Although the update is yet be seen... ✏

Android manor updates suck, but we should stop the offtopic here.

!XSF_Martin: roger

One of the owners in this room seems to be a Roman Papist - just so you know. Catholics are Wolves in Sheep clothing who follows that AntiChrist 666. A pagan Satanic cult, the very masterpiece of Satan. They hate the truth and look to the Devil for guidence. They worship a dry cookie and call it God...

Let's get back to flags.

Holger: Just noticed. Anyway back to research. :)

https://www.getselfhelp.co.uk/psychosis.htm

🇫🇮️

moparisthebest: The truth does that to people - but the truth stays the truth.

Ups that was not private.

im atheist so im neutral on this discussion

This isn't remotely topical, so stop please.

ikeameatballs: okay... But most people tend to hang on to Evolution when they are atheists.

As I said, please stop.

moparisthebest: I don't fall for slick Catholic talk. The Pope the Devils front face in this worldand any Christian being part of that system should come out of it imediatly.

Or ignore me.

Kev, thx

Trying to set a new record of channels to get banned from? ✏

ah sorry I see he didn't understand how PMs worked, I was trying to talk some sense into him and he was just responding in here :/

>AntiChrist 666. A pagan Satanic cult Where can I enroll?

moparisthebest, I fear that is wasted time

yea I suspect so, it was worth a shot though

I think *everyone* should drop it.

yeah

oh

UPDATED: XEP-0313 (Message Archive Management)

congrats, MattJ

something went wrong though and the revision block points to the wrong date

I’ll get so much flak for that

ah well

Uh oh, thanks!