bhtooefr

If you follow me here, I've moved to @bhtooefr@snack.social and will only use this account as a backup.

Please follow me over there!

BTW, although follower import isn't working so I haven't actually followed anyone that I follow here over there, if you follow me, you probably want to follow me over at @bhtooefr@snack.social

@staticsafe@mastodon.zombocloud.com For that matter, when even chat programs have formatting syntax (mIRC's control code markup, irssi has limited parsing of _underlines_ and *asterisks* for emphasis, the old IM clients had lots of formatting options, and "modern" chat systems have Markdown), and microblogging is a step up from chat programs in spontaneity (read: you're *more* likely to use formatting)...

idea for Fediverse software: timed mute

mute a user, but only for a certain time period, with customizable permeability (for instance, maybe allow them to directly reply to you, but not appear in your home timeline)

this way, when someone's being lewd as fuck and you're at work, you can mute them and not forget to unmute them when you're no longer at work

(yes this is a subpost)

(and the specific user I'm subposting has suggested another feature that could deal with this equally well before)

@hund@linuxrocks.online @crodges@fosstodon.org Ah, I didn't see a post saying that.

@cynicalsecurity@mastodon.social @cynicalsecurity@bsd.network One thing that might be a good idea is to also change your name to "moved to bsd.network" on this account, or something similar? If someone's typing "@cynicalsecurity@mastodon.social" into a toot, there's no clear indication that you've moved, just that you have two accounts.

@phessler@bsd.network @aag@bsd.network @cynicalsecurity@bsd.network Yeah, network packets were the example of a data format designed on a big-endian machine that I could think of. But, with ARM, I'm pretty sure you could just switch the core into big-endian mode to handle packets, then back into little-endian, if you really needed to optimize that.

@aag@bsd.network @cynicalsecurity@bsd.network @phessler@bsd.network (Generally the only cases I can think of, of where mixed-endianness is used, would be things like a big-endian architecture emulating a little-endian one, or a little-endian architecture interacting with data formats that were designed on big-endian machines?)

@phessler@bsd.network @cynicalsecurity@bsd.network @aag@bsd.network Yeah, that's exactly what it is - big (fast, power-hungry) and little (small, power-efficient) cores. Mixed-endian systems do exist, though, but would be completely pointless to intentionally create one, especially given that ARM cores have supported bi-endian operation for ages. (Let's not talk about how ARM FPA stored things in a middle-endian format, because it never was widely adopted AFAIK.)