Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Michiel de Jong
    @michielbdejong
    @scenaristeur I created https://w3c-cg.solid.community/public/w3c-cg-chat/.acl with public read/write access at the time.
    only team members can write to that chat room
    David
    @scenaristeur
    ok
    But even for reading, not writing it takes a long long time...
    Michiel de Jong
    @michielbdejong
    are you logged in with a webid that's outside of solid.community?
    David
    @scenaristeur
    no not logged on sce...github.io/... but logged with spoggy-test.solid.community on localhost seems to be the same, and the date seems to be in another format ??? i get it in 01/01/1970 on Solidos and the good date on w3c-cg-chat
    For now i have to go , sorry
    but even for Reading (HEAD) time is long for solidos logged as spogyy-test.solid.community
    Mitzi László
    @Mitzi-Laszlo
    Would any of the developers behind the Solid apps listed in the 'social' category be interested in joining the Interoperability panel call next Monday at 2130 CEST on https://global.gotomeeting.com/join/620786365 to talk about making the apps there interoperable? If you're interested in joining and haven't already, don't forget to join the W3C Solid Community Group.
    Michiel de Jong
    @michielbdejong
    Sure! What's the agenda/goal of that meeting?
    We could use the LongChat format as a strawman and propose improvements ahead of the meeting.
    For instance, I think its main problem is that it's not authenticated.
    And we don't have a system for chat invites
    Michiel de Jong
    @michielbdejong
    We should probably fix both those problems at the Solid OS level?
    Mitzi László
    @Mitzi-Laszlo
    Correction - the interoperability panel call is on Tuesday at 1600 CEST
    2 replies
    Michiel de Jong
    @michielbdejong
    I added invites list, invite sender, and chats list to the stand-alone version of Solid OS chat-pane.
    Michiel de Jong
    @michielbdejong
    I can't deploy it to https://solid-chat.5apps.com/ for some reason (I asked 5apps support team about this) but you can try it out by following the localhost build instructions on https://github.com/solid/chat-pane#chat-pane
    you can send an invite to yourself, and then it will show up in your own invites.
    the 'your chats' list uses const { instances } = await UI.authn.findAppInstances({}, $rdf.sym('http://www.w3.org/ns/pim/meeting#LongChat'))
    so it searches your public and private type index for things of type LongChat
    Michiel de Jong
    @michielbdejong
    Screenshot 2020-08-14 at 22.46.56.png
    Michiel de Jong
    @michielbdejong
    Can't make it to the 4pm meeting sorry, but you can take that ^ as a strawman. We'll also discuss Solid Profile and Solid Chat at the Solid OS meeting tomorrow (in 23 hours from now), see https://gitter.im/solid/solidos
    Jules Cole
    @Julian-Cole
    I plan to look at adding infinite scroll to Solidarity Chat at some point but one issue is i'm not that happy with the 1 day of chat in a single file.
    Tim Berners-Lee
    @timbl
    Why not? Too much or too little chat in one file?
    Infinite scroll would be great — quite tricky in some ways.
    Tim Berners-Lee
    @timbl
    Let’s decide on a default place to put a 1 on 1 chat I invite you to. Something like https://Alice.solid.community/IndividualChats/bob.inrupt.net/index.ttl say
    If bobs webid ends in something like profile/card#me .
    Michiel de Jong
    @michielbdejong
    ok!
    Jules Cole
    @Julian-Cole
    @timbl I think too much for larger group chat; it would be fine for smaller chats; if you look at gitter they initially seem to pull in 47 chats before the last chat (on my desktop) and every time you scroll-up it pulls in another 47 previous chats - which sounds pretty sensible to me. What if in long-chat if anyone sends #51 message of the file they create a new file chat2.ttf.. etc in the same day folder?
    Jules Cole
    @Julian-Cole
    I know there was a mention about Solid profile apps; so just a comment on the profile pics, in Solidarity i just pull in the profile pic directly, and some profile pics can be quite big (which is fine) but having just one single version of the pic is probably not the way to go; Ideally under the hood (client-side) it should be resized to maybe preset sizes like 1024px, 512px, 256px, 128px, 64px using a wasm module using bicubic / blinear with a little sharpen filter afterwards.
    Tim Berners-Lee
    @timbl
    Breaking a long day into multiple files does make sense. 47 is a funny number! I guess it is arbitrary.
    Yes let’s pick 50 and write it up. That means reading the day directory before reading the chat file.
    Have to make code back compatible.
    Tim Berners-Lee
    @timbl
    Yes also agree about the client quietly making thumbnails of various sizes of profile pictures and probably other pictures too. Also we can add a separate banner background picture maybe
    David
    @scenaristeur
    @Julian-Cole sure i could adapt Shighl lib to match 50 messages but i don't understand what is the problem with more than 50 . Is it the post operations (retrieve name /pic of sender ) ? If yes, this is not a problem of length of chat.ttl file, but a problem of caching the name/pic of users instead of retriving them each time. If we make 50 messages files, who would build the second &third.. files ? The server ? I don't think it is it's role to say 'oh there are more than 50' i must create a new one! The client ? It will not simplify the implementation... When the client will want to write a new file... Oh there are more than 50 in the chat.ttl, let's create a second .. oh it already exists, how messages in it ? Ho more than 50... And so one... It will make many many more request to post and to retrieve messages... I don't think it's a good idea...
    David
    @scenaristeur
    It's already too much in my opinion to have subfolders 2020/08/19/chat.ttl 2020/08/18/chat.ttl with 404 if the file doesn't exist... Why not using in the main folder 2020-08-19.ttl 2020-08-18.ttl this way we can get a list of all existing file/day in one request with solid-file-client/readfolder . Then it's easy to load each one when the infinite scroll come to bottom. With 50 file per message it will be harder to know which file to load chat1.ttl, chat2.ttl, ...
    ??
    Another day ? Which day ?
    David
    @scenaristeur
    When you open the chat, where is the last message ? In chat7.ttl ? chat8.ttl?
    Jules Cole
    @Julian-Cole
    "Is it the post operations (retrieve name /pic of sender )" no. Do you not see any possible ui performance hit / unnecessary resource loading when you read and parse a full day of chat each site visit, as opposed to just reading 50 messages at a time each visit? why does gitter only seem to read 47 messages at a time?
    Jules Cole
    @Julian-Cole
    If you get the file count of folder 2020/08/19 and there are 5 files you load chat5.ttl; 2 files=chat2.ttl; 1 file=chat.ttl
    Michiel de Jong
    @michielbdejong
    This might come in handy, I created it so that we can put a "Chat with me" button on every Solid user's home page: solid/chat-pane#45
    David
    @scenaristeur
    @Julian-Cole sorry but as already said, performance issue is not due to more than 50 messages, but retriving name & pic form user . With Shighl, If one user post 10 messages we go 10 times get its name & 10 times get its pic https://github.com/scenaristeur/shighl/blob/9b4b61d06d8a20f55de3f2aa580cbc5fb840d584/src/Shighl-chat.js#L131 performance can be optimized by caching them
    And using Tripledoc instead of ldflex could be a better way reading files. 50 messages per file will complicate everything. The first thing is to review Shighl lib before make it more complicated...
    David
    @scenaristeur
    @michielbdejong nice, should the the user change it's inbox acl to receive notification?
    @Julian-Cole on the other side i'm agree to the different size of pictures 🙂👍
    Another perf issue, could also be the json + websocket you developed on each user pod. I would rather use a connected_users.ttl on the chat folder that would be updated on each connect/disconnect... So you only have one websocket instead of one per user 🤗
    Jules Cole
    @Julian-Cole
    @scenaristeur "@Julian-Cole on the other side i'm agree to the different size of pictures 🙂👍" well 1 idea out of 2 isn't too bad! lol