The high cost of fake urgency in the modern workplace
https://qz.com/fake-urgency-at-work-leadership-burnout?utm_source=flipboard&utm_medium=activitypub
Posted into Business News @business-news-quartz
The high cost of fake urgency in the modern workplace
https://qz.com/fake-urgency-at-work-leadership-burnout?utm_source=flipboard&utm_medium=activitypub
Posted into Business News @business-news-quartz
@the_moep I think you're right that it's not enabled by default -- but I think that's a good thing. People should know what's happening with their content. Then they can take the steps they want -- leave it alone, silence the notifications, block the bot, do something else.
@the_moep it's ok that you don't understand it!
On the protocol level, the receiving server keeps a list of shares of every object. If we didn't send the Announce activity to the original author's server, it would not be able to keep that list.
What happens at the protocol level doesn't have to be the same as what happens at the user interface level. In fact, it would be pretty wild to have your UI controlled at a remote server!
@levelbot nice
we're seeing cauliflower levels at about 73%
(73%) ■■■■■■■□□□
Bonjour! 👋 Le 15 avril, nous étions au ministère de la Culture pour présenter le bilan de notre exploration mastodon.
Le @palaisdetokyo , @theatreodeon et @LeMuseum ont notamment partagé leur retour à cette occasion.
On a présenté aussi un argumentaire à destination des directions et élu·e·s (en cours de finalisation).
Ainsi que les raisons de cette exploration, ses modalités opérationnelles... et la continuité et ouverture de reseauCulture.fr ☺️
Et voici le replay !
👉 https://doc.reseauculture.fr/doc/presentation-retour-dexperience-150426-Z7aB13HXL3
@evan I'm unsure if a manual filter option would solve the intial confusion, seeing as at least in your PR the filter is not enabled by default and people tend to not change away from it.
Also it seems that this filter is for all notifications, not only for boosts. Not noticing a bot (or people abusing the tag) replying with some weird stuff to your posts would be a major issue. In my eyes this needs a more fine-granular setting
(Or as I suggested: Not send notifications to the user at all when "boosting" in an automatic way. I personally do not see the value of what is basically providing the same functionality as hashtag following sending notifications when hashtag following itself doesn't.)
Was the original intent of the ActivityPub / ActivityStreams "name" field to be a title?
(It seems as if some software is using it that way.)
What should the file-extension for ActivityPub / ActivityStreams documents be?
I.e., for application/activity+json data?
I've been using .activity
Ex: filename.activity
(The extension cannot be .json or .jsonld if you want to be able to detect it just based on the file-extension.)
What do you think?
Another update to #tagspub tonight. I had a number of problems with following people back last month, most of which are fixed bugs. I added some startup code to check who hadn't responded, unfollow and refollow. Instantly doubled the number of followers. Should have done that a lot earlier!