RISC-V is just an instruction set -- same idea as x86. While it is, of course, important to also have an open instuction set, that is somewhat separate from this post's intention. I am referring to the physical manufacture of semiconductors, RISC-V, or otherwise.
0
I believe that the addition of an edit history would be a massive boon to the usefulness of Lemmy on the whole. A common problem with forums is the relatively low level of trust that users can have in another's content. When one has the ability to edit their posts, and comments this invites the possibility of misleading the reader -- for example, one can create a comment, then, after gaining likes, and comments, reword the comment to either destroy the usefulness of the thread on the whole, or mislead a future reader. The addition of an edit history would solve this issue.
Lemmy already tracks that a post was edited (I point your attention to the little pencil icon that you see in a posts header in the browser version of the lemmy-ui). What I am describing is the expansion of this feature. The format that I have envisioned is something very similar to what Element does. For example:
What this image is depicting is a visual of what parts of the post were changed at the time that it was edited, and a complete history of every edit made to the post -- sort of like a "git diff".
I would love to hear the feedback of all Lemmings on this idea for a feature -- concerns, suggestions, praise, criticisms, or anything else!
This post is the result of the current (2023-10-03T07:37Z) status of this GitHub post. It was closed by a maintainer/dev of the Lemmy repo. I personally don't think that the issue got enough attention, or input, so I am posting it here in an attempt to open it up to a potentially wider audience.
If you look at this documentation it outlines various methods of generating URL thumbnails. Essentially, a separate request from the client for only the URL is made to the server which then returns a thumbnail. It's an absolutely moronic design choice, if you ask me.
EDIT (2023-10-02T01:35Z): Do note that the link that I provided is for Synapse v1.37 -- Synapse is currently on v1.97. Curiously, the documentation for the new versions of Synapse have removed the sections talking about URL previews. I'm not sure what's up with that.
RT373YSQwMB+y28d7xm/Xybihcmx9jgkd4RskvPuoFQ3hapIv4exdmtMe+QxsVqos5odxTVuKAftj53zXFFQyD7MK0985zDvfKYjIj+b+8rNSAG0fArG2SXVBW0mLXqRnXiZXiknoPekyu7MKr1aD8k9DMQzCap60oNWmOLoCQXdmEetiEnhGL8zW2KR9P4MxtzxMzLzPWJyLmpLbXVJdxTmHFN32IvMHiyY29iJqZegmIuav0+IP2c3leGrJs75eGW2uWoj8J8VWWzflWfRRO3FwzJFRIvrptPN0osD0wMrgLJ4FYwXZQetIEJ99TxWvxqTYak90q6HxvVygOyHPw==
I don't follow what you mean.
I have found that instances that do seem to modify the source code just use the existing "Code" link and simply point it to their own repo instead.
The first two lines of the for loop,
byte upper_byte = input_bin >> 8;
byte lower_byte = input_bin & 0x00FF;
don't really accomplish anything. The first line is bit shifting to the right 8, and then you just bitwise and it resulting in the same thing. For example, starting with input_bin:
1000 0000 0000 0000
>> 8
0000 0000 1000 0000
& 0xFF
0000 0000 1000 0000
So, every time you go through a cycle of the for loop, you'll just start with the same values in upper_byte, and lower_byte. To sequentially output each shifted value, you'll instead want something like:
output_value = 0b1
for i = 1 to 16:
latch(low)
shift_out(output_value)
latch(high)
output_value = output_value << 1
That is, if I interpereted correctly that you want the shift registers to output the following:
output_count, upper_shift_register, lower_shift_register
1, 00000000, 00000001
2, 00000000, 00000010
3, 00000000, 00000100
.
.
.
16, 10000000, 00000000
Note: Lemmy has a bug where it doesn't format some symbols correctly, so the left angle bracket gets formatted as <. The same issue exists for the right angle bracket, the ampersand, and I would presume others.
view more: next ›
Does your network not support UPnP? You shouldn't normally need to port forward in order to seed a torrent, unless your network prevents NAT traversal.