My concern is that when we succeed making "our own web" popular, the Big Cos will lobby for legislation that would put burden on all operators, such that it would be unreasonably costly for small operators but easy for themselves to meet. Probably under disguise of "think of the children". Besides technology we'd need a strong organization advocating for "our own web".
That is already happening, but this is where peer-to-peer becomes helpful, because in order for 'Big Cos' and 'Big Gub' to audit your web they have to have visibility into it in the first place.
I'm thinking more of situation where definitions of mass-media are extended to cover individual bloggers.
> Professional influencers with over 500,000 followers fall under the Dutch Media Act (Mediawet, 2008) and are supervised by the media authority CvDM, which applies rules similar to those for on-demand audiovisual media services, including requirements on recognizable advertising and protection of minors.
> Current Rule: Now, influencers with 100,000+ followers (across YouTube, Instagram, or TikTok) who post at least 24 videos a year and earn money must register with the CvdM and pay annual supervision fees.
> The Burden: You are expected to know your reach. If you cross the 100,000 mark and fail to register, you are technically in violation.
I have a silly take on this: to avoid rocking the floating city you throw the rocket overboard, let it re-orient itself upright, then use the main thruster to slow down the fall and then move up.
My workaround for this is to always log in from porn/incognito mode where it doesn't remember cookies. Each time I have to type password and go through 2FA.
> Resist the urge to build walls between people/teams/departments
Do you often have to deal with support staff reaching out directly to developers on Slack to investigate some problem – without going through "normal" process of creating a ticket that gets assigned? Or even asking for features.
Developers generally want to be helpful, but also small requests often turn out to be rabbit holes. And even in best case it distracts from work that was explicitly assigned and scheduled.
I noticed I experience a bit of anxiety every time I'm doing some work that came through backchannels. The way I try to alleviate is create the ticket myself, mention its source and assign it to myself. This way switching context is visible and I can tell myself that "if manager doesn't want me to spend time debugging this now, they can react".
In fairness, it seems the problem in your case is that the "manager" has built up walls between people, trying to own the work, and in that not allowing you the full context that would allow you to make informed decisions around such asks. "The manager not wanting you to spend time debugging this now" should be a false premise. Knock down the walls and you will know yourself that you shouldn't spend time debugging it now.
That makes sense. Either knock down the walls all the way and empower developers to make decisions, or keep the walls and let all requests go through the pipeline.
> failure condition on a computer bus or network in which a malfunctioning node sends data at inappropriate times thus interfering with the communication of the working nodes
1. The cash doesn't have to be withdrawn all at once, it can happen over the course of months
2. The cash can come from earlier cash transactions, not withdrawal
3. Payment can be indirect: CEO donates to a non-profit that hires sheriffs family
4. Instead of kickback the CEO can repay the sheriff with another favor at future time
I hope we're not planning to outlaw cash and implement total invigilation of every transaction just to make corruption slightly more inconvenient.
