deg, eyecontact, cuteness overload
Hello Im Océane's partner and I took control of her account mouahahahahaa
I know youre used to political content but here's a pic of our dog instead
Deuces!
Discussion
deg, eyecontact, cuteness overload
Hello Im Océane's partner and I took control of her account mouahahahahaa
I know youre used to political content but here's a pic of our dog instead
Deuces!
primo post su bonfire!
Looking for some #valueflows here. Are there any examples on this demo?
@toontoet not on this instance, here we have enabled only microblogging features (plus some bonfire custom ones like circles, boundaries). The only way to test VF specific extensions atm is to run a local instance with Cooperation FLAVOUR enabled
Looking for some #valueflows here. Are there any examples on this demo?
@mayel @ivan Wow this was a tough one to find.
It's happening in the smaller post composer that pops up on the bottom right of the screen. Using a Mac, Google Chrome, 1700px or wider screen.
So for some reason when I reply, the Content Warning is being enabled by default. If I KEEP it enabled, then the space on this smaller posting window isn't being recalculated (minus content warning box space), and when I get to the end of the box, it runs over and I can't view what I'm typing.
So I had figured I had hit a "hard stop" and it wasn't allowing any further entry. I tried two different themes and it happened on both. Happened on three different themes, so no theme specific.
Removing the content warning option fixes the issue. Hope this helps. I've noticed some great speed improvements lately, by the way!
Attached video (maybe?). 😊
I randomly came across this via HN and thought it was relevant to the above @ivan
@dajb thanks I've started reading it, bookmarked for tonight!
@vera a link preview is supposed to appear, it wasn't in this case because of the absence of opengraph/oembed/etc tags, but that will be fixed in the next update
@vera testing if fixed: anagora.org/coop-cloud-feder...
@ivan Here's some #bonfire_feedback if you haven't thought about this already. Have some pre-packaged sets of audience configurations - "Community Clubs", "Local Crises Support", "Family with Children", "Family with Teens", "Family Elder Care"
Also - how are you writing longer posts than I can? I keep running out of space. 😊
> When the computer takes more than 0.1 second but less than 1 second to respond to your input, it feels like the computer is causing the result to appear.
> This means that during 1-second response times, users retain the feeling of being in control of the interaction even though they notice that it's a 2-way interaction (between them and the computer). By contrast, with 0.1 second response times, users simply feel like they're doing something themselves.
> For web usability, this means that new pages must display within 1 second for users to feel like they're navigating freely; any slower and they feel held back by the computer and don't click as readily.
Arguably for something like liking or boosting it's not the same as an automatic UI interaction (like opening a menu, which should be as close to instant as possible), you're communicating with your instance's server and in turn other people's servers, but more importantly with other humans, since you're requiring attention from the author and/or your followers by taking that action.
So not "clicking as readily" as they say may be a pro?
@ivan @dajb another UI approach that could work is what some messenging apps do, where they have a slightly different icon to show various statuses: eg. message received by server -> message received by user's device -> message read. So in our case: click taken into account -> received by server -> queued for federation -> etc?
> When the computer takes more than 0.1 second but less than 1 second to respond to your input, it feels like the computer is causing the result to appear.
> This means that during 1-second response times, users retain the feeling of being in control of the interaction even though they notice that it's a 2-way interaction (between them and the computer). By contrast, with 0.1 second response times, users simply feel like they're doing something themselves.
> For web usability, this means that new pages must display within 1 second for users to feel like they're navigating freely; any slower and they feel held back by the computer and don't click as readily.
Arguably for something like liking or boosting it's not the same as an automatic UI interaction (like opening a menu, which should be as close to instant as possible), you're communicating with your instance's server and in turn other people's servers, but more importantly with other humans, since you're requiring attention from the author and/or your followers by taking that action.
So not "clicking as readily" as they say may be a pro?
I've just filed a bug for what might seem like the world's most trivial thing @ivan
github.com/bonfire-networks/...
However, I think that having a delay from clicking the star icon to it turning yellow is likely to lead to frustration and/or people repeatedly clicking it because it "hasn't worked".
(you know when the UX 'bugs' are getting this specific that you're doing something right overall!)
(you know(you know when
I randomly came across this via HN and thought it was relevant to the above @ivan
#bonfire_feedback
This may be a bit of a different perspective on the Circles, Boundaries and Roles concepts. I have a parent with #Dimentia that loves social media.
Would it be possible to setup an account so that they can ONLY interact with users within specific circles and boundaries? And even further - limit that user's response types (like, retweet only)?
@box464 I think we have almost all the building blocks in place to implement such feature (the recent development of groups and topics can be relevant as well).
It would require to build custom UIs and develop ad-hoc features on top of such building blocks to make it happen.
The high-level picture that cross my mind would be something like this:
At this point bob can presumably safely interact with a custom audience, but he would be still able to see the feed and follow any users in the fediverse in different ways (navigating to a family member profile, looking to their followers and go from there).
We already have the possibility to limit features based upon boundaries, so we should enforce such rules across all the platform (eg. If I search for a username or hashtags, open a thread or look at user followers they should return only contents / users based upon my boundaries )
That would be a crucial features for enhancing safety on social network for different categories and usecases (another one that comes in my mind is about introducing children/teenagers on social networks and the internet at scale in a safe environment)
#bonfire_feedback ^ no strikethrough?
@Oceane fixed 😊
There' a new kid on the block. Let's test it out.
bonfirenetworks.org/
#Bonfire #Fediverse
Filed an issue: github.com/RobertDober/earma...
This has be fixed in the library, so should work with the next update.